LULUSKILL ARTICLE
Website, web app, mini-program or local tool: how to choose
Four questions that settle most cases, what each shape costs to keep running, and the signs you picked the wrong one.
This is LuluSkill's own writing. It does not quote, mirror or summarise any third-party Skill, and it recommends none. Reading it builds, publishes and runs nothing: what an AI tool does with your text is for you to check.
The quick answer: one sentence per shape
When more than one row seems to fit, the four deciding questions below settle it, asked in order.
- Website
- Build a website when everyone should see the same pages and nobody needs to come back to their own information; most first ideas land here.
- Web app
- Build a web app when each person must come back and find their own information, and you are ready to take on sign-in, stored data and permissions.
- Mini-program
- Consider a mini-program only when your people already spend their day inside one messaging or payment platform and the job depends on its sharing or payment.
- Local tool or script
- Build a local tool when the work is on files already on one computer, for one person or a small team, and nothing needs to be reachable from the internet.
What the four shapes actually differ on
It is tempting to choose by how impressive the result sounds. A better way is to ask three plain questions about the finished thing: where does a person open it, whose data does it keep, and who has to look after it once it exists. The four shapes are four different answers to those questions.
None of the four is a beginner or an expert option. A one-page website can be exactly right for a clinic, and a web app can be exactly wrong for a birthday invitation. The right shape is the smallest one that still lets your people finish the thing they came to do.
The four, in one line each
In plain words
- Website
- Pages anyone can open in a browser. Everyone sees the same thing, and the site does not need to remember who visited.
- Web app
- A browser tool that remembers each person's own information between visits, which means sign-in, stored data and rules about who may see what.
- Mini-program
- A small app that lives inside a larger messaging or payment platform and borrows that platform's sign-in, sharing or payment features — and follows that platform's rules.
- Local tool
- A program that runs on one computer, usually to work on files that are already there. Nothing needs to be reachable from the internet.
Four questions that settle most cases
Ask them in order and stop at the first clear answer. Later questions only matter when an earlier one is undecided.
- Does the work happen on files that are already on one computer, for one person or one small team? If yes, start with a local tool. Nothing about the job needs the internet, and keeping it off the internet removes a whole category of risk.
- Do your people already spend their day inside one particular messaging or payment platform, and does the job depend on that platform's sharing or payment? If yes, a mini-program is worth considering — and so is the extra account, rules and review step it brings.
- Does each person need to come back and find their own information — a saved list, a booking, a history? If yes, you are describing a web app, and you are also taking on sign-in, stored data and permissions.
- If none of the above is true, it is a website. Most first ideas land here, and that is good news: it is the cheapest shape to build, host, check and change.
Answers that do not decide the shape
- "It should look professional." Every shape can look professional; it is a design decision, not a shape decision.
- "It should work on phones." Three of the four can be used from a phone; a local tool usually lives on a computer.
- "We might need accounts later." Later is not now. Write it on the out-of-scope list and choose for the first version.
What each shape asks of you after the first version
Building the first version is the short part. The table below is about the long part: who opens it, where information ends up, and what somebody has to keep doing for as long as it exists. The rows are general tendencies, not guarantees; your own situation decides.
| Shape | Who opens it | Where information lives | Ongoing work |
|---|---|---|---|
| Website | Anyone with the address, without signing in. | In the pages themselves. Visitors' details are only kept if you add a form, and then you have to decide where they go. | Keeping the content true, renewing the address, and occasionally checking that every page still opens. |
| Web app | People who sign in, each seeing their own part. | In a database you are responsible for, including other people's personal information. | Account help, backups, security updates, and answering "who can see my data" honestly. |
| Mini-program | Users of the host platform, from inside it. | Partly with the host platform, under its terms, and partly wherever you store your own records. | Following the platform's rules as they change, and passing its review whenever you release a change. |
| Local tool or script | Whoever uses that computer. | On that computer, next to the files it works on. Nothing leaves unless you make it. | Keeping a copy of the files it changes, and deciding exactly which folders it may touch. |
Example
Four situations, worked through
Example
Four invented situations, one for each shape, each run through the four questions in order.
- A piano teacher wants parents to see term dates, fees and how to get in touch. No files on one computer, no platform dependency, and nobody needs to find their own information: a website.
- A small accounting office wants to rename two hundred scanned receipts in a shared folder by date and supplier. The work is on files already on one machine, for one team: a local tool.
- A running club wants each member to log their weekly distance and see their own progress. No local files and no platform dependency, but each person must find their own history: a web app, with sign-in and stored data to plan for.
- A neighbourhood bakery takes most orders through the one messaging platform its customers already use, and wants them to pre-order Saturday bread and pay without leaving it. No local files, and the job depends on that platform's sharing and payment: a mini-program is worth weighing, together with the review step and rules that come with it.
The running club could also start as a website with a shared spreadsheet behind it, and move to a web app only if members ask for privacy. Starting smaller is a legitimate answer, as long as you write down that you chose it on purpose.
Signs you picked the wrong shape, and what changing costs
- You keep adding sign-in to a website so people can "see their own" page. That is a web app arriving one feature at a time; it is usually better to decide it on purpose.
- Your web app has accounts that nobody uses, because everyone sees the same thing anyway. It may be a website carrying costs it does not need.
- Your local tool is being emailed around so other people can use it. The job has outgrown one computer, and the next question is who may see which files.
- Your mini-program spends more effort on the platform's requirements than on your own users. A website linked from that platform may do the same job with fewer rules.
Changing shape is not a failure, but it is not free. Moving from a website to a web app adds accounts and data you must now protect; moving the other way means deciding what happens to data you already hold. Whichever direction, write the reason down first — it becomes the first paragraph of your next brief.
Your next step
Three things to do with your own idea, in order. None of them needs an account, a tool or a Skill.
- Write one sentence about your idea, then answer the four deciding questions in order and stop at the first clear yes.
- Read the row of the running-costs table for the shape you chose, and write down who will do the ongoing work.
- Add the shape and the reason for it to the top of your brief, so anyone reading it knows the decision was deliberate.