Hmm. I can't think of any time I've thought the app was really missing something, or didn't work. In fact, I always thought the app was pretty smooth and "just worked".
By comparison, several years ago, I was regularly streaming Netflix content without any trouble. One day I streamed a show on the HBO app on mobile data and it ate up almost all of my month's data usage. I guess it's behind the scenes work, and not so exciting, to e.g. stream a smaller resolution for a mobile phone, but in moments like that you realise there are a substantial amount of things to think about when making such an app.
If you live in the US there is a good chance that was your phone company throttling Netflix and the app automatically switching to 480p to adjust to the reduced bandwidth. They probably do that more broadly now but when they first started it was only Netflix.
I don't live in the US, but how would this work? Isn't the video sent over SSL? In that case how would the phone company know what to send back?
I just assumed that Netflix had different video formats on its' servers, ready to go, and when the app requested the video it also sent the screen size/resolution to get the smallest file size, that would also look good on my phone. If that was 480p then all well and good, it was fine to watch.
It was a while ago now, but IIRC the amount HBO used was pretty horrendous, like a GB for 30 mins or so of video, so I guess they just downloaded a big file and let the player on the phone handle that.
Like a say, a few years ago now so the situation may well be better with HBO now.
By comparison, several years ago, I was regularly streaming Netflix content without any trouble. One day I streamed a show on the HBO app on mobile data and it ate up almost all of my month's data usage. I guess it's behind the scenes work, and not so exciting, to e.g. stream a smaller resolution for a mobile phone, but in moments like that you realise there are a substantial amount of things to think about when making such an app.