3 ms·
Some of that hardware will have physical keyboards. Some of it will not. .... If you build an Android app, you have to decide if you'll optimize it for a physic
by trezor 17y ago
Some of that hardware will have physical keyboards. Some of it will not. .... If you build an Android app, you have to decide if you'll optimize it for a physical keyboard on the long edge, or a physical keyboard on the short edge, or a software keyboard.
Add touch-screen capabilities to this list, and you have the mess that was software for Windows mobile. Add multi-touch if you want to make it really messy.
In the end, 90% of your software's code is going to be dealing with different types of user-input, user-input capabilities and how to interface with the actual code that does stuff.
I'm definitely going to agree with you on this being a problem that needs solving before Android being on thousands on devices can be considered a good thing.
- mechanical_fish 17y agoI only left the touch-screen out of my argument because I frankly can't remember what kind of touch screen the typical Android phone has. Which, of course, may also be a symptom of the problem. (Though perhaps it is just a symptom of my poor memory.)