Android Studio is the official IDE for Android development, and includes everything you need to build Android apps.
visual layout editor
Create complex layouts with ConstraintLayout by adding constraints from each view to other views and guidelines. Then preview your layout on any screen size by selecting one of various device configurations or by simply resizing the preview window.
Find opportunities to reduce your Android app size by inspecting the contents of your app APK file, even if it wasn’t built with Android Studio. Inspect the manifest file, resources, and DEX files. Compare two APKs to see how your app size changed between app versions.
Push code and resource changes to your app running on a device or emulator and see the changes instantly come to life. Instant Run dramatically speeds up your edit, build, and run cycles, keeping you “in the flow.”
Intelligent code editor
Write better code, work faster, and be more productive with an intelligent code editor that provides code completion for Kotlin, Java, and C/C++ languages.
Install and run your apps faster than with a physical device and simulate different configurations and features, including ARCore, Google’s platform for building augmented reality experiences.
Flexible build system
Powered by Gradle, Android Studio’s build system allows you to customize your build to generate multiple build variants for different devices from a single project.
The built-in profiling tools provide realtime statistics for your app’s CPU, memory, and network activity. Identify performance bottlenecks by recording method traces, inspecting the heap and allocations, and see incoming and outgoing network payloads.
Note: the newest versions of Android Studio do not offer a Window 32-bit version. Android Studio 3.6.3 was the last to offer a Windows 32-bit version. You can download it here,
Complete release notes can be found here,
New in Layout Inspector: Capture layout hierarchy snapshots
Layout Inspector now allows you to save snapshots of your running app’s layout hierarchy, so that you can easily share them with others or refer to them later.
Snapshots capture the data you would typically see when using the Layout Inspector, including a detailed 3D rendering of your layout, the component tree of your View, Compose, or hybrid layout, and detailed attributes for each component of your UI. To save a snapshot, do the following:
- Deploy your app to a device running API level 23 or higher
- Open the Layout Inspector by selecting View > Tool Windows > Layout Inspector.
- The Layout Inspector should connect to your app process automatically. If not, select the app process from the dropdown menu.
- When you want to capture a snapshot, click Export snapshot from the Layout Inspector toolbar.
- In the system dialog that appears, specify the name and location you want to save your snapshot. Make sure to save the file with a *.li extension.
You can then load a Layout Inspector snapshot by selecting File > Open from the main menu bar, and opening a *.li file.
Support for inspecting Compose semantics
In Compose, Semantics describe your UI in an alternative manner that is understandable for Accessibility services and for the Testing framework. In Android Studio Bumblebee, you can now use the Layout Inspector to inspect semantic information in your Compose layouts.
When selecting a Compose node, use the Attributes window to check whether it declares semantic information directly, merges semantics from its children, or both. To quickly identify which nodes include semantics, either declared or merged, use select the View options dropdown in the Component Tree window and select Highlight Semantics Layers. This highlights only the nodes in the tree that include semantics, and you can use your keyboard to quickly navigate between them.
Document Layout Inspector snapshots
You can now capture snapshots of your app’s layout hierarchy to save, share, or inspect later. Snapshots capture the data you would typically see when using the Layout Inspector, including a detailed 3D rendering of your layout, the component tree of your View, Compose, or hybrid layout, and detailed attributes for each component of your UI. When inspecting the layout of a live running app, click Export snapshot Export
icon from the Layout Inspector toolbar and save the snapshot with an *.li extension. You can then load a Layout Inspector snapshot by selecting File > Open from the main menu bar, and opening a *.li file. The snapshot appears in a tab in the Editor window, so that you can easily compare it with your running app.
New in App Inspection
In Android Studio Bumblebee, there are new tools and functionalities in the App Inspection window. You can open the App Inspector by selecting View > Tool Windows > App Inspection from the main menu bar.
The Network Profiler in the Profilers tool window has now moved to the App Inspection tool window. If you’ve previously used the Network Profiler, all the same features and rich network traffic data is still available. Simply deploy your app to a device running API level 26 and higher and open the App Inspector > Network Inspector tab.
Inspect Jobs, Alarms, and Wakelocks
The Background Task Inspector now allows you to inspect your app’s Jobs, Alarms, and Wakelocks, in addition to the existing support for inspecting Workers. Each type of asynchronous task now appears under the appropriate heading in the inspector tab, allowing you to easily monitor its status and progress. Similar to Workers, you can select a Job, Alarm, or Wakelock to inspect its detailed information in the Task Details panel.
Android Studio Bumblebee supports the wireless debugging feature on Android 11 and higher devices. Pair and deploy your app from Android Studio over Wi-Fi without using a USB cable or managing Android Debug Bridge (adb) connections using the command line. To use, navigate to the Paired devices using Wi-Fi option from the device selection menu, and then either choose a QR code or Pairing PIN Code. Then on your Android 11 and higher device, under Developer options, and find the Wireless Debugging screen and initialize and connect to an adb session wirelessly with Android Studio. Learn more about the wireless debugging setup at Connect to a device over Wi-Fi (Android 11+).
Compose interactive preview enabled by default
Starting with Android Studio Bumblebee, the interactive preview feature is enabled by default. The interactive preview allows you to interact with a preview as it would work on a device. The interactive preview is isolated from other preview in a sandbox environment, where you can click elements and enter user input in the preview. It’s a quick way to test different states and gestures of your composable, like a checkbox being checked or empty.
Previous release notes
Android Gradle Plugin
- lint standalone plugin doesn’t handle gradleApi() dependency properly
- JPS build triggered while Gradle build runs outside of Studio
- Enabling both KSP and Kapt in a project with both containing processors that generate sources breaks BundleLibraryClassesInputs
- UI freezes due to long JniReferencesSearch computation in background
- Allow saving DBs
- Unable to export data using App Inspection/Database Inspector with blank space in path
- Java lambdas cause unexpected behavior when subclassing subclasses
- Cannot constrain type error during r8 minification
- Issue while executing R8 3.0.69 (from AGP 7.0.2) and 3.0.72
Updated version numbering for Android Studio
We have changed the version numbering system for Android Studio to more closely align with IntelliJ IDEA, the IDE that Android Studio is based on.
In the previous numbering system, this release would have been numbered as Android Studio 4.3 or version 188.8.131.52. With the new numbering system, it is now Android Studio – Arctic Fox | 2020.3.1, or version 2020.3.1.
Updated UI for recording in Memory Profiler
We have consolidated the Memory Profiler user interface (UI) for different recording activities, such as capturing a heap dump and recording Java, Kotlin, and native memory allocations.
Updates to Refresh Linked C++ Project
We have moved files unrelated to configuration from the .cxx/ folder into the build/ folder. CMake C++ builds require a configuration phase that generates the Ninja project that’s used to execute the compile and link steps. Projects generated by CMake are expensive to generate and are expected to survive across gradle clean. For this reason, they’re stored in a folder called .cxx/, next to the build/ folder. Typically, the Android Gradle plugin will notice configuration changes and automatically regenerate the Ninja project. However, not all cases can be detected. When this happens, the “Refresh Linked C++ Project” option can be used to manually regenerate the Ninja project.
New test matrix for multi-device testing
Instrumentation tests can now run across multiple devices in parallel and can be investigated using a specialized instrumentation test results panel. Using this panel, you can determine if tests are failing due to API level or hardware properties.