Turn a Figma Make App into an Android App (APK and AAB)

Figma Make turns prompts and Figma designs into web apps, and publishing puts the app on the public web at a figma.site address or your own domain. It has no Android or iPhone export. To get one onto phones, publish it, settle the address you will keep, and wrap that URL into a signed Android APK and AAB.

What publishing gives you

Sources: Figma's Figma Make FAQs and Publish, update, or unpublish a Figma Make file, checked October 3, 2026. Published apps are hosted by Amazon Web Services, with the domain and routing served by Cloudflare. On paid plans you can also export the code and host it yourself; the app then wraps that address instead. On Starter, anyone can remix the Community file, its code and chat history included, and unpublishing the Community page also takes the web app offline, and the Android app's content with it.

Three things to settle before you build

• The address. The App license binds the website's address as well as the package name, so connect your custom domain first if you want one, and enter the address the site ends up on after any redirect between example.com and www.example.com. Custom domains need a paid Figma plan. Figma reuses the same figma.site address when you republish, so that address also works if you keep it.
• Who can open it. The app shows what a visitor's browser shows. With password protection on, every user types the password first. An app limited to your organization needs a Figma sign-in, which opens in the phone's browser, so the app cannot get past it. Publish to anyone on the web, without a password; on Organization and Enterprise plans an admin can turn that off or require passwords, so check with them first.
• Sign-in. When you add a backend, Figma Make connects Supabase for data and sign-in. Email-and-password sign-in runs on your own page and works inside the app. Social sign-in through Supabase, such as Google or GitHub, first goes to your project's supabase.co address, so in the Android app it opens the phone's browser, and the session stays there. Links Supabase emails, such as a sign-up confirmation or a password reset, also open in the browser; people then sign in in the app. Try your sign-in on a phone first, and keep the Supabase project active: Supabase pauses a Free plan project that sees too little database activity in a week, and a paused backend stops sign-in in the app too.

From the URL to an Android app

Figma says Make works best for desktop and full-screen layouts and is still improving mobile output, so ask Make for a phone-width layout and check it on a phone before you buy. Paste the published address into the free preview to see the app in a phone frame. Then create the app with the package name you want to keep and, for Google Play, upload your own keystore before its first build, because the signing key is fixed from that build on. Buy the App license for that app ($69): Release APK and AAB for this website, without the Code2Native watermark. One-time payment. Not on a free Preview of the same site, which is a separate app signed with our shared key. The steps are the same as for any website, in URL to APK. For iPhone, the same license also builds an unsigned IPA on its included credits; sign it before you submit it, and read the App Store review checklist first.