1. Make sure you're using the latest version of Android Studio Meerkat and that your app uses the latest version of Android Gradle Plugin.
2. Open Android Studio and create a new Android project with the Empty Activity template.
3. Switch from the Android view to the Project view to access the project structure.
4. Click the New button in the Project view and select Kotlin Multiplatform Module from the options. Choose Shared Module as the type and keep the default settings.
5. Open the build.gradle.kts file in the Android app directory and add a dependency on the shared module.
6. In the Shared module, edit the Platform.android.kt file and add the following line of code:
   actual fun platform() = "Android from Shared KMP Module"
7. Open the MainActivity.kt file in the Android app directory and modify it to call the platform() function from the shared module.
8. Build the project and run the Android application. You should see the message, "Hello Android from Shared KMP Module!" displayed on the screen.

To get started, click the + button from the Device Manager, and select either Create Virtual Device or Select Remote Devices.

When creating a new virtual device, new filters and recommendations make it easier to create a device configuration that fits your needs and performs the best on your workstation.

Similarly, when selecting remote devices from Android Device Streaming, new filters make it easier to find and select the devices you need. You now only need to click the Firebase button at the top of the Device Manager window to select the Firebase project you want to use for Android Device Streaming.

To generate unit test scenarios, do the following:

1. Navigate to the class you want to generate unit test scenarios for.
2. Right-click on the class and select Gemini > Unit test scenarios from the context menu.
3. In the dialog that appears, select the methods of the class that you want to generate scenarios for, and set the destination package for the tests.
4. Click OK.
5. Confirm the destination directory for your tests and click OK.
6. If the test class already exists, confirm whether you want Gemini to suggest updates to the existing file.

After Gemini processes the request, you should see either a new file with the suggested unit tests or a diff for you to accept recommended changes to an existing file.

• Added a new Build 'run-configuration-name' Run Configuration action: This action builds the currently selected run configuration. For example, if you have the :app run configuration selected, the action will build and assemble app. If you have recently run a test on a device the action will build those tests.
• Made Build 'run-configuration-name' Run Configuration the default Build action: To better match developer's intent, both the toolbar button and the shortcut Control/Command+F9 now execute the new Build run-configuration-name Run Configuration action.
• Reordered build actions: We placed the new Build run-configuration-name action at the top of the Build menu, next the Compile actions, and next the "Assemble ..." actions (previous "Make ..." actions). We also renamed the "Rebuild Project" action to "Clean and Assemble Project with Tests" to more clearly reflect what the action does.
• Used verbs that match what the build actions actually do: In addition to "Build" and "Compile" actions, we renamed Make Project to Assemble Project. We also introduced a new Assemble Project with Tests action to assemble test components as well.