Linked by Thom Holwerda on Fri 15th Feb 2013 18:53 UTC
Permalink for comment 552738
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
More Features »
Sponsored Links



Member since:
2005-07-06
I'm not sure who would use the emulated Android device in the Android SDK, because it's trivially easy to get the SDK's "Run..." option to send the built apk to a real device (attached via USB in debugging mode) and run it immediately. I do it with my Nexus 7 and/or 10 when coding Android apps - it's almost irresponsible of any devs not to do this, especially since it's so easy.
Hence, how efficient the emulated Android device is really is an irrelevancy as far as most devs are concerned because I bet very few of them use it exclusively (who is going to develop any meaningful Android app and not have *any* real Android devices to test it on?).
Also note that the Nexus 10 is an ideal "reference Android device" because not only does it get the latest Android releases first, it can also adjust its screen resolution/density (via adb commands) to simulate the screens of "lesser" devices should you wish to test real hardware (GPS, accelerometer etc) with different screen attributes.