MCON Dev wrote: > Mark, > Good ideas.. I went by your suggestion to move ahead. But this is a > potential risk (small one I guess). I assumed that the emulator testing > would be enough atleast for the android application. Are there cases > where the product has worked well on the emulator but worked differently > on the actual product ?
The closer you get to actual hardware, the less the emulator is "real". So sensors, camera, microphone, WiFi, GPS, SIM cards, and things like that are all either unavailable or very fake on the emulator. Similarly, the emulator lacks graphic hardware acceleration that may be available on some devices (G1, HTC Magic), which may affect graphics rendering rates. For application logic that depends less on the hardware, the emulator is great and generally seems to behave the way real devices do. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 1.0 In Print! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
