You are f** right. And I'm just ungry. Android is going stright forward J2ME way - milions of devices, thousands profiles, screen sizes, controls, etc..
I think, the biggest Java/Android advantage - one code for all devices is slowly vanishing. I tried to fix some problems with my app on new devices. But you can't bugfix, without real device, when your app works on all emu possible SDK's without problems. I'm tired of that shit. So, small developers like me, that do not own thousand devices to test, are wasting more and more our time for testing, tuning, special custom design, bugfixing for new devices each day. The problem is growing and I'm sure, that future testing costs will be BIG. I'm jumping out of that train to nowhere.. On 17 Sty, 05:06, Alberto <albertovi...@gmail.com> wrote: > UPDATE: At first this was going to be just a call to fix the updating > process, but I've realized is not just the updates Google needs to > take control of. > > Now is the time to address the fragmentation issue that's starting to > plague the platform, before there are hundred of handsets and the > whole thing spins out of control. I believe we've seen enough evidence > that the updating process through the carriers doesn't work, many > phones are left behind and the whole thing is a mess, today we're > already talking about the next update (2.5 Froyo?) while there are > phones out there stuck on 1.5, the fragmentation is only going to get > worse as we move on. > > Imagine when 3.0 gets here, and we have hundreds of handsets with 1.5, > 1.6, 2.1, 2.5, 2.7, 3.0 some with Sense UI, MotoBLUR, etc. It's going > to be hell for developers and even more confusing for consumers, > driving everybody away from the platform. You guys need to take > control of this at least for the Google Experience phones. I'm not > sure if Google updating the handsets directly would bring legal issues > with the carriers/manufacturers, if it would, please enlighten me. > > So how do we fix this? I'm pretty sure you guys have already thought > about this and I wouldn't be surprised if a solution was coming soon, > since it''s such an obvious problem. However, here's my two cents, the > solution is very simple, a desktop application for syncing/updating/ > media playback/android market/amazon mp3, lets call it Android HQ or > Android Home for the sake of argument. > > The updates would be available to consumers as soon as they're > released, instead of months, years, or never depending on carriers. > This way most users would've the latest version as well as the > developers would have the latest SDK, developers would be able to take > advantage of the new APIs each updates bring and innovate faster, > instead of spending time supporting older versions. > > Android HQ would also address the next two biggest problems with the > platform, they're: media ecosystem and media syncing/backing. Also, > the Android Market badly needs a desktop client. > > The fragmentation issue is the biggest obstacle the platform is facing > today and it will most likely decide its success, I've sensed a couple > of times that Google stance on these issues is to let manufactures/ > carriers make the decisions on a phone to phone basis (multi-touch > anyone?) but that won't work, it'll eventually slow the momentum we > have now and kill the platform (WinMo?) Google needs to have a more > hands-on approach to Android if it wants it succeed. > > Anyway, the guys/gals in the Android Team want the platform to succeed > as much as me, I'm sure they've given this a lot of thought, and a > solution is probably on the works.
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
