I shipped Green Time Tracker, a small iPhone/iPad app for logging time spent outside. It is mostly for families doing annual outdoor-hours goals, but the broader idea is simple: notice whether you got outside, then put the phone away.
The app started because our family had been using paper/coloring trackers with the kids. Those were fun at home and much less fun when we were at a park, on a walk, or out running around and somebody had to remember the hours later. My wife asked if I could build a simple iPhone app for it, so I did.
The current version is native SwiftUI/SwiftData after an earlier React Native version. The rewrite was mostly an exercise in restraint: keep the Dashboard, quick logging, History, Settings, charts, streaks, and tags, but avoid turning outside time into another complicated dashboard.
The business model is also intentionally boring:
v1.1.5 is now live with an App Store preview video, which feels like a small but useful milestone. Instead of explaining the app with more copy, the listing can show the actual flow: open Dashboard, log time, see progress, close the app.
I am curious how other indie devs think about this tradeoff. For a small utility that is meant to be used quickly and calmly, would you keep it free/tip-supported, charge up front, or eventually add paid features?
App Store:
https://apps.apple.com/us/app/green-time-tracker/id6755641298
Showing the whole flow directly on the App Store page instead of hiding behind screenshots is a bold, honest move — curious if that transparency has actually helped conversion, or if you're still gathering data on that.
I'm curious what convinced you removing subscriptions and feature gates creates a better product rather than simply a different pricing model.
Was there a point where you realized the business model itself could either reinforce or undermine the habit you wanted people to build?