3 ms·
In fairness to Samsung they do incur non-trivial cost doing this. Imagine this situation Verizon says, "Our Samsung Galaxy S phone must get 2.2" while Sprint s
by kenjackson 16y ago
In fairness to Samsung they do incur non-trivial cost doing this.
Imagine this situation Verizon says, "Our Samsung Galaxy S phone must get 2.2" while Sprint says, "No need". Should Sprint have to pay for what Verizon is getting?
The issue is that you're going to pay, whether its Samsung or HTC. Some companies will build the price into the phone, others will price it in some other way (or some companies could eat the cost -- but that's probably not sustainable).
Charging directly to the end user seems like the best way to do it. If I want 2.2, then I should pay for it, and if I'm happy with 2.1 why should I pay for other people to get 2.2? But short of that, charging the carriers makes sense.
- jsz0 16y agoThe biggest downside I see is that it will shackle Google's ability to move the platform forward. For example 2.3 is reported to include some major improvements for low latency audio. As a game developer how do you handle this? Just ignore this 2.3-only feature and target 2.1? Or do you build a 2.1 and 2.3 version? 2.2? 3.0? 3.1? Unfortunately we're talking about these phones being around for another 2-3 years at minimum so realistically you might be asking a developer to support 2.1 3 years from now? That's going to be a really tough sell. The other issue is security. Leaving all those old versions out there with little or no post-release updating is just begging for trouble. (and let's not forget about bug fixes -- no one wants to suffer 2 years working around an annoying bug. They simply won't buy another Android phone after a bad experience like that)
- deleted 16y ago[deleted]
- deleted 16y ago[deleted]
- deleted 16y ago[deleted]
- marshray 16y agoI know the goal is to run lean and all, but there are these principles called "cost of doing business" and "not chiseling your customers to the point they feel cheated". The problem is they're hard to quantify, so businesses with more spreadsheets than soul are doomed to go down this road. I'm a software developer and I've built a Linux kernel my share of times. I don't know anything about Android though. But it seems to me we're talking about porting a kernel and some device drivers that you already have working to a new version. If a new version of Android such a big deal to you then maybe you shouldn't be in the smart phone business? Just sayin. Like I said, I don't know Android, so someone could 'spain it to me.