3 ms·

This is why you should avoid developing for the Android for at least 6 more months. It has been too liquid and fragmented so far. The yield for your effort is n

This is why you should avoid developing for the Android for at least 6 more months. It has been too liquid and fragmented so far. The yield for your effort is not very optimal.

napoleoncomplex 15y ago
I would argue that now is the perfect time to start developing for Android, if for some reason you aren't doing it yet. The recently published design guidelines from Google are clear and lay a good foundation for anyone who has struggled with figuring out how to develop and design for the OS, and also show that Google finally "gets" where their platform has been lacking so far. The Action bar, although in a limited manner, can also be implemented in older versions of Android, so from a coding perspective, there's nothing terribly scary about it.
babebridou 15y ago
Fragmentation is definitely not that kind of issue. It has to do with Hardware Acceleration, Screen sizes, Memory capabilities, native I/O threading and the likes. The only fragmentation issue I've ever had that directly concerns the UI is the presence of default Android Icons and fonts. Some manufacturers remove them, others decide to not implement them or give them arbitrary layout constraints: Sense UI for instance refuses to let you draw a Generic android icon over less than 40pixels. Motorola Xoom's default OS on Honeycomb did not let you display a size 106 font. Stuff like that. These are the kind of fragmentation issues you're going to have to bite. Fragmentation over whether a phone has or doesn't have a menu button is of no relevance. This app(1) for instance works both with the Action Bar, the software menu button and the hardware menu button. I only had to point the onCreateOptionMenu method to a single XML, and the ICS SDK did all the defragmentation work for me. It works fine from Froyo to Ice Cream Sandwich, on tablet, on phone, on KindleFire. (1) shameless plug: https://market.android.com/details?id=com.fairyteller.icanread https://market.android.com/details?id=com.fairyteller.icanre...
shareme 15y ago
a lot of contracts will come up of companies updating apps..money to be made..

This is why you should avoid developing for the Android for at least 6 more months. It has been too liquid and fragmented so far. The yield for your effort is not very optimal.

napoleoncomplex 15y ago

I would argue that now is the perfect time to start developing for Android, if for some reason you aren't doing it yet. The recently published design guidelines from Google are clear and lay a good foundation for anyone who has struggled with figuring out how to develop and design for the OS, and also show that Google finally "gets" where their platform has been lacking so far. The Action bar, although in a limited manner, can also be implemented in older versions of Android, so from a coding perspective, there's nothing terribly scary about it.

babebridou 15y ago

Fragmentation is definitely not that kind of issue. It has to do with Hardware Acceleration, Screen sizes, Memory capabilities, native I/O threading and the likes. The only fragmentation issue I've ever had that directly concerns the UI is the presence of default Android Icons and fonts. Some manufacturers remove them, others decide to not implement them or give them arbitrary layout constraints: Sense UI for instance refuses to let you draw a Generic android icon over less than 40pixels. Motorola Xoom's default OS on Honeycomb did not let you display a size 106 font. Stuff like that. These are the kind of fragmentation issues you're going to have to bite. Fragmentation over whether a phone has or doesn't have a menu button is of no relevance. This app(1) for instance works both with the Action Bar, the software menu button and the hardware menu button. I only had to point the onCreateOptionMenu method to a single XML, and the ICS SDK did all the defragmentation work for me. It works fine from Froyo to Ice Cream Sandwich, on tablet, on phone, on KindleFire. (1) shameless plug: https://market.android.com/details?id=com.fairyteller.icanread https://market.android.com/details?id=com.fairyteller.icanre...

shareme 15y ago

a lot of contracts will come up of companies updating apps..money to be made..