I personally think that in the simplest language, the simulator is to use the least amount of money to provide a small number of services.
But this is at the expense of performance, the full range of performance drops, and the things that can be done are few. Many times you in the simulator to raise everything, feel no problem, to the real machine will appear a variety of inexplicable bugs, let you unprepared So the best way to do Android is to use the real machine Specific reasons:
- android, resulting in virtual machines and Samsung, Huawei and other terminal machines there are some differences
- android simulator itself is not very good, very slow to run, really very slow
- android simulator sys-img to be downloaded or trouble , or Die slow
- for cameras, GPS, sensors and other hardware development, Real-machine testing benefits are significant
But the real machine also has a problem, some start-up companies or small and medium-sized enterprises do not have so much capital to build model libraries, at most, there are several mainstream machine, but want to do a successful app this is not enough, to complete the application test needs of the model cost is very large, so it is recommended to use now Testbird Cloud phone for remote debugging, save a lot of purchase cost, and the same is the real machine, the same effect. Of course, the real machine debugging or simulator debugging is mainly to see the degree of convenience, different needs of the choice may not be the same, for example, I would like to adapt to the latest Android 6.0 system, but the real machine system may not be so timely update, you have to use the analog machine. For simulators, it is recommended to use Genymotion, which is faster and has a free version. Genymotion Simulator is fast because it is based on the x86 architecture, if you use so in your application, but there is no x86 architecture so, can only abandon the use of it, Android Studio Simulator is the same; |