Health, home and travel decision
Did I Do?
A competent developer can reproduce the core single-user flows (widgets, notifications, photo verification, iCloud sync) in a few weeks, but the shipped app’s polish, App Store presence, and long-term OS-edge-case fixes are costly to match; full parity with the paid product is therefore only partially realistic.
View on the App Store↗$0.99/mo
$12/yr
Read off the official pricing page.
$100one-off80 h to build
$8.25/mo3 h/mo upkeep
On cash alone, building overtakes the subscription at 17 seats.
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
- Tap widget or app to mark task done → store completion with optional photo → show streak/heatmap and widget state → schedule/reschedule local notifications and resets → optionally sync via iCloud
What it still won’t have
- Polished App Store distribution, discoverability, and existing user reviews
- Developer-maintained polish, bug fixes, and UX refinements accumulated over releases
- Existing multi-device support and solved edge-cases (widget refresh quirks, notification race conditions)
- Time saved vs. building and maintaining iOS-specific features like Widgets + CloudKit integration
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 17 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 an iOS SwiftUI app + Home Screen Widget using Swift and SwiftUI, Core Data with CloudKit for optional iCloud sync, and UserNotifications for local reminders. Core features in scope: (1) create/edit recurring or custom-interval tasks, (2) home-screen widget showing up to 5 tasks with one-tap complete, (3) local notification scheduling and snooze options, (4) attach photo proof to a task completion and store per-day history, (5) display streaks and a simple heatmap view, (6) implement App Store in-app purchases (monthly, yearly, lifetime) and local receipt check, (7) settings, task sharing (simple state share link), and basic accessibility. Out of scope: server-hosted multi-user accounts (beyond CloudKit), analytics backend, and advanced collaboration. Include error handling, unit/ui tests for core flows, CI build script, and clear README with App Store provisioning and CloudKit setup steps.
How we checked
How the score was reached
- Partly verdict base52
- 2 cited sources+1
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Evidence score60
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 · 2
Every page the run actually retrieved.
- official pricingDid I Do? - ADHD & OCD Help App - App Store
- official productDid I Do? - App Store product page
Integrity checks
What held up, and what did not.
