ApkRunner
Developers · testers · clients · iPhone and iPad

Test an APK on an iPhone

An iPhone can't install an APK, but it can run one: the build runs on a real Android™ 12–15 device in the cloud and you use it in Safari. Choose the APK your developer sent, sign in, and the app opens in a minute or two. Sending the build? The checklist is below.

Free minutes · Google sign-in · no card
Drop an APK here Run an APK .apk .xapk .apks .apkm

For the person with the iPhone

You got an APK by email, chat or a Drive link and have no Android phone. Nothing is installed on the iPhone, and everyone who should see the build does the same on their own device. More on Safari, iPad and the home-screen icon: run APK files on an iPhone.

Save the APK to Files

In Mail, Gmail, WhatsApp or Slack, tap the file, then Share → Save to Files. From a Drive or Dropbox link, download it in Safari: it lands in Files → Downloads.

Choose it here

Tap Choose file above, then Choose File in the menu iOS shows. The APK is checked on the iPhone first: name, package, version, the Android it needs and whether it will run. If it is refused, send the reason to the developer: it says what to fix.

Sign in and use it

Apple or Google gives 15 free minutes, an email code 3; no card. Tap, type with the Keyboard button, turn the iPhone for landscape. The iPhone's own screenshot captures the app for your feedback.

For the developer sending the build

The same checks run in the browser before anything is uploaded, so you can drop the file into the APK viewer on your computer and see what your client will see.

  • Signed. A debug build (./gradlew assembleDebug, or Build APK(s) in Android Studio) is signed with the debug key and runs. Refused: an APK with no signature at all, as some "unsigned" exports from build tools and game engines are, or one rebuilt with apktool; and one with only the old v1 (JAR) signature that targets Android 11 (API 30) or later. apksigner or uber-apk-signer fixes both.
  • An APK, not an App Bundle. .aab files don't run here. bundletool build-apks --mode=universal writes an .apks with one universal.apk inside: send that APK. Split APKs can also go as one .xapk, .apks or .apkm file.
  • minSdk 35 or lower. The devices run Android 12 (API 31) to 15 (API 35); versions below your minSdk are greyed out. Any targetSdk installs, old ones included.
  • ARM code, or none. arm64-v8a runs everywhere; a 32-bit armeabi-v7a-only build runs on our devices in Europe; an app with no native code runs anywhere. x86- or x86_64-only builds are refused.
  • Up to 1 GB on free minutes, 2 GB on a paid plan.
  • A backend it can reach. The device is in a data center: localhost, 10.0.2.2 and your office network are out of reach. Point the build at a public staging server.
  • A way in without Google. The device has microG in place of Google Play services, so Google sign-in, Google Play purchases and Play Integrity checks may not work. Give your client an email-and-password test account, or a build that skips those checks. The APK check flags apps that use Play services.

What you can check from an iPhone

Enough for a client to sign off on screens and flows, or for you to see a bug report for yourself.

Android 12 to 15

Choose the version at each start and see the same build on Android 12, 13, 14 and 15.

Three phone sizes

Small phone, phone and large phone screens, and landscape when the iPhone turns: the usual places for layout bugs.

Real input

Taps, swipes, text from the iPhone's keyboard and the app's sound. Forms and menus feel like a phone; fast games show the stream's delay.

Your staging server

The device is online, so the app talks to your public API, and links and web views open as they would on a phone.

Updates, on a paid plan

The phone is kept between sessions with its apps, data and sign-ins: install once, come back tomorrow, and upload the next build over it to test an update.

Logs on a computer

Logcat (filtered to your app, saved to a file), screenshots and screen recording are under Tools in the online emulator on a computer. AI coding agents get the same devices through the MCP server.

What to check on a real phone instead

  • Speed and graphics: the device draws in software on a server and reaches you as video, so frame rates and jank say little about a phone.
  • Camera and Bluetooth: the device has neither.
  • Google sign-in, Google Play Billing and Play Integrity, which microG may not pass.
  • Permission prompts: runtime permissions are granted when the app installs, so the first-run dialogs don't appear.
  • What differs on one maker's phones, Samsung's or Xiaomi's: the device runs plain Android.

Other ways to put an Android build in front of someone

Each suits a different job. Here the person with the iPhone needs only the APK and this page, and nothing is set up on your side.

Test distribution

Firebase App Distribution and Google Play's testing tracks deliver builds and updates to testers, who install them on an Android device of their own.

Hosted app previews

Services such as Appetize take builds from the developer, often from CI, and share links that stream the app to a browser: made for teams that demo and support apps every week.

Real-device clouds

BrowserStack, LambdaTest and the like offer many physical phone models, test automation and team plans, for QA departments.

Simple pricing

Start with free minutes, no card. Paid plans differ only in how long they last. One account for this site and the Chrome extension.

Free

$0

Free minutes to try it

Start free
  • One session or several
  • Android 12–15
  • Phone screens at 20 fps
  • Logcat and recording

7-day pass

$3.99 once

One payment, no subscription

  • Everything in Free, plus
  • 7 days of access
  • Sharp 2× video at 30 fps
  • Foldables and tablets
  • Priority in the queue
  • Your phone kept for next time

Monthly

Most popular
$9.99/month

Cancel anytime

  • Everything in Free, plus
  • A month of access
  • Sharp 2× video at 30 fps
  • Foldables and tablets
  • Priority in the queue
  • Your phone kept for next time

Yearly

Save 40%
$5.99/month

$71.90 billed yearly

  • Everything in Monthly, plus
  • The lowest price a month
  • One payment a year

Prices in US dollars, taxes included. Fair use on paid plans: past about 30 hours a month, sessions still run, after other paid ones. The cloud device has microG in place of Google Play services.

Testing an APK on iPhone: FAQ

Can I test an APK on an iPhone?

Not by installing it: iOS runs only iOS apps. You can run it on a real Android device in the cloud and use it in Safari on the iPhone or iPad: choose the APK on this page, sign in, and it opens on Android 12 to 15. It needs iOS or iPadOS 16.4 or later.

My developer sent me an APK. How do I open it on my iPhone?

Save it to Files (Share → Save to Files), open this page in Safari, tap Choose file and pick it. After a sign-in with Apple, Google or email, the app opens on a cloud Android device in a minute or two.

Can I send my client a link to the running app?

No: there is no link that opens your device for someone else. Send the APK and this page's address instead. Your client signs in, runs the APK on a device of their own and gets free minutes for a first look.

Why is my APK refused as not signed?

Android installs only signed APKs, so the check refuses one with no signature, and one with only a v1 signature that targets Android 11 or later. A debug APK from Android Studio is signed with the debug key and runs; apksigner or uber-apk-signer signs any other.

Will Google sign-in and in-app purchases work?

The device has microG in place of Google Play services. Most apps that use them run, but Google sign-in, Google Play purchases and Play Integrity checks may not. For a client demo, use a test account with an email and password.

Can the app reach our test server?

If the server is on the internet, yes. The device is in a data center, so localhost, 10.0.2.2 and servers inside your office network or VPN are out of reach.

Is a private client build safe to upload?

Before you sign in the APK does not leave the iPhone: it is checked on this page. Then it is uploaded only to start your own device and is deleted from our servers after an hour. The device is yours alone and is wiped when the session ends, unless a paid plan keeps it for you. See the privacy policy.

Does the person testing need to pay?

Not to start, and no card: Apple or Google sign-in gives 15 free minutes, email 3, one free allowance per device. Longer reviews and a phone kept between sessions are under pricing.

Your free minutes are up

Choose a plan to keep this device going. The device waits , then the session ends.

Keep this phone?

Ending the session wipes this phone: the apps you installed and the accounts you signed in to are gone.

Paid plans keep your phone as it is: next time it starts where you left it.

Confirm your plan

    Includes:

    You will finish the payment with our payment provider. Prices in US dollars, taxes included.