What actually happens when you press Publish?
In the Leanfinit beta, Publish puts your app live on the web with a link to share. What it does, what it doesn't do, and where each visitor's data lives.
In the Leanfinit beta, pressing Publish puts your app live on the web, so anyone with the link can open it in a browser. It costs nothing during the beta and needs no hosting account, domain setup or server. Publish does not submit your app to the App Store or Google Play.
We kept Publish to one button on purpose. Below is what that button does, what it leaves to you, and what "no backend" means once other people start using your app.
Why one button
Getting from a working preview to a live app is where many AI-built apps stop. Hosting accounts, deployment settings, environment variables and DNS records are routine for developers and a wall for everyone else. We wrote about where AI-built apps get stuck in more detail.
So the studio treats publishing as a single step. You build the app by describing it, check the preview, and press Publish. The result is a link.
What Publish does
It builds a production version of your app. The preview in the studio is for trying things out. Publish turns the current version into the one people will open from the link.
It puts the app on the web. The app is hosted for you and reachable from a link you can share, put on a website or print as a QR code.
It gives you something to share right away. The link works in a phone or desktop browser. Nobody needs to install anything from a store to use it.
What Publish doesn't do
No store submission. During the beta, Leanfinit does not submit apps to the App Store or Google Play. If you need a store listing, export the code and take it through Apple's and Google's processes under your own developer accounts. Whether you need a store at all is a fair question. Our guide on web, PWA or App Store for a personal app helps you decide.
No accounts for your users. Publishing does not add sign-up or login screens. An app asks for an account only if you described one, and most personal and small-business tools don't need it.
No database on a server. Generated apps have no backend by default. That has consequences worth understanding before you share the link widely.
Where your visitors' data lives
Apps built with Leanfinit keep their data on the device. For a published web app, that means each visitor's entries stay on the device and browser they use.
In practice:
This is the right default for personal tools, private notes, trackers and calculators. It also means a published app is not the right tool when people must see each other's updates live, such as a shared staff schedule or a list several people edit at once. That needs a backend, which you can add to the exported code.
Updating a published app
Apps change. You describe the change in the studio, check the preview, and publish again.
Because data is kept on each visitor's device rather than on a server, think about changes that affect stored records. Renaming or removing a field that people have filled in for months deserves a moment's thought before you publish.
Before you share the link
A quick check saves awkward messages later:
When to export instead
Publish covers many uses: tools for yourself, your family, a club or a small shop. Export the code when you need something Publish doesn't do:
Generated apps are built on Flutter, a widely used open-source framework, so the exported code is something any Flutter developer can work with.
Web app or installed app?
Many people assume a "real" app has to come from a store. For tools you use yourself or share with a few people, a link is often the faster and simpler route: no review, no developer account, no waiting. Our insights on building a PWA without coding and PWA vs native apps for personal use go deeper into the trade-offs.
Build something small and press Publish in the Leanfinit studio. It is free during the beta.