4 ms·
Using it for app development. Better performance than android emulators, and better workflow if you place the copied screen side-to-side to your IDE.
by quambene 5y ago
Using it for app development. Better performance than android emulators, and better workflow if you place the copied screen side-to-side to your IDE.
- iKlsR 5y agoCan you explain your workflow/setup a bit more in detail?
- MrDresden 5y agoI imagine his workflow consists of a mobile device (that stays awake without user input) is plugged in to the dev machine which is running scrcpy. The scrcpy screen is then on the dev machine screen next to the editor so that code can be deployed/hot-reloaded/applied to the device as it changes. The emulator is too slow, and Jetpack Compose previews do not handle complex situations well, so a device is always the most preferred method. This has at least been my way of developing for Android over the years.
- quambene 5y agoYes, appropriate description. This way you can use your mouse to navigate your app instead of switching between mobile device and mouse all the time. I was surprised that there is no noticeable lagging. If you like you can turn the device screen of via option --turn-screen-off, and the scrcpy screen will still be available. Furthermore, option --max-size 1024 is handy to customize the size of the scrcpy screen accordingly.