6 ms·
Why a web-based emulator? Just use the one that's included with the Android SDK. You can simulate any combination of memory, screen size, screen resolution, and
by yellowbkpk 14y ago
Why a web-based emulator? Just use the one that's included with the Android SDK. You can simulate any combination of memory, screen size, screen resolution, and various hardware characteristics. Sure it can be slow, but it's getting better and is actually emulating the system you're developing for.
- stesch 14y agoIs the emulator in the SDK usable now? Last time I tried Android programming it was slow as hell. Unusable even for a simple Phonegap app.
- sureshv 14y agoIt's still slow because it literally emulates the phone running on an ARM CPU rather than simulate ala the iPhone simulator which runs an x86 version of IOS.
- myko 14y agoUnless you use the x86 emulator image.
- cageface 14y agoIf you use the Android x86 system image it's not bad at all. ARM emulation is still slow as molasses.
- mdwrigh2 14y agoTry enabling GPU emulation if you're dealing with ICS. It's much, much faster.
- taligent 14y agoYou've never actually built an Android app have you ? The emulator is NOTHING like the real devices.
- yellowbkpk 14y agoYes I have. Admittedly we usually used real devices for testing but the emulator does just fine debugging most "fragmentation" issues (screen size and resolution and Android API differences).
- deleted 14y ago[deleted]