Mark, The D pad issue can be lifted off of the product demos. Who ever found that from only looking at the video is pretty sharp... I typically don't start putting in the effort until I have some hardware or at least a serious emulator in my hands. Once the devices roll out I am sure more issues will pop up. I might walk down to the T-Mobile store one of the days and check one out, if they let me, just for laughs. It's the principle that makes me wonder. It's lost on me how virtual test environments are sufficient to support testing nowadays, where a good rate of the apps rely on sensor inputs and where timing is key. So, rhetorically asking, what's the approach, beyond that? That devs buy all the shiny toys can't quite be the answer. Or can we factor that into charging for apps (uhum).
On Sep 11, 5:49 am, Mark Murphy <[email protected]> wrote: > JoaJP wrote: > > The vast majority of apps will not receive any "adjustment", safe some > > exceptions with deep pockets that can justify the expense. > > For the Cliq's D-pad, I suspect that the vast majority of apps will not > need changing. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Android Training in Germany, 18-22 January 2010:http://bignerdranch.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
