The problem we kept running into
People build a product on Lovable, Bubble, Webflow, Framer, Softr or plain React, it works, it has users — and then someone asks the question that stops everything: “is there an app?”
Answering it used to mean a native codebase, a build toolchain, signing keys, two store consoles and a release process. That is weeks of work for something the web version already does. Most people never get there, and the question keeps coming back.
What actually happens to your URL
You paste an address. We read it, check whether it has a manifest and a service worker, and pick the build mode accordingly — a Trusted Web Activity when the site is a real PWA, Capacitor otherwise, which is what makes sites without a service worker work at all. Then a container builds the project, generates a keystore, signs the bundle and hands you the artifact.
The keystore matters more than it sounds. Sign an update with a different key and Google Play rejects it outright — permanently, for that listing. Yours is generated once, encrypted, emailed to you, and reused for every later build of the same project.
What ships today
- Android — a signed .aab for the Play Store plus an .apk for sideloading and testing, targeting API 36.
- iOS — an .ipa built on macOS and submitted through App Store Connect. Live since July, included from the first paid plan.
- Desktop — .msi for Windows, .dmg for macOS, .AppImage for Linux, all three from the same build.
- Android TV — a leanback launcher, a TV banner and D-pad navigation injected into the web view, in a single universal bundle that still installs on phones.
- Seven stores — Google Play, Amazon Appstore, Samsung Galaxy Store, Microsoft Store, GitHub Releases, Snap Store and Flathub.
We are on Product Hunt today
If this is useful to you, the most helpful thing you can do is tell us where it falls short. Comments on the launch page get read and answered.
What we do not do — and will not claim
A wrapped web app is not a native app, and pretending otherwise wastes your money. Here is the honest boundary:
- The store accounts are yours. Google Play costs 25$ once, Apple 99$ a year. We cannot remove that, and nobody can.
- The listing has to exist first. We build and upload the artifact; creating the app in the store console, writing the listing and passing review are still yours.
- A site that is only a brochure will be rejected. Both stores turn away apps that are a thin wrapper around a static page. This works for products people come back to — a SaaS, a store, a tool, a community.
- The Mac App Store is not supported. The macOS build is a .dmg you distribute yourself.
What it costs
The first build is free — one per account, carrying our logo — so you can see the result before deciding anything. After that: 9€ for a single build with your own branding, from 21€ for Android plus desktop across the seven stores, 49€ for five update sets, and 79€ a month for unlimited. Everything except the last one is a one-time payment — no per-seat fee, no per-app fee.
The full breakdown is on the pricing page, and if you want to check whether your site is ready before spending anything, the live checker on the PWA to APK page reads your manifest and answers in about ten seconds.