Framer makes beautiful sites. It has no path to the App Store or Google Play. Shastra wraps your published Framer site in a native Android and iOS app — animations intact, push notifications included, real App Store listing under your name.
Free Android APK build to start. No card needed. 14-day money-back guarantee.
Framer's answer has always been: figure it out yourself. These are the problems that creates for designers, agencies, and founders who built on Framer.
This is not a missing feature — it is a deliberate product choice. Framer publishes to the web. The App Store and Google Play require a compiled binary file (.ipa / .aab), a developer account, code signing certificates, and a review process. Framer does none of this, and provides no official workaround.
Framer lets you enable a PWA manifest. A user can "add to home screen" on an iPhone or Android. This creates a bookmark that opens a browser tab. It does not appear on the App Store. It does not support push notifications on iOS at all. It does not have a rating, reviews, or a download count. Clients who ask for "an app" do not mean this.
A native React Native or Flutter rebuild of a Framer site costs $50,000 at minimum, takes 3-6 months, and requires rebuilding every animation, every interaction, and every CMS integration from scratch in a different codebase. The Framer site becomes irrelevant — you pay for the web version and then pay again for the app version of the same design.
Custom native apps go stale. Every CMS update, every copy change, every new section on the Framer site has to be separately replicated in the native app codebase. Two separate codebases drift apart within months, requiring paid maintenance to sync. With a WebView wrapper, the Framer site and the app are the same thing — one update, both surfaces.
Sharing a Framer preview link works for stakeholder review. It does not work for user testing with non-technical participants, for distributing to a beta group who expects an app-like experience, or for a soft launch before going public on the App Store. An installable APK from Shastra's free tier fills exactly this gap.
A design agency builds a Framer site for a client. The client then wants Android and iOS apps. The agency either loses the brief to a native development shop, or quotes a custom build that kills the relationship. There has been no third option — until now. Shastra is the answer a Framer-native agency can deliver in the same week as the site launch.
This is not a compromise. For Framer sites specifically, wrapping is the right architecture — not a shortcut.
Scroll-triggered transitions, page transitions, spring physics, micro-interactions — all of these run in the WebView's full browser rendering engine. There is no partial support, no fallback, no degraded experience. If it plays in a mobile browser, it plays identically in the app. Framer is specifically designed to produce high-quality CSS and JS animations, which is exactly what the WebView renders.
Framer CMS powers blog posts, portfolio pieces, product pages, and team members. When you update content in Framer and republish, the app shows that content on the next load. No App Store update submission, no review wait, no version bump. The app and the site are the same publishing pipeline.
Custom code overrides, JavaScript components, and third-party script embeds (Calendly, Typeform, Stripe, analytics) all execute in the WebView's JavaScript context identically to a browser. There is no reconciliation step, no compatibility layer, no reimplementation required.
Framer sites already have mobile breakpoints built into their design. The app shell scales to the device screen and defers to Framer's own responsive layout. The result is a design-accurate experience across all device sizes without any additional layout work — because Framer already did it.
Framer's PWA and Shastra both work with your existing Framer site. The outcomes are not the same.
| Native App | ||
|---|---|---|
| Listed on Google Play Store | ✕ | ✓ |
| Listed on Apple App Store | ✕ | ✓ |
| Your icon on iOS home screen | Browser bookmark only | ✓ Real app icon |
| Push notifications (iOS) | ✕ | ✓ |
| Push notifications (Android) | Limited browser push | ✓ Full FCM push |
| App Store reviews and ratings | ✕ | ✓ |
| Native bottom tab bar navigation | ✕ | ✓ |
| Framer animations work | ✓ | ✓ |
| Framer CMS updates instantly | ✓ | ✓ |
| No rebuild of existing Framer site | ✓ | ✓ |
No Framer configuration, no plugins, no rebuild. Your published Framer URL becomes the app.
iOS does not support push notifications in PWAs except in very specific circumstances. Shastra uses Firebase Cloud Messaging to deliver real push notifications to lock screens on both iOS and Android. Portfolio updates, new posts, product launches, event reminders — sent from your Shastra dashboard to everyone who installed your app.
Your app appears on the Google Play Store and Apple App Store with your name, your icon, your screenshots, and your description. Users can find it by searching. They can leave reviews. They see "Made by [Your Studio]" in the listing. A browser PWA shortcut appears in a folder labeled "Utilities" that nobody opens.
Framer navigation is CSS-based. It works on the web. In a native app, the expected pattern is a bottom tab bar — Home, Portfolio, Work, Contact — that persists across all pages and gives users one-tap access to anywhere in the site. Shastra builds this natively and it sits below the Framer content, not inside it.
Some elements work on web but interfere with a native app experience — a floating chat widget, a cookie consent banner, a browser-nav-bar-aware sticky header. Inject CSS from the Shastra dashboard to hide or adjust any element for the app context without modifying your Framer site.
Framer CMS powers your content. When you publish a new post, update a case study, or swap a hero image, the app shows the new content on the next load. No version bump, no App Store submission, no review wait, no notification to users. The content cycle stays inside Framer.
Code signing certificates, developer account setup, App Store metadata, screenshot requirements, review guidelines — handled. Android approval in 2-3 days, iOS in 1-2 days. Designers and agencies can deliver app publishing as a service without becoming mobile DevOps engineers.
No Framer configuration required. No code changes to your site. Your published URL is all you need.
Your published Framer domain — custom domain or framer.app subdomain. No API keys, no Framer account access, no configuration inside Framer.
Upload your app icon, set header and splash colors to match your Framer brand, configure bottom tab navigation for your key pages, and add any CSS adjustments for the app context.
Click Build. The pipeline compiles your Android APK, AAB, and iOS IPA — signed, versioned, and ready for store submission within the hour.
Submit the binary yourself with our step-by-step guide, or let us handle the full Google Play and App Store submission process including metadata and screenshots.
Clients consistently ask for apps after seeing their Framer site. With Shastra, the agency can quote app delivery as a line item in the same project — $99 cost, marked up to whatever your rate is — and ship the client an App Store listing in the same week as the site launch. No referral out, no second agency, no custom build.
A Framer landing page or product preview site built for a launch needs to be everywhere people look — including the App Store. An app listing gives you discoverability, social proof via reviews, and a real mobile presence without pulling engineering from your actual product work.
A Framer-powered magazine, newsletter, or blog can push new article notifications to installed users at a fraction of the cost of email. The push notification opens the article directly. The Framer CMS update flow stays exactly the same — publish in Framer, readers see it in the app.
A Framer portfolio in an installable app stays on a client's phone home screen long after the browser tab closes. When a project brief opens up six months later, they open the app, scroll through your work, and call you. Push notifications let you announce new case studies directly to every client who installed it.
No rebuild. No new codebase. No waiting months. Paste your Framer URL and get a real App Store listing under your name.
14-day money-back guarantee. Free APK build, no card needed.
Not natively. Framer publishes websites. App Store and Google Play require a compiled binary — a signed .ipa for iOS, a signed .aab or .apk for Android — along with a developer account, code signing certificates, and a passed review process. Framer does not produce any of these. Shastra does: it wraps your published Framer URL in a native shell, compiles and signs the binary, and produces the files you submit to both stores.
Yes, completely. Framer animations are CSS and JavaScript. The native app's WebView is a full browser rendering engine — the same engine that powers Safari on iOS and Chrome on Android. Every scroll-triggered animation, every page transition, every spring physics interaction plays identically in the app as it does in a browser. This is one of the strongest arguments for the WebView approach specifically for Framer sites: nothing is lost in translation.
Framer's PWA support adds a basic web app manifest, allowing a user to "add to home screen" on Android or iOS. On Android, this creates a browser bookmark that opens in Chrome. On iOS, this creates a Safari shortcut. Neither produces an App Store listing. Neither supports push notifications on iOS. Neither has reviews, ratings, or download counts. Clients who ask for "an app" universally mean a store listing they can send someone to download — not a browser bookmark on their phone's second home screen page.
Yes. Shastra wraps your live published Framer URL. When you publish new content in Framer CMS — a new blog post, an updated case study, a changed hero section — the app loads that content on the next visit. No app update, no App Store submission, no notification to users. The content publishing cycle stays entirely inside Framer.
Clients ask for apps. You now have an answer that does not require a separate agency or a custom native build. Quote app delivery as a line item alongside the Framer site. Your cost is $99 (one-time, lifetime, unlimited apps). Charge what your rate justifies. Deliver the APK and IPA from the Shastra dashboard in the same week as the site launch. You can also handle App Store submission as a service since Shastra covers the managed submission process.
They work. Code overrides, custom JavaScript components, Typeform embeds, Calendly, Stripe payment links, Loom videos, Google Maps — anything that executes in a browser on your Framer site executes identically in the WebView. There is no reimplementation or compatibility shim required.
No. Shastra wraps any public Framer URL, including a framer.app subdomain. A custom domain is better for App Store credibility — "Made by myagency.com" looks more professional than "Made by myproject.framer.app" — but it is not a requirement to build and submit the app.
Yes. When you send a push from the Shastra dashboard, you set a title, body, and an optional URL. Tapping the notification opens the app and navigates directly to that URL — a specific blog post, a new portfolio piece, a product page. The deep link points to any path on your Framer domain.
Setup in the Shastra dashboard takes around 10 minutes. Build generation completes within the hour. Google Play review is 2-3 business days. Apple App Store review is 1-2 days. Most Framer sites have a live App Store listing within a week of signing up.
Visit shastrapps.com/pricing to see current pricing for your region. There is a 14-day money-back guarantee on all paid plans.
Shastra works with any website platform