How to run your app on a real phone — step by step for Android and iPhone

One detail almost nobody warns you about: you can put your own build on an iPhone for free, without the $99 a year — and it will stop opening after exactly seven days. It won't break or disappear; one day it simply refuses to launch, because the free profile expired. On Android there's no such clock at all. Let's walk through running your app on a real phone on both platforms — and what to expect from each.
Why bother, if there's an emulator
Emulators are great for "that button landed wrong." But three classes of problems never show up there:
- Speed. Your laptop is several times faster than a phone. A list that glides in the emulator can stutter on real hardware.
- Gestures and hit targets. A finger is fatter than a cursor. A 30×30 button taps perfectly with a mouse and takes three tries with a thumb.
- Anything touching hardware or the OS. Camera, haptics, notifications, the screen notch, face unlock, what happens during an incoming call.
Plus the big one: only on a real phone do you first see the app the way a user sees it — with no development window framing it.
Android: four steps
- Turn on developer mode. Settings → "About phone" → tap "Build number" seven times. You'll get a "You are now a developer" toast, and a "Developer options" entry appears in Settings (sometimes under "System").
- Enable USB debugging. Settings → "Developer options" → the "USB debugging" switch.
- Plug in the cable and accept the key. On Android 4.2.2 and above, the first connection pops a dialog with your computer's RSA key. You must unlock the phone and tap Allow — without that, the computer won't see the device. Ticking "always allow from this computer" is convenient.
- Run it. In Android Studio pick the phone from the device list and hit Run. To check from a terminal, run
adb devices— your phone should be listed asdevice, notunauthorized.
Without a cable. From Android 11 on, wireless debugging works: phone and computer on the same network, enable "Wireless debugging" in Developer options, then in Android Studio choose "Pair Devices Using Wi-Fi" and scan the QR code (or type the six-digit code shown on the phone). You pair once — after that the device connects on its own.
iPhone: four steps
- Sign into Xcode with a regular Apple ID. Xcode → Settings → Accounts → add your account. A "Personal Team" appears — that's the free tier, no paid membership needed. Select it as the Team in your project settings.
- Connect the phone and target it. Cable to the Mac, unlock, answer "Trust This Computer." In Xcode's toolbar pick your iPhone instead of a simulator.
- Turn on Developer Mode. From iOS 16 the build won't launch without it: Settings → "Privacy & Security" → "Developer Mode" → switch on, and the phone will ask to restart and confirm once more after booting. The catch: the menu item only appears after the phone has been connected to Xcode at least once — if you can't find it, do step 2 first.
- Trust your own certificate. On first launch iPhone will say the developer isn't trusted. Settings → "General" → "VPN & Device Management" → pick your Apple ID → "Trust."
What you get — and where the free tier ends
The app sits on your phone and launches like any other, no Xcode attached. Then the free Personal Team limits kick in, and it's better to know them upfront:
- The profile lives 7 days. After a week the app stops opening — rebuild and reinstall from the Mac.
- Up to 3 devices per platform and up to 10 app identifiers at a time.
- You can't hand it to anyone. Free mode means your devices, from your computer, only.
The moment you need to give a build to someone else, you're into the paid Apple Developer Program and TestFlight. Android has no such fork: a built .apk can simply be sent to a person, who installs it by hand after allowing unknown sources.
If the phone doesn't show up
A short checklist, most common first:
- The cable. Half the cases. Cheap cables are often charge-only, no data. Try another.
- The phone is locked. Both Android and iOS show the trust dialog only on an unlocked screen. Unlock and reconnect.
- The dialog wasn't accepted. On Android check
adb devices:unauthorizedmeans the RSA key wasn't approved — unplug, replug, and watch the phone's screen. - Developer Mode is off (iOS 16+) or USB debugging is off (Android). Recheck step 3 in your section.
Can I do iPhone builds without a Mac?
Building for iOS requires macOS — Apple's requirement, and there's no local way around it. The options are indirect: cloud macOS machines and CI services that build the project on their side. For Android any operating system will do.
The app installs but closes instantly — now what?
Read the logs from the connected device: Logcat in Android Studio, the console in Xcode. A crash on launch almost always writes its reason there. A common vibe-coding story: the app reaches for keys and data that aren't on the device — they stayed in environment variables on your computer.
Do I need a signing key for this?
Not for testing — debug builds are signed automatically. But remember that debug and store builds carry different keys, so one won't install over the other. Why that is — see the piece on app signing.
The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.





