3 ms·
You raise a good point, and in order for this to work they'll need to ensure a full suite of emulators are available for testing. Android already provides an em
by qeorge 17y ago
You raise a good point, and in order for this to work they'll need to ensure a full suite of emulators are available for testing. Android already provides an emulator [1] that can be configured to match the target device, although I can't speak to its quality as I have not used it. Windows Mobile is in a similar position, and its SDK provides emulators for every phone you would want to test on.
Phones differ so much in form factor alone that you really need to be testing individually for any phone in your target market anyway. Its a huge time-sink to be sure, but you won't be flying blind.
[1] http://developer.android.com/guide/developing/tools/emulator.html http://developer.android.com/guide/developing/tools/emulator...
- evgen 17y agoIts not just about being able to test (although I have serious doubts that any suite of emulators will be able to give anything more than a rough guess as to how an app will perform on a wide variety of potential platforms) but also about what features will be available, what APIs will work, and how much code you will have to write to deal with some funky condition on Vendor A's phone that makes it differ in some subtle way from Vendor B and C's phones. Eventually they will probably figure it out, but for the next year or so this game is going to make browser feature detection look like a walk in the park...
- shimi 17y agoFrom I seen so far unless you're playing with low level stuff the software is consistent across the devices. For now Android is far from the J2ME scenario, let's hope it will stay that way.
- dminor 17y agoThe emulator is quite configurable, so you can set up a profile for each set of hardware. Of course there are things like tilt sensors and accelerometers that just don't translate well.