I do this through calendar notifications but I agree that there isn't as much granularity, such as "ping me X times a week but once I finish a task, stop pinging me." Calendars don't keep track of that kind of state and thus aren't well suited to this kind of productivity tracking.
I'm building something in the same space [0], the landing page is outdated but the version in my head is similar to your idea, as a mobile app in Flutter with a Rust backend API, and Twilio for the SMS, calling, and emailing.
And good for you for cutting scope and just launching! That's what I did a few weeks ago, I built a site in 24 hours, launched it on HN and Reddit, and got 20k visitors in a 48 hour span after launching [1] because I was tired of procrastinating launching products. I also got a lot of really good feedback from the launches, so now I'm learning that launching early and often is key to iterative development.
Don't worry about the pricing by the way. I'm going to make my app cost $20 a month simply to weed out people who won't take habit formation seriously. Those that want to buy it will buy it and those that won't, well, they're not really worth caring about since they're not your customers anyway.
The temptation to make it perfect and build out a large feature set first is real and paralyzing; I doubt I would've gotten anything out the door if I didn't cut scope.
This took a bit longer than your project (initial commit on Oct 16, I just checked), but I still cut a ton of stuff I'm excited about building. How are you managing scope for your project?
Regarding pricing, I haven't really given it too much thought yet, and the current numbers are essentially just placeholders. Thanks for the feedback, and good luck with your project!
Besides the scoping, there is also "it is not perfect yet". This was driving me crazy because I could never finish something( as a home developer of home applications) and I had a bunch of "products" in constant development.
I decided to release them often and let my family drive the development direction. I quickly understood that having the ability to (usually) switch lights on and off was more important that the dashboard about how far from home I was when biking from the office.
I'm building something in the same space [0], the landing page is outdated but the version in my head is similar to your idea, as a mobile app in Flutter with a Rust backend API, and Twilio for the SMS, calling, and emailing.
And good for you for cutting scope and just launching! That's what I did a few weeks ago, I built a site in 24 hours, launched it on HN and Reddit, and got 20k visitors in a 48 hour span after launching [1] because I was tired of procrastinating launching products. I also got a lot of really good feedback from the launches, so now I'm learning that launching early and often is key to iterative development.
Don't worry about the pricing by the way. I'm going to make my app cost $20 a month simply to weed out people who won't take habit formation seriously. Those that want to buy it will buy it and those that won't, well, they're not really worth caring about since they're not your customers anyway.
[0] https://getartemis.app
[1] https://news.ycombinator.com/item?id=33303269