I doubt that it is going to be as big of a problem as you are expecting it to be.
The *main* issues are going to be related to the effects of screen size. Desktop software developers have had to contend with infinitely variable screen space for years (for desktops, there is more than just the screen resolution -- there is also the infinite variation in "unmaximized" size). Other issues may be the physical sensors (i.e. accelerometer) which could be calibrated differently between devices. Things like GPS will be fine. Users of the NDK will definitely have a hard time wrt different CPU architectures that are bound to come into play, but applications on market will target for the CPU architecture anyways. When you talk about the camera differences between MAGIC and DREAM, to what specifically are you referring and what did you have to do to deal with it? From what I can tell, they are *identical* in that respect... Are you certain that it was due to hardware difference and not due to running a different version of 'droid? The wonderful thing about running your software in a virtual machine (dalvik) is that it creates a *much* more constant environment for the application to run in, which really helps in reducing the effects of device variation. On Oct 20, 11:35 am, JP <[email protected]> wrote: > Someone paid attention and compiled a > list:http://wiseandroid.com/NewsItem.aspx?category=News&path=October&itemi... > > The issue of varying screen sizes, resolutions and densities seems to > be decently covered by the tools upgrades in 1.6 and what must be the > longest developer blog post so far. It seems everyone can cover this > area reasonably well. > > Based on how things have shaped up so far, there seem to be plenty of > differences even among devices of one manufacture that'll still be out > there to get everyone who's published apps that go beyond ringtones > and skins. Personally I've gotten lightly burnt on a difference re: > the camera preview between the Ion and the G1, so it's obvious there's > plenty of things that have and will continue to go wrong based on > device variances. > > Anybody got any good ideas or practices to cover this? So far I've > only come up with the idea of including a disclaimer like "Tested on > Google Ion and HTC G1" in the app description. Neither appealing nor > terribly professional, so I wonder what everbody's intending to do to > cover this issue... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
