For the development cost, you could just wait till September and get the new
Archos tablethttp://www.archos.com/products/gen9/index.html?country=uslang=en
that
starts at $270. It looks like it should be the fastest available tablet.
On Sat, Jul 23, 2011 at 12:49 PM, Mark Murphy
If my users were inconvenienced, I would try to give
them a temporary solution to hold them over until I have a good solution.
But that's just me. It's a difference in engineering philosophy.
Your innocence is touching :D
Google doesn't have users, it has beta-testers.
I know it's going to
All your suggestions are valid and I've already used some of them. E.g.
I've finished with the 2.2 testing. I want to now test with as many other
devices as possible (without having to mortgage my home).
The issue isn't whether there are work-arounds, we're all engineers, our
jobs are to
On Sat, Jul 23, 2011 at 3:15 PM, Jimen Ching jimen.ch...@gmail.com wrote:
If you do not agree a VirtualBox solution is a more convenient
and efficient solution, then I don't think there's anything I can say to
convince you otherwise.
If it would work, it might be. However, I doubt that it will
Sooner or later you will have to test against a real device anyhow. it might
be a financial burden but it is inevitable.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
I don't deny that real hardware is needed sooner or later. But I hope
Google isn't restricting their developer ecosystem to multi-million dollar
software houses only. I am developing applications for multiple Android API
levels, multiple screen resolutions and screen sizes. Is Google saying
The 2.2 and 2.3 emulators work fine on decent hardware (e.g.,
dual-core 2GHz+, ample RAM). It is only the Honeycomb series of
emulators that is an issue.
Given the low penetration of Honeycomb devices to date, it is
perfectly reasonable for you to say oh, never mind for now and focus
on Android
7 matches
Mail list logo
