Figma Make + login
Figma 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.
From $109 one-time per platform, or let our team do it all from $698.
Google refuses OAuth inside embedded WebViews. WebViewGold's Social Login Helper detects the Google (and Facebook) login URL and runs that step in a dedicated login window with an accepted user agent, then returns to your app. One setting, no changes in Figma Make.
If the iOS app offers Google, Facebook or GitHub login, Apple requires an equivalent privacy-friendly option, typically Sign in with Apple. Enable the Apple provider in Supabase Auth via the Figma Make integration, or none for content apps, add the button, and WebViewGold handles the appleid.apple.com flow automatically.
Email magic links and password resets open in Safari or Chrome instead of the app. Universal Links (iOS) and App Links (Android) in WebViewGold route links to your domain into the app and keep the session there.
Paste this into Figma Make to implement the web-app side. Review the result, publish, then test inside the WebViewGold app.
Prepare the sign-in flow for the WebViewGold app wrapper around this Figma Make app. Change the email login from a magic link to a six-digit code: call Supabase signInWithOtp, then show a code entry screen that calls verifyOtp with type email, in the same visual style as the existing screens. Add a Continue with Apple button next to Continue with Google using the Supabase Apple provider. Add a Delete my account option in the profile screen with a confirmation step that calls a Supabase edge function delete-account, which removes the user's rows and auth account, then signs out. Keep every button functional, no placeholder screens, and link a /privacy page from the login screen.
With a good optimized version of your web app you can have a stunning mobile app within a couple of minutes. Additionally to that the customer service is very nice and very helpful! I can just recommend WebViewGold :-)
About 30 minutes, mostly in the store dashboards.
In Config.swift set google_login_helper_triggers (accounts.google.com) and facebook_login_helper_triggers; on Android use GOOGLE_LOGIN_HELPER_TRIGGERS in Config.java. Test the login inside the app.
Create a Services ID and key in the Apple Developer portal, enable the Apple provider in Supabase Auth via the Figma Make integration, or none for content apps and add a "Continue with Apple" button next to Google. Nothing to configure in WebViewGold.
Host the apple-app-site-association and assetlinks.json files on your domain, enable Universal Links / App Links in WebViewGold and make sure the auth redirect URL in Supabase Auth via the Figma Make integration, or none for content apps points to your domain. See the deep-link guide.
Apple (5.1.1) and Google require in-app account deletion for apps with sign-up. Add a Delete account button that calls a backend function. See the account deletion guide.
In App Store Connect (App Review Information) and the Play Console (App access) enter test credentials so reviewers can see the logged-in experience.
bioauth://). Gate the app on launch or protect sensitive screens.No. The Social Login Helper works on the native side by detecting the OAuth URLs. The only additions are the Sign in with Apple provider (required by Apple if you offer other social logins) and, for magic links, the domain files for Universal Links.
Only if your iOS app offers a third-party login such as Google, Facebook or GitHub. If users can only sign in with email and password or magic link, Guideline 4.8 does not apply.
Google blocks OAuth in embedded WebViews for security reasons (the host app could read the credentials). The Social Login Helper runs the Google step in a trusted window that Google accepts and hands the session back to your app.
Yes. WebViewGold persists cookies and local storage, so Supabase Auth via the Figma Make integration, or none for content apps sessions behave as in the browser.
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
$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 page$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 demo$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.
App Store & Google Play approval guarantee – or your money back within 14 days
Rather hand it over? Full Service: we configure, build and deliver within 72 hours, from $698 per platform. Questions? Chat with us 24/7.
Refunds are granted under the conditions listed in our FAQ: a non-content rejection by Apple and/or Google, claimed within 14 days after purchase.