7 ms·
So should we force product owners to support multiple older versions of clients, even though the backend is progressed? Who will pay for this extra cost, the us
by seqizz 3y ago
So should we force product owners to support multiple older versions of clients, even though the backend is progressed? Who will pay for this extra cost, the users who don't upgrade their devices? I don't think so.
Do every rule has to be written, or does writing them into law makes it logical every time? App owners can add "we only support client versions which is max 6 months older than current stable version" to their EULA and it is also fine (while being worse than current situation) then?
- ftth_finland 3y agoNo, not forced to support. One should, however, be able to download old software and install it. This is not currently possible.
- gtvwill 3y agoForce the release of all code that product was sold with in its factory state to users along with code for all updates applied to that factory state during its company supported lifetime. Firmware blobs the lot. Corporate profits aren't an acceptable excuse for negligent business practices that push a forced culture of wasteful consumption. Apple needs to pull their head in along with many others in the tech world.
- TeMPOraL 3y agoWe should force product owners to stop designing their products as thin clients of server-side APIs. Then there won't be any support costs for older devices.
- ajmurmann 3y agoHow does that work for a lot of the apps described in the article? Railroad tickets get purchased without web access how? Would all map data for the map applications mentioned in the article be downloaded with the app?
- joshspankit 3y agoJust like anything physical, you could simply have a “go ahead and do it, but you get no help from us” policy. When the ecosystem is open enough there is a community of people who learn what they need to. For reference see: car racing.