As an aside, I asked the same question of Romain and Chet at Devoxx, and if there were plans to improve it. They were both honest and said that all the Android dev team use real hardware rather than the emulator whenever possible. If I remember correctly they also said there were plans afoot to try and improve things.
Having written a small amount of Android code I can say that if you are writing commercially then a development phone will pay for itself very quickly in terms of time saved. There is also the plus that all of the APIs are fully functional whereas in the emulator some are stubbed - development is complicated by some of these stubs that throw an exception when invoked instead of pretending to 'do something'. On Jan 28, 1:05 pm, Casper Bang <[email protected]> wrote: > Also not a bad question, lots of people wonder about this (as did I > when I got started:http://goo.gl/J6IMz). :) > > On Jan 28, 12:31 pm, Karsten Silz <[email protected]> wrote: > > > On Jan 28, 12:22 pm, Casper Bang <[email protected]> wrote: > > > [...] > > > Thank you very much, that was a great answer. -- You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en.
