| ▲ | Wowfunhappy 6 hours ago | |||||||
It makes no sense to me at all. If they don't want to support interactivity features in their overall Netflix.com front-end, they should release a separate app. They're still trying to get into video games—they just bought the rights to FIFA, for goodness sakes—so they should make use of their ready-made content. There is no way the actual code for selecting choices is particularly complicated. Maybe as part of a larger codebase it could become tech debt, but on its own? | ||||||||
| ▲ | zamadatix 6 hours ago | parent [-] | |||||||
A separate app would be a lot more work. Not only do you need to publish separate apps on all of the platforms you still need to maintain that separate app (even if it's 100% locked to bug and security patching). If I were to guess, it had less to do with being "too difficult" and more to do with "not being worth it". I.e. they have the numbers for how many people were watching the limited interactive content from years ago, they know whether they plan on having more interactive video content, and they know how much it is to maintain across different apps (and likely don't want to fragment their service availability to support something they identify as a declining niche). Just because they may be getting into games does not mean it makes sense to have support for other interactive stuff people hardly ever watch. They tried something different, it didn't work out to be popular enough to bother with for the rest of time, and they moved on. | ||||||||
| ||||||||