A couple weeks ago I posted here asking whether my app was a "recorder"
or a "trend tracker." The thread genuinely changed how I think about it —
thanks to everyone who weighed in.
Update: SnoreScribe is now live on the App Store. Solo, $0 marketing
budget, zero third-party SDKs, audio that never leaves the phone.
What changed since the beta:
I picked a side on positioning. It's NOT "an app that records your
snoring." It's "an app that tells you if your snoring is getting
better or worse." Same feature set, completely different sentence —
and the second one is the reason anyone actually pays.
I rewrote everything around that. Landing page hero went from
"record at night, understand in the morning" to "is your snoring
getting better or worse?" The App Store metadata follows next build.
Pricing: one-time purchase, no subscription, no surprise paywall.
Where I actually am, honestly:
Open question I'm still chewing on: for a "search-type" need like snoring
(people don't browse communities for it, they search the App Store
directly), how much does build-in-public actually move the needle vs just
nailing ASO? Curious how others with utility apps think about this.
If you want to poke at it: https://apps.apple.com/app/id6778848782