Job 02 · Not yet tested
Fastest way to build a working web app from a prompt?
Prompt-to-app tools, scored on a habit tracker that really signs in, lists habits, keeps a streak, and has a URL someone else can open.
Vibe coders who need a working app, not a screenshot of one.
The standard test
Pack 0.1.0 · specified · Habit tracker
Habit tracker with sign-in, list, streak, shareable URL
Setup
One written prompt. The result must let a person sign in, keep a list of habits, show a streak, and hand out a URL that opens the app. A mock that only looks finished does not pass. We do not add requirements after the first tool runs.
Inputs
The prompt, and nothing else. No starter repo unless the product cannot work without one, in which case every tool gets the same empty project.
Time limit
One wall-clock cap for every tool in the job. The number is published with the pack before the first run and does not move between tools.
What we record
- Requirements that work
- Human fixes
- Time
- Cost
- Tool version
- Plan
How the FitScore is built
FitScore = weighted average × 20, rounded to the nearest integer. The weighted average is the sum of (criterion score × weight) divided by 100.
- Output quality30
- Reliability15
- Cost and free tier15
- Speed10
- Setup friction10
- Agent, API, and MCP support10
- Privacy and data10
5 excellent · 4 good · 3 usable · 2 poor · 1 fails. Full method.
Candidates
Candidates for App builders / vibe coding. This order is the launch list, not a ranking. No FitScores are published.
Version and plan recorded when a test is published
Version and plan recorded when a test is published
Version and plan recorded when a test is published
Version and plan recorded when a test is published
Version and plan recorded when a test is published
Version and plan recorded when a test is published
Questions this page answers
- Fastest way to build a working web app from a prompt?
- FitForTool has not published a FitScore for this job. The launch candidates are Lovable, Bolt.new, v0, Replit Agent, Base44, and Firebase Studio. Each one is listed as not yet tested. A ranking is published only after every tool in the comparison has had the same test pack run, and a person has reviewed the result. Until that page shows a FitScore, there is no winner.
- How will FitForTool test app builders / vibe coding?
- Habit tracker with sign-in, list, streak, shareable URL. One written prompt. The result must let a person sign in, keep a list of habits, show a streak, and hand out a URL that opens the app. A mock that only looks finished does not pass. We do not add requirements after the first tool runs. We record requirements that work, human fixes, time, cost, tool version, and plan. Those notes are then scored from 1 to 5 on seven shared criteria. The pack has been specified and has not been run.
- Can a vendor pay to rank higher on this job?
- No. FitForTool does not sell position or score. A sponsorship, if we run one later, is labelled and sits outside the ranked list. An affiliate link is disclosed and does not change order. A vendor may ask for a retest, and we rerun the same pack. Sponsors do not see the result before it is public.
- What does "Not yet tested" mean?
- The tool is a candidate for this job. There is no published hands-on run, so there is no FitScore, no criterion score, and no rank. Research-only is a different label, used when we have read the docs and still have not run the pack. Neither label is a score.