Our approach to development will use user experience and feedback to help broach this problem. Instead of a traditional "from sales people to market" flow, we use something more like: 1) Prototype the core feature(s) of a great idea (something we ourselves would like to use) 2) Release as Beta 3) Use customer feedback to define featureset 4) Final release
So, we count on users of our applications to help--to some degree--as the platforms diverge. In addition, we try to keep an eye on the obvious differences and will purchase the proper hardware to test on as and when necessary. For example: 1) The (mentioned) camera differences between the Ion and G1 2) The hardware OpenGL differences between the HTC devices and Samsung devices 3) The varying screen sizes So, for example, as soon as we ready any OpenGL-related product, we will purchase a Samsung Galaxy. While there are notable differences, and I believe the number of them will increase in the short term, I also think we'll see a convergence much like in the PC market, where the differences will not make or break the applications. For example, a unified Camera Preview pixel format API might be released, some minimal set of hardware OpenGL might become ubiquitous, etc. Scott On Tue, Oct 20, 2009 at 8:35 AM, JP <[email protected]> wrote: > > Someone paid attention and compiled a list: > http://wiseandroid.com/NewsItem.aspx?category=News&path=October&itemid=14 > > 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... > > > > -- Warm regards, The PhoneMyPC Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
