No-Code App
Definition
Two families share the label and they behave very differently. Platform no-code keeps your app inside the vendor's system: the data lives in their database, the pages render on their servers, and the app exists only while the subscription does. Generated no-code hands you files instead — usually a web page with the logic inline — which you can open, read, edit and host anywhere. What both have in common is the reason people choose them: for an internal tool, a form, a calculator or a small workflow, the time from idea to working thing is hours rather than weeks. What neither removes is the need to understand the difference between data held in one browser and data held somewhere everyone can reach, which is where most no-code projects eventually run aground.
Why It Matters
The economics are genuinely different. A small internal tool that would take a developer a fortnight can be described, generated and published the same afternoon by the person who actually needs it, and that changes which problems get solved at all. The limits deserve the same attention. Ask two questions before anyone relies on the result. Where does the data live, and who else can see it — because a generated app usually keeps records in each visitor's browser, so ten people produce ten private copies. And who owns the thing you built, because an app made of files you hold is portable, while an app inside a platform moves only as far as that platform's export button allows.
How It Works
A generated no-code app is a web page: markup for the interface, script for the behaviour, styles for the look, generally in one file. Publishing it means saving that file as index.html and uploading it to a static host, which serves it over HTTPS at your address and runs nothing itself. Everything you see happens in the visitor's browser. That is sufficient for calculators, checklists, viewers, quizzes, planners and dashboards drawn from data baked into the page. Anything shared, saved centrally, authenticated or scheduled needs a server, which a file host does not provide. The usual arrangement when you need both is a static page that calls a hosted service or a no-code backend, with the credentials held by that service and never written into the page.
Real-World Example
A clinic manager describes a triage checklist — a few branching questions and a recommended action at the end — and gets a working page. It goes on 99helpers as clinic-triage and answers at clinic-triage.99helpers.site, with password protection turned on so only staff see it. Nothing is recorded, by design: the page gives an answer and forgets. When the protocol changed she uploaded a new version over the same name, and the poster in the staff room with the address on it stayed accurate.
Common Mistakes
- ✕Assuming a generated app collects what people enter — unless it posts somewhere, each visitor's data stays in their own browser and reaches nobody
- ✕Building on a platform without checking the export — the app can be excellent and still be unmovable, which is a problem the day the pricing changes
- ✕Putting an API key in the page so the app can reach a service — anyone can read it, and on a public address someone eventually will
- ✕Treating a generated tool as documented — six months on, nobody remembers the rules it encodes, so write them down somewhere outside the app
Related Terms
Prompt-to-App
Prompt-to-app describes tools that turn a written description of an application into something you can run — usually a working web page produced in one pass, then refined by asking for changes.
Vibe Coding
Vibe coding is building software by describing what you want in ordinary language and iterating on whatever the model returns, judging the result by whether it behaves correctly rather than by reading every line of the code.
No-Backend App
An application that runs entirely in the visitor's browser, with no server process of its own. Everything it does — layout, logic, data — happens in downloaded files, so it can be served as plain static files.
Single-File Web App
A single-file web app is a complete, working application contained in one HTML document, with the styles and the JavaScript written inside the same file. Open it in a browser and it runs — there is nothing to install and nothing to build.
Static Hosting
Static hosting is a service that stores a folder of finished web files and serves them over HTTP, without running any application code of yours. You upload the folder; the host answers requests for the files in it.
Put a file online in seconds
Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.
Host a file free →