Developing applications for the Android platform inevitably leads to a moment when the code needs to be turned into a finished product that is understandable to the operating system. The file with extension .apk (Android Package Kit) is a standard container containing all the necessary code, resources, certificates and application manifest. Without this stage, it is impossible to test on real devices or transfer the project to the customer for verification.
Modern development environment Android Studio provides powerful tools for automating the assembly process, but beginners often face difficulties finding the necessary settings. It is important to understand the difference between the debug version for testing and the release version for publication. Incorrect configuration can lead to the application simply not being installed on the phone or working unstable.
In this article we will analyze in detail the entire path from writing code to receiving a ready-made installer. We'll look at settings Gradle, managing signatures, and choosing the right build options. You'll learn how to avoid common mistakes and optimize the final file size for quick downloads by users.
Preparing the development environment and project structure
Before you start compiling, you need to make sure that your project is configured correctly. Android Studio uses a build system Gradle, which manages dependencies and the code compilation process. If the file build.gradle has syntax errors or library version conflicts, the APK creation process will be interrupted at the initial stage.
Pay attention to the folder structure of your project. The source code should be in the directory src/main/java, and the resources in src/main/res. Any deviation from the standards may result in the compiler not finding the required classes or images. Also check the file AndroidManifest.xmlas it contains critical information about access rights and entry points into the application.
Make sure you have the latest version Android SDK Build-Tools. Legacy build tools may not support new language features Kotlin or Javawhich will cause compilation errors. In the SDK manager, you can check the presence of all the necessary components and update them to the latest stable versions.
⚠️ Attention: The Android Studio interface is updated regularly. The location of some menus and the names of items may vary slightly in different versions of the IDE. Always check the official documentation if you can't find the item you need in the menu.
Before starting the build, run the Clean Project command in the Build menu to remove old temporary files that may conflict with the new compilation.
Configuring Build Variants
One of the key concepts in the Android ecosystem is division of assemblies into debug and release. By default, Android Studio creates a debug variant (debug), which is signed with an automatic key and contains debugging information. This mode is convenient for development, but is not suitable for final distribution.
To switch between modes, use the panel Build Variants, usually located in the lower left part of the IDE window. Here you can select the active build option for each module of your application. Selecting a mode release activates code optimization, enabling ProGuard or R8 for obfuscation and removal of unused resources.
- 🛠️ Debug —mode for development, includes logging and debugging, does not require manual signature.
- 🚀 Release —optimized mode for publication, requires a digital signature of the developer.
- 🧪 Staging —intermediate mode for testing before release, often used in large projects.
When selecting the mode release the system will require you to configure a signature. Without a valid security key, the Android operating system will not allow the application to be installed on the user's device. This is a security mechanism that ensures that application updates come from the same author as the original version.
The compilation process and file generation
The process of creating the installation package itself is launched through the main menu of the development environment. You need to go to section Build and select item Build Bundle(s) / APK(s). Here the system will offer two main options: creating a regular APK or modern format Android App Bundle (AAB).
Format .aab is preferable for publishing on Google Play, as it allows the store to generate optimized APKs for specific user devices. However, for manual installation on your phone or distribution through third-party platforms, you will need a classic .apk file. Select the option Build APK(s) to start the process.
Build -> Build Bundle(s) / APK(s) -> Build APK(s)A build progress indicator will appear in the bottom panel. Android Studio During this time, Gradle performs many tasks: compiling Java or Kotlin code into bytecode, processing resources, merging manifests, and signing the resulting file. The execution time depends on the power of your computer and the complexity of the project. DEX, processing resources, merging manifests and signing the resulting file. The execution time depends on the power of your computer and the complexity of the project.
⚠️ Warning: If you changed the Gradle configuration files during the build, the process may require synchronizing the project. Do not interrupt the synchronization process to avoid damage to the build cache.
☑️ Check before building
Searching and extracting the finished APK file
After successful completion of compilation, a pop-up notification with a link will appear in the lower right corner of the screen locate. Clicking on this link will automatically open a file explorer in the folder where the generated installer is located. This is the fastest way to find the file you need among the many project service data.
If you missed the notification, the file can be found manually in the project directory structure. The path to the file usually looks like this: app/build/outputs/apk/. Inside this folder there will be subdirectories corresponding to the selected build options (for example, debug or release) and the type of processor architecture.
| Build type | File path | File name | Size |
|---|---|---|---|
| Debug | app/build/outputs/apk/debug/ | app-debug.apk | Larger (uncompressed) |
| Release | app/build/outputs/apk/release/ | app-release.apk | Smaller (optimized) |
| Universal | app/build/outputs/apk/release/ | app-release-universal.apk | Largest |
Please note that the file name may vary depending on the settings applicationId and versions specified in build.gradle. Always check the modification date of the file to ensure that you are copying the version you just built and not an artifact of a previous compilation.
What if the file is not found?
If the file is not in the outputs folder, check the build console for errors. The process may have failed and the file was not created. Also check if exclusion of the build folder is enabled in your antivirus settings.
Signing the application with a digital certificate
Each APK file must be cryptographically signed before installation. For debug versions Android Studio uses a temporary key debug.keystorewhich is stored in the user profile. This key is convenient for testing, but cannot be used to publish applications in stores.
To create a release version, you must generate your own key through the signing wizard. Select Build -> Generate Signed Bundle / APKfrom the menu. The wizard will prompt you to create a new keystore (Keystore), where you need to specify the password, _alias_ and owner information. Keep this file in a safe place, as losing it will make it impossible to update the application in the future.
The signing process ensures the integrity of the code. If someone tries to change the contents of the APK after signing, the digital signature will become invalid and the Android system will refuse to install such an application. This is a fundamental mechanism security of the platform.
The loss of the Keystore file and passwords for it makes it impossible to release updates for an already published application on Google Play.- 🔐 Alias —an alias for the key inside the storage used for identification.
- 📅 Validity — key validity period, it is recommended to set it to 25 years or more.
- 🏢 Certificate — data about the developer included in the certificate.
Never use a debug key to publish an application in stores. Create a separate release key and save a backup copy in cloud storage.
Installation and testing on the device
The resulting file can be transferred to a smartphone in any convenient way: via a USB cable, cloud storage or instant messenger. Before installation, make sure your device allows installation of applications from unknown sources. This setting is located in the system security section and may be called Unknown applications.
When you first launch a signed release application, the system may request confirmation of installation, warning about potential risks. This is standard procedure for any APK not downloaded directly from the official store. After confirmation, the application icon will appear in the launcher.
For advanced developers, installation via ADB (Android Debug Bridge) is useful. This method allows you to quickly deploy an application on a connected device or emulator with one command from the terminal. It is especially convenient for frequent iterations of development and testing.
adb install -r app/build/outputs/apk/release/app-release.apkThe flag -r in the command means replacing an existing application while preserving its data. This allows you to update the test version without losing user-entered settings or game progress. If the application does not install, check the logs using the command adb logcat to diagnose the error.
⚠️ Attention: When installing an APK signed with a different key over an existing application, the system will require you to completely remove the old version. All local application data will be irretrievably lost.
Use the Android Studio emulator to test the APK initially before installing it on a physical device. This will save time and protect the main phone from potential failures.
Solving common build problems
When creating an APK, developers often encounter errors related to the Gradle process being out of memory or library version conflicts. If the build fails with an error OutOfMemoryError, you need to increase the amount of allocated memory in the file gradle.propertiesby adding the line org.gradle.jvmargs=-Xmx2048m.
Another common problem is a mismatch between the version SDK in the project and installed on the system. The error can be solved by specifying the correct path in the file or through the project settings in the project itself. Make sure that the paths do not contain Cyrillic characters, which sometimes causes problems in older versions of the tools. SDK location not found can be solved by specifying the correct path in the file local.properties or through the project settings in the Android Studio. Make sure that the paths do not contain Cyrillic characters, which sometimes causes problems in older versions of the tools.
If the application installs but immediately closes (“crashes”), check Logicat. A common cause is missing required permissions in the manifest or accessing resources that were not included in the build due to compression settings. In such cases, disabling code minification during debugging helps.
Why is the APK file not installed on the phone?
The most common reasons: installation blocking from unknown sources is enabled, the file is damaged during download, the Android version on the phone is lower than the minimum required (minSdkVersion), or the application is already installed with a different signature.
What is the difference between APK and AAB?
APK is a ready-made installation file for a specific device. AAB (Android App Bundle) is a publishing format for Google Play that allows the store to dynamically generate optimized APKs for each user, reducing the download size. Is it possible to create an APK without Android Studio? Yes, using the command line and Gradle directly, or other IDEs such as IntelliJ IDEA. There are also online compilers for simple projects, but for professional development Android Studio is the standard.
Is it possible to create an APK without Android Studio?
Yes, using the command line and Gradle directly, or other IDEs such as IntelliJ IDEA. There are also online compilers for simple projects, but for professional development Android Studio is the standard.
How to reduce the size of an APK file?
Use resource compression (shrinkResources), code obfuscation (minifyEnabled true), remove unused libraries and support only necessary processor architectures (ABI splits).
Where is debug.keystore stored?
By default, it is located in the user folder: Windows (~/.android/debug.keystore), macOS (~/.android/debug.keystore), Linux (~/.android/debug.keystore). The default password is usually "android".