What it is
Figma Make turns prompts and Figma designs into working web apps and prototypes you can publish. Designers who already live in Figma and want the working build in users' hands, not just in a review link.
Start here
Figma Make app → App StoreStep by step from the published Figma Make URL to the App Store listing, with the Figma Make-specific checks.Figma Make app → Google PlayThe Android walkthrough for Figma Make apps, including the Play Console setup and the 12-tester rule.Figma Make: App Store + Google PlayBoth stores from one URL: differences, costs and the parallel plan.Figma Make app rejected: fixesRejected? The triage for Figma Make apps, the usual reasons and a reply template.
Native features for Figma Make apps
Each feature page explains the native part (one setting or one URL call) and the web-app part for your Figma Make stack, with a prompt to paste.
Push notificationsBrowser web push on iOS only works for home-screen web apps and most users never see it. As a native app built with WebViewGold, your Figma Make app gets the real thing: system push notifications on iOS and Android, sent from your backend, from a dashboard, or scheduled by your own JavaScript.Google login and Sign in with AppleFigma Make apps typically use Supabase Auth via the Figma Make integration, or none for content apps. Email and password login works unchanged inside a WebViewGold app. Google and other OAuth providers block embedded WebViews, and Apple adds a rule of its own. Here is how to make every login method work in the app without changing your auth code.
Figma Make at a glance
Stack
React + Tailwind CSS generated by Figma Make, optional Supabase integration for auth and data
Publishing and hosting
Click Publish in Figma Make to get a public figma.site link for your app. Publish again to ship changes.
Authentication
Supabase Auth via the Figma Make integration, or none for content apps
Payments
Stripe (via Supabase functions or after export)
Builder badge
No builder badge to remove.
Example: from Figma Make project to approved app
Say you designed an exhibition guide for a local art gallery in Figma Make: one page per artwork with audio commentary, artist bios and a floor plan. You publish it to a figma.site link, connect guide.yourdomain.com and wrap it with WebViewGold, turning on the native QR scanner so visitors scan the code next to each piece to open its page. Because some rooms have poor reception, you bundle the most visited pages as an offline fallback. You replace the last placeholder bios before submitting, since Apple rejects incomplete content. Both stores approve the app, and each new exhibition goes live with a Publish in Figma Make.
Your first week after launch
- Change texts and images in Figma Make and publish; the app shows them on next launch.
- Update the bundled offline pages only with your next store build, since they ship inside the app.
- Send a push when a new exhibition opens or a talk is about to start, linked to its page.
- Check the published site on a small Android phone; layouts designed on a large canvas often need a tighter mobile breakpoint.
- Ask for a rating with rateapp:// after a visitor has scanned several artworks.
Store-readiness prompt
Paste into Figma Make, review the changes, publish.
Prompt to paste into Figma Make
Prepare this app for publishing as a native iOS and Android app (it will run inside a native WebView wrapper): replace all placeholder content with real content; make every button and link functional; add /privacy and /terms pages linked from the footer; make all screens responsive from 320px to tablet widths with 44px tap targets; remove external promotional links; add an empty/retry state for failed data loads; set the title to the app name (max 30 characters).
What you get with WebViewGold
A complete native app project, not a subscription. Everything below is included in the license and switched on with a setting.
- Native app project
- Push notifications
- Offline screen
- App icon & splash screen
- Share sheet & haptics
- Deep & universal links
- In-app purchases
- Free updates, white-label
Frequently asked questions
Can a Figma Make app be published in the App Store?
Yes. Publish the app, insert its public URL into WebViewGold for iOS and submit the native build. The same URL powers the Android app. Make sure the app is complete, not a clickable prototype.
Do I need to export the code from Figma Make?
No. WebViewGold loads the published URL. Export only if you want a custom domain or your own hosting.
Can a Figma Make app with mock data pass review?
Usually not. Reviewers test whether features work, so a login that accepts anything or a list that never saves fails Guideline 2.1. Add the Supabase backend through Figma Make's integration so data really persists, or remove the feature until it works.
Do I need a custom domain for my Figma Make app?
Not for WebViewGold, the published figma.site link works. A custom domain is still worth setting up before submission, because the URL is compiled into the app and your own domain lets you move hosting later without a new store build.
Three ways to get your app into the stores
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
Do it yourself
$109 per platform, one-time
The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.
See plans on the main pageCloud Builder
$349 per license, one-time add-on
No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.
How the Cloud Builder works Try the free demoFull Service
$698 per platform $798
Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.
Full Service details Powered by
Winter Sale prices valid until December 31, 2026.