[android-developers] Re: First QVGA Android Phone — HTC Tattoo™ — on sale October 2009. Is your application ready?

I've already tested the Tattoo's (and other) screen sizes; works fine
in the emulator... i've built that capability into my products from
day one. But that's starter issues; emulator testing only goes only
so far.
As an example, there is no adequate representation of the camera
preview in the emulator. Sensors (accelerometer, magnetometer) fall
into that category as well. Given different processors/clocking
resulting in different execution speeds, race conditions in multi-
threaded apps may be revealed. Or some work might be required for
those that integrate an audio codec in their app, to bring up another
example.

Even on relatively closely related devices like the G1 and the Google
Ion (please fill in the correct HTC product names), we've seen
problems with the camera preview. And with other manufacturer's
products we heard about differences in sensor outputs. So, at least
speaking for myself, with emulator testing only, it is not possible to
ready an app for the upcoming Tatoo, or any new device, with
sufficient confidence.

On Oct 28, 6:07 am, "htcand...@gmail.com" <htcand...@gmail.com> wrote:
> Thank you for your question.
>
> We expect the same look and feel between the QVGA emulator and the
> device, so if the UI of your application does not have a problem
> displaying on the emulator, then it should not have a problem on the
> device.

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---