Health, home and travel decision
Smokify
A minimal smoking-tracking and reminder app is realistic for one capable developer to implement and maintain; Smokify's site provides no evidence of hard-to-replicate moats or proprietary data.
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.
$100one-off32 h to build
$45/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
- Track a user's smoking events and progress, store their data, and send reminders/notifications to support cessation.
What it still won’t have
- Brand recognition and existing user base
- Any proprietary user engagement algorithms or community features if present
- Polished mobile apps or native push behavior (unless built)
- Integrated third-party partnerships or data the vendor may have
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Smokify 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 one-weekend-to-week single-tenant web app in Node.js (Express) + React, Postgres for storage, and Redis for background job coordination. Core features in scope: email sign-up/login with secure sessions, REST API to create/read smoking events and milestones, a React SPA dashboard showing streaks and simple charts (use Chart.js), background worker (BullMQ) to send scheduled reminder emails via SendGrid, and migrations/seeding. Out of scope: native mobile apps, complex gamification, multi-tenant billing. Include error handling, input validation, transactional DB ops, unit tests for API endpoints, and an integration test that runs the signup -> record event -> scheduled reminder flow. Provide Dockerfiles and a docker-compose setup for local development and a short README with deploy steps to a VPS or managed Postgres + container registry.
How we checked
How the score was reached
- Build verdict base78
- Evidence score78
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.
