There are two benefits of real machine debugging: first, debugging is more efficient, and second, you can get a real operating experience (after all, the screen on the computer does not support touch screen)
Real machine debugging of standardized commercial projects is still necessary.
It depends on your own situation. Not every time you need to debug on a real machine, most of them can still be done on the simulator. Unless there are special circumstances. It's fine on the simulator, but it's problematic on the phone. For example, yesterday I encountered a problem, and it was fine in the simulator. There is a problem on the phone. So it is necessary to debug on a real machine instead of debugging on a real machine every time
This depends on the needs of your project; if you are developing a pure app application and do not need to communicate with other hardware devices, then it will be no problem to directly use the simulator to develop and debug your project throughout the process. But if you develop applications for smart hardware, you need real machine debugging. For example, if you want to develop a Bluetooth speaker APP, then you will inevitably need to communicate with the speaker through Bluetooth BLE; and the simulator does not have Bluetooth function, so it needs to be run on a real machine for debugging. Hope this helps!
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
There are two benefits of real machine debugging: first, debugging is more efficient, and second, you can get a real operating experience (after all, the screen on the computer does not support touch screen)
Real machine debugging of standardized commercial projects is still necessary.
It depends on your own situation. Not every time you need to debug on a real machine, most of them can still be done on the simulator. Unless there are special circumstances. It's fine on the simulator, but it's problematic on the phone.
For example, yesterday I encountered a problem, and it was fine in the simulator. There is a problem on the phone.
So it is necessary to debug on a real machine instead of debugging on a real machine every time
Subject to the real machine.
A real machine can be understood as a formal test environment.
When making the interface, I basically debug it on a real machine. Data binding, use the simulator to debug when writing logic.
This depends on the needs of your project; if you are developing a pure app application and do not need to communicate with other hardware devices, then it will be no problem to directly use the simulator to develop and debug your project throughout the process. But if you develop applications for smart hardware, you need real machine debugging. For example, if you want to develop a Bluetooth speaker APP, then you will inevitably need to communicate with the speaker through Bluetooth BLE; and the simulator does not have Bluetooth function, so it needs to be run on a real machine for debugging. Hope this helps!
Decided according to your project needs