Developing Android Mobile Devices
Here’s a clean, end-to-end setup you can follow to turn any PC/Mac/Linux box into a full Android app development rig, from “nothing installed” to “build, run, test, sign, and publish”.
1) Check your machine meets the basics
-
OS & CPU (64-bit required):
-
Windows 10/11 (64-bit), macOS 12+, or 64-bit Linux.
-
RAM: 8 GB minimum; 16–32 GB recommended if you’ll use the Emulator a lot.
-
CPU: Recent Intel/AMD or Apple Silicon; virtualization enabled for fast emulators. Android Developers
-
-
Why it matters: Android Studio + Emulator are heavy; hardware acceleration gives big speedups. Android Developers
2) Install Android Studio (the official IDE)
-
Download Android Studio and run the installer. Android Developers
-
Follow the first-run wizard; let it install:
-
Android SDK
-
Android SDK Platform-Tools (adb/fastboot)
-
Android SDK Build-Tools
-
Android Emulator
(You can always add/remove later in Tools ▸ SDK Manager.) Android Developers+1
-
Tip: Android Studio bundles a compatible JDK—no separate Java install needed for typical Android/Kotlin projects.
3) Configure essential SDK components
Open Tools ▸ SDK Manager:
-
SDK Platforms tab: install the latest stable Android SDK (e.g., Android 15 / API 35) plus whatever older APIs you need for testing.
-
SDK Tools tab: ensure Android SDK Platform-Tools, Build-Tools, Android Emulator, and (optionally) NDK (Side by side) and CMake for any C/C++ code. Android Developers+2Android Developers+2
4) Make emulators fast (hardware acceleration)
-
Windows: use the built-in VM acceleration (WHPX/AEHD). If you previously enabled Hyper-V and have issues, see the acceleration guide to ensure the Emulator uses the right backend. Android Developers+1
-
macOS: uses Apple’s Hypervisor.Framework automatically (great on Apple Silicon).
-
Linux: ensure virtualization (VT-x/AMD-V) is enabled in BIOS/UEFI. Android Developers
Create a device in Device Manager (AVD Manager) and choose a system image (x86_64 or arm64, matching your host). Android Developers
5) Set up a physical device (optional but recommended)
-
On your phone, enable Developer options (tap Build number 7×), then enable USB debugging (or Wireless debugging). Android Developers
-
Windows only: install the Google USB Driver (or your OEM driver) via SDK Manager ▸ SDK Tools ▸ Google USB Driver. Android Developers+2Android Developers+2
-
Verify with
adb devices
(should list your device). Android Developers
6) Command-line tools you’ll actually use
These install with the SDK and are handy in CI or power workflows:
-
adb (device & emulator control), fastboot (bootloader), sdkmanager/avdmanager (headless SDK & AVD install), bundletool (builds/play-tests App Bundles). Android Developers+1
7) Languages & UI toolkit
-
Kotlin is first-class for Android; Android Studio has Kotlin built in. For modern UI, use Jetpack Compose. Android Developers+2Kotlin+2
8) Build system
-
Android uses Gradle with the Android Gradle Plugin (AGP). Keep AGP & Gradle within supported version pairs (AGP major bumps require a Gradle bump). Android Developers+1
9) Create your first project (sanity check)
-
New Project ▸ Empty Views Activity or Empty Compose Activity.
-
Pick a Package name, Save location, Language: Kotlin, Minimum SDK (e.g., API 24+).
-
Click Run on an AVD or your physical device.
If it launches, your toolchain is good.
10) Testing & quality
-
Unit tests: JUnit. UI tests: Espresso / UI Automator. (Setup is part of standard templates in Android Studio.)
-
Lint & inspections: Android Lint is built in; run before releases.
11) App signing & release (Play-ready)
-
Android requires apps to be digitally signed. For Google Play, you should use Play App Signing (Google manages the app signing key; you keep the upload key). Configure in Play Console when you first publish. Android Developers+1
-
Upload format: Google Play expects .aab (Android App Bundle); Play generates per-device APKs. Play App Signing is required for new apps using AAB. Android Developers
-
Some Google APIs (e.g., Maps, Sign-In) need your SHA-1—get it from Play Console (if using Play App Signing) or via
keytool
/Gradle’ssigningReport
. Google for Developers
12) Target & minimum SDK (Play requirements in 2025)
-
For new apps & updates after Aug 31, 2025, Play requires targetSdk = 35 (Android 15) or higher (different rules for Wear/Auto/TV). Existing apps must target at least API 34 to remain available to new users on newer devices; extensions to Nov 1, 2025 were offered. Set this in
module ▸ build.gradle(.kts)
. Android Developers+2Google Help+2
13) (Optional) Native code toolchain
If you need C/C++:
-
Install NDK (Side by side) and CMake from SDK Manager ▸ SDK Tools. Android Studio will place the NDK under
…/android-sdk/ndk/
. Android Developers+1
14) (Optional) Useful add-ons
-
Version control: Git (GitHub/GitLab/Bitbucket).
-
Cross-platform frameworks: Flutter or React Native devs still use the Android SDK, AAB signing, and Play requirements when targeting Android. Flutter Documentation+1
Quick checklist (copy/paste and tick off)
-
OS is 64-bit; virtualization enabled; RAM ≥ 16 GB preferred. Android Developers+1
-
Installed Android Studio and default SDK components. Android Developers
-
Added latest SDK Platform, Platform-Tools, Build-Tools; created a fast AVD. Android Developers+1
-
(Device) Enabled USB/Wireless debugging; on Windows, installed Google USB Driver. Android Developers+1
-
Project builds & runs (Kotlin/Compose recommended). Android Developers
-
Release pipeline: Play App Signing set; building AAB; upload key secured. Android Developers+1
-
targetSdk
meets current Play policy (API 35 as of Aug 31, 2025). Android Developers
Comments
Post a Comment