Health, home and travel decision
Getfasted
A capable developer can build the core fasting timer, logging, and recipe browsing in about a week and maintain it cheaply, but reproducing the vendor's polished mobile apps, distribution, and user base is non-trivial.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$50one-off30 h to build
$20/mo3 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- User starts a fast (Start Fasting), app runs a timer and notifies at goal end, user ends fast (End), logs water sips and weight, and consults recipes/nutrition.
What it still won’t have
- App-store distribution and the polish of native mobile UX
- User acquisition, reviews and established user base
- Multi-language support and edge-case-tested flows
- Any proprietary analytics or internal optimizations the vendor ships
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Getfasted does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal intermittent-fasting web app using React (Expo if mobile), Node.js + Express, and Postgres. In scope: a timer screen with Start/End fasting, background scheduling and local or push notifications, REST API to record fasting sessions, water intake and weight logs, a static recipe list with nutritional fields, simple email or token authentication, and a single-user sync flow. Out of scope: multi-tenant billing, analytics dashboards, full app-store submission, and extensive localization. Include error handling, input validation, unit tests for API routes, and end-to-end tests for the core timer + logging flows.
How we checked
How the score was reached
- Partly verdict base52
- 3/3 assessment runs agreed+4
- Evidence score56
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Integrity checks
What held up, and what did not.
