3 ms·
Forgive me, but do you work somewhere where you have access to what's coming down the Android pipeline? You're in for an unpleasant surprise. Most of the devi
by kogir 17y ago
Forgive me, but do you work somewhere where you have access to what's coming down the Android pipeline? You're in for an unpleasant surprise.
Most of the devices I've seen are great by themselves. If I played with one in a store I'd want it. But as a group, when they're what my company has to target for distribution, things could get really ugly.
- jrockway 17y agoHow? Android 1.6 seems to provide enough features for abstracting away the differences between current and near-future devices. Practically; I was an early adopter for the HTC Magic. Despite that, all the apps designed for the G1 worked fine. I could even use Emacs in ConnectBot (ssh client) with the soft keyboard. Now that's abstraction!
- hackoder 17y agoI dont see why it would be hard to change the screen resolution on the fly, kinda like what desktop games do. Other apps can use fluid layouts to fit multiple resolutions. When it comes to other features of the phone, e.g. camera or accelerometer, like one of the posters said- you'll have to do progressive enhancement. Intelligent web developers already know how to do this. You feature test, then you enable a particular feature. Its not all that difficult.
- angelbob 17y agoFluid layouts are a reasonable compromise, but they mean a layout that's slightly "off" in many cases. Look at how GTK+ scales on different mobile devices, for instance. It works, but it means giving up a lot of control, and the results tend to show it.
- buster 17y agoforgetting the fact that GTK is quite some years old and software has evolved. You really think it's impossible to have a scalable UI? Ever surfed the internet with different resolutions? Now imagine you don't have cross browser incompatibilities and a framework that behaves the same everywhere.