> Fast hardware can mask performance issues, Very good point there. The emulator to me seems to be "reasonably slow" for a good emulation of the G1 however.
Outside of that, I'd go with the N1. If I did Android development all day, the time savings when debugging on the device will add up. I have yet to see a nicely built Android device. Haven't nearly seen them all though. By and large there's always a level of flimsiness and they all (the HTC's at least) heat up when being charged/GPS is on//searching for a network... or whatever. Cheap parts everywhere you look, but if you use it for development that shouldn't matter that much. On Feb 2, 10:04 pm, String <[email protected]> wrote: > On Feb 2, 7:08 pm, Jonathan <[email protected]> wrote: > > > I would also like to know which phone(hardware name) is nicely built > > and 'the best' 2.0 phone and supports nicely for my Android 2.0 > > application development and testing? > > IMHO, you're better off developing on a phone which ISN'T the latest/ > fastest hardware. Fast hardware can mask performance issues, which > will nonetheless be seen by the large percentage of users who are > still on older/slower hardware. > > Also, there is no single "best" phone. It's all a matter of > opinion. :^) > > String -- 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.
