Health, home and travel decision
Shotwise
A competent developer can build and maintain a practical Shotwise replacement in ~40 hours using native iOS tooling; the product has no durable moats in the supplied pages so self-build is realistic.
View on the App Store↗$0.42/mo
$5/yr
Read off the official pricing page.
$100one-off40 h to build
$0/mo3 h/mo upkeep
On cash alone, building overtakes the subscription at 20 seats.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Shotwise alternatives, with the arithmetic →
What a replacement has to do
- Log injections and dose → schedule local reminders → record weight → view combined history and charts
What it still won’t have
- App Store distribution and existing user base
- Polish and bug fixes accumulated in the production app
- Developer support and warranty for App Store payments/subscriptions
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 20 seats.
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 iOS (SwiftUI) GLP‑1 shot and weight tracker backed by CoreData and optional HealthKit sync. Scope: screens to add/edit injections (medication, dose, injection site, timestamp), weight entry screen, list/history, line chart overlaying weight with injection events, configurable local notifications/reminders, App Store receipt validation to gate premium features, CSV export, and basic settings. Out of scope: server backend, analytics, multi-user accounts. Include unit tests for data model logic, UI tests for core flows, error handling for failed saves/notification scheduling, and build/run instructions.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 3 cited sources+3
- Price verified on pricing page+3
- Evidence score89
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 →Cited sources · 3
Every page the run actually retrieved.
- official productGLP 1 Tracker - Shotwise (App Store)
- open sourceoliexdev/openScale
- open sourcewger-project/wger
Integrity checks
What held up, and what did not.
