Understanding the limitations of the simulator (understanding the emulator's limitations)

Understanding the emulator's limitations

Although the new simulator keeps up with the development of devices and ensures high-fidelity simulation of devices and the convenience of developers, each simulator has some limitations when simulating real devices. The smartphone code run by the simulator in the smartphone SDK is compiled for the x86 CPU. In most major application development scenarios, this is enough to meet the requirements. However, this type of simulation still has some limitations:

L to use a simulator, the application must be compiled into a program running on the x86 CPU. Applications must suffer from potential differences between x86 compilers, runtime, and support files and ARM-based devices.

L because of the difference between the CPU architecture (x86 CISC versus arm PROTEUS) and the instruction set, it is impossible for the simulator to express every absolute detail of the operation, and the simulator cannot optimize the memory area very well. However, for most applications, this level of analysis does not constitute a real problem.

L The mouse replaces the touch screen. Although the mouse and touch screen functions are similar, application developers still need to consider the user experience of running the program using the touch pen.

No matter whether the development workstation supports the recording function or not, the recording function is not supported in the simulator.