Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The problem is usually complexity and opportunity cost.

Once you have a team that can keep Android patched, someone at Google is going to use them to speed up another product or create a new one.

Why not add another team more? First, the situation will repeat itself, other needs would be prioritized higher. And there is a limit on the number of teams an organization can manage without non-linear manager cost increase.

Linux runs on old hardware because big corporations own old hardware and are willing to pay to not have to replace it. Replacing a phone is a cost for the individual owner. And my experience with company phones is that they are seen as a retention perk. So newer flashier phones are worth the cost, it could be different in other industries, thou.

One common solution to these problems is regulation. The government forces phone makers to patch the software for X years. Now there is a strong incentive to do so if the phone makers want to continue operating in that market.



> The problem is usually complexity and opportunity cost.

> Once you have a team that can keep Android patched, someone at Google is going to use them to speed up another product or create a new one.

Apple is still supporting phones made in 2016. Given Google size and profit margin, it is a business choice.


A lot of those costs go down with good interface design and interoperability.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: