To be honest, I rarely use the Emulator that comes with Android Studio. On the one hand, it is very slow (the computer is too bad), and on the other hand, when the IDE is in full screen, you can’t view it directly, and you have to cut it by shortcut keys, which is very troublesome.
In the latest Android Studio 4.1 Canary 8, Emulator is built directly in. You can run Emulator directly from within the IDE, rather than as a separate application. Here’s a picture from the official website to give you a feel.
I have to say that the Android Studio team has been in good faith lately, having just released the Database Inspector feature. I talked about that in the previous tweet database you can also view it this way.
In addition, the latest Database Inspector now supports Live Update. When you make changes to Database data in your application, the changes are displayed automatically in the View tools instead of manually refreshing the data.
The following is a brief introduction to the use of the built-in Emulator.
use
File > Settings > Tools > Emulator (or Android Studio > Preferences > Tools > Emulator on macOS)
Check Launch in a Tool Window on the right.
Then run the application as usual. You can start the VIRTUAL machine through AVD Manager, or run the App directly on the virtual machine.
limit
The built-in VM supports few extended functions, such as shutdown, volume, screen rotation, back button, Home button, and screenshot. If your app relies heavily on extensions, stick with the previous approach.
experience
I tried it on my open source project Wanandroid, and it looks something like this.
Yeah, it smells good.
I’ll stick with the real thing. Escape ~
digression
I don’t know if you have run my previous version of Wanandroid, I can’t bear to look at it. In the last commit, I upgraded to MDC 1.1.0, which is this:
Implementation 'com. Google. Android. Material: material: 1.1.0'Copy the code
MDC 1.1.0 brings Material Theming, new components, dark mode support, and more. I replaced the AppCompat system theme in my application with the MaterialComponents system theme, and replaced some of the components, which, I have to say, is much nicer. You can try it.
For specific modifications, please refer to my latest submission:
https://github.com/lulululbj/wanandroid/commit/fc900ab20b07c2bf4b266fae4ab931f1c6aef01e
There is also an official article devoted to MDC at the following address:
https://medium.com/androiddevelopers/migrating-to-material-components-for-android-ec6757795351
Today’s article is here, I have been adhering to the original bingxin said, more latest Android dynamic, scan code to pay attention to my public number!
This article is formatted using MDNICE