I don't know a single Android developer who uses the emulator. As you point out, I don't understand how I can run the emulator on a 3 point something gigahertz processor with zillions of cores, many gigabytes of RAM and the emulator has the same sort of performance as a 100MHz ARM device.
And even if you manage to get the emulator running it is virtually useless. Various pieces are missing. A lot of my work involved sound. The trivial "play this mp3" interface worked, but doing anything else failed. For practical purposes you cannot play or record audio.
Then Google likes to have bugs such as the WebView crashing when you use addJavascriptInterface. This means you can't run most apps that use WebViews. The bug has been there for 18 months, starred by many users, and Google has done SFA about it. Most importantly, why does the emulator differ in behaviour from the real device?
I don't know a single Android developer who uses the emulator. As you point out, I don't understand how I can run the emulator on a 3 point something gigahertz processor with zillions of cores, many gigabytes of RAM and the emulator has the same sort of performance as a 100MHz ARM device.
And even if you manage to get the emulator running it is virtually useless. Various pieces are missing. A lot of my work involved sound. The trivial "play this mp3" interface worked, but doing anything else failed. For practical purposes you cannot play or record audio.
Then Google likes to have bugs such as the WebView crashing when you use addJavascriptInterface. This means you can't run most apps that use WebViews. The bug has been there for 18 months, starred by many users, and Google has done SFA about it. Most importantly, why does the emulator differ in behaviour from the real device?
http://code.google.com/p/android/issues/detail?id=12987