Glideep Documentation

Glideep turns any responsive website into a native Android and iOS app — no coding required. You configure everything through the visual editor, click Build, and Glideep does the rest. This guide walks you through every feature from setup to publishing.

🚀 From zero to published in 5 steps

1. Create an account at app.glideep.com

   Sign up and choose a plan. All plans include a 14-day money-back guarantee.
2. Create a new app

   Enter your app name, the website URL you want to wrap, and optionally your Android package name and iOS Bundle ID.
3. Customize in the Visual Editor

   Set your icon, splash screen, colors, navigation, push notifications, and any other features you need. Every change shows instantly in the live preview.
4. Click Build

   Builds usually take 1–2 minutes and produce a signed APK/AAB (Android) or an IPA that's automatically sent to TestFlight (iOS).
5. Publish to the stores

   Upload the AAB to Google Play Console, or promote your TestFlight build to App Store. Your app is live.

➕ Create Your App

Go to Dashboard → Create New App and fill in the details below. You can always change most of these later from the editor.

🎨 Visual Editor

After creating your app you're taken to the Visual Editor. It has a settings panel on the left where you configure everything, and a live phone preview on the right that updates as you make changes.

The left sidebar groups every setting into tabs:

Changes save automatically a moment after you stop typing — there's no separate Save button. Your settings apply to the next build.

ℹ️ Basic

The foundation of your app — its name, the website it loads, and the store identifiers. You set these when you create the app; this tab is where you edit them afterward.

🖼️ Assets

Your app icon and splash screen — the first things users see, before your site even loads.

App Icon

Auto-fetched from your website when you create the app — click the upload icon on either preview to replace it any time. Square PNG/JPG, 1024×1024 recommended, max 2MB. The editor previews it two ways: an iOS squircle and an Android circle.

Splash Screen

Shown while the app launches, before your site loads.

🎛️ Appearance

Controls how the app's chrome looks — the phone's own status and navigation bars, and whether the app follows light or dark mode.

🧭 Navigation

Glideep lets you add two types of native navigation to your app, configured as two sub-tabs. Both are optional — your website's own navigation always works inside the app regardless.

You can enable one or both at the same time — Bottom Navigation and Side Drawer are separate sub-tabs inside the Navigation tab.

🏠 Home Screen

Optionally show a fully branded native home screen before the WebView loads on launch. It has two sub-tabs: Home Screen (the design) and Store Details (used by its Share & Rate buttons).

Store Details

Powers the home screen's Share and Rate buttons: Android Package Name (Play Store rate link), iOS App ID — the numeric App Store ID (App Store rate link), and Share Text — the message used when a user taps Share.

📋 Onboarding

Onboarding screens are shown the first time a user opens your app. They're great for introducing key features or setting expectations before the main content loads.

🎚️ Features

Core app behaviors — how the WebView responds to touch, screen behavior, content protection, push notifications, and the rating prompt.

Browsing & loading

Screen & security

Push Notifications

Send push notifications directly to your app users. Glideep uses OneSignal — a free service — to deliver notifications on both Android and iOS.

1. Create a free account at onesignal.com

   Create a new app in OneSignal and pick Google (FCM) and/or Apple iOS (APNs).
2. Copy your OneSignal App ID
   In OneSignal, go to Settings → Keys & IDs and copy the App ID.
3. Paste it into the Features tab
   Turn on Enable Push Notifications and paste the App ID.
4. Send your first notification
   In OneSignal, go to Messages → New Push, write your message, and send.

In-App Purchases (RevenueCat)

Sell subscriptions or one-time products through your own store account — Glideep never takes a cut, the money goes straight to you. Handled through RevenueCat, a free-to-start layer over Google Play Billing and Apple StoreKit.

1. Create the product first
   Set up the subscription or one-time product in App Store Connect and/or Google Play Console.
2. Connect RevenueCat
   Sign up free at revenuecat.com, add your app, import those store products, and attach each one to an Entitlement.
3. Add the API key in Glideep
   Copy the Public SDK API key from RevenueCat → Project Settings → API Keys, paste it in the Features tab, and turn on Enable In-App Purchases.
4. List your products
   For each product, add its Product ID (must match the store listing) and the Entitlement name it grants in RevenueCat.
5. Trigger the purchase from your site
   If your site can run custom code, call the JS bridge: window.flutter_inappwebview.callHandler('nativeApp', JSON.stringify({type:'purchase', id:'<product_id>'})) — check status with type:'iapStatus', restore past purchases with type:'restorePurchases'.
   If your site is built on a no-code tool that can't run custom JS (Glide, Base44, Lovable, etc.), just link any button to a URL with ?glideep_iap=<product_id> appended — the app buys the product instead of loading that page.

Rate App Prompt

Show a native in-app rating dialog to encourage reviews. The OS controls exactly when and how the dialog appears — you set the trigger conditions and copy.

🛡️ Permissions

Every toggle here maps directly to a device permission your app can request — camera, location, microphone, and so on. They're all off by default, and each one is tied to real app functionality: turn on only the ones your website or web app actually uses. If a permission is off but your site calls the matching browser API (e.g. it asks for the camera), that feature simply won't work inside the app — the OS never grants access, so there's nothing for your page to use.

🔑 Social Login

Native sign-in providers that hand the session back to your website — Google, Apple, and Facebook.

Session Bridge

Each provider (except Apple) has a Post-login redirect URL — where the app's WebView goes after a successful sign-in. Leave it blank to use your app's home URL.

For passing the native login back into your own web session, set a Cookie Domain (e.g. .example.com) and a Token Set URL — an endpoint on your site that receives the native auth token and sets a web session cookie.

📈 App Insights Firebase

Track crashes, non-fatal errors, screen views, and user activity — all inside your own Firebase Console. Nothing routes through Glideep; you bring your own Firebase project.

⚙️ Advanced

Power-user configuration — hiding elements, controlling which links stay in-app, deep links, biometric lock, and the delete action.

Hide Elements

Comma-separated CSS selectors to hide inside the WebView — e.g. .header, .footer, #banner.

Allowed Origins

Deep Linking

Let external sources (emails, QR codes, social posts) open your app directly to a specific page instead of a browser.

The Advanced tab can generate both verification files for you — Generate & Download next to each platform:

1. Android
   Downloads assetlinks.json, pre-filled with your Package Name and Glideep's signing certificate fingerprint.
2. iOS
   Downloads apple-app-site-association, pre-filled with your Bundle ID.
3. Upload both to your site
   Host them at https://yourdomain.com/.well-known/assetlinks.json and https://yourdomain.com/.well-known/apple-app-site-association (no file extension on the second one). Both must return HTTP 200 with Content-Type: application/json, and /.well-known/ must not redirect — Apple and Google verify the files directly.

Biometric Authentication

Require Face ID / Touch ID (iOS) or Fingerprint / Face Unlock (Android) before users reach the app or specific pages.

Danger Zone

Delete This App permanently removes the app and its configuration. This action cannot be undone.

🗝️ Key Manager

Add your own signing keys for store-ready builds. This is optional — Glideep signs with its own key by default, which works fine for testing.

Both key types are stored encrypted and used only at build time.

⬇️ Build & Download

Pick a platform, set the version, and hit Start Building. Your app usually builds in 1–2 minutes, then you download it right here.

Version numbers

Every app has a Version Name (e.g. 1.0.0) and a Version Code (an integer, e.g. 1). When you publish an update, the Version Code must be higher than your last submission — bump both before triggering a new build for a store update.

▶️ Publishing to Google Play

You need a Google Play Developer account ($25 one-time fee) to publish your app.

1. Create the app in Play Console

   Create app → fill in the app name, language, and type. Then complete the required sections: store listing, content rating, privacy policy, and app access.
2. Enroll in Play App Signing

   Production → Setup → App integrity. Enroll so Google manages your signing key — required for new apps.
3. Create a new release and upload the AAB

   Production → Create new release. Upload the .aab from the Build & Download tab and add release notes.
4. Submit for review

   Review release → Submit. Google typically reviews new apps within 1–3 days.

🏪 Publishing to the App Store

After a successful iOS build, your app is automatically uploaded to TestFlight. From there you test it, then submit it to the App Store.

1. Find your build in TestFlight

   Go to appstoreconnect.apple.com → TestFlight. Your build appears within a few minutes of the Glideep build finishing.
2. Test on a real device

   Install TestFlight on your iPhone, add yourself as an internal tester, and verify key flows — login, navigation, purchases.
3. Create a new App Store version

   App Store Connect → My Apps → [your app] → Distribution → Add Version. Set the version number, add release notes, and add at least two sets of screenshots (6.5" and 5.5" iPhone sizes).
4. Select your TestFlight build

   On the version page, under Build, click "Select a build before you submit" and choose the build you tested.
5. Submit for review

   Add for Review → Submit to App Review. Apple's review typically takes 1–3 business days.

Need help with publishing? Our Studio service handles everything end-to-end.