Does a lot" is the opposite of what gets clicks on this kind of post: there are 50 ToDo apps already and people scroll right past generic framing.
What's the one mechanic only your app has? Lead with that in the title and the first line of the description, then mention the rest.
Right now the App Store page also doesn't say it in the first paragraph
I've always sucked at marketing. For HN, I decided to be honest because that's the kind of people who read HN.
And it really does do a lot. That's not hype. It's full-featured as I could make it without turning into something it's not, like a calendar or "productivity system."
At the heart of it is the mechanic of a rotation list, not forgetting what's next, but that's just the beginning.
This is the epitome of "my idea didn't get stolen, it just got tired of waiting"!
Just kidding (although I did have a similar idea for an app a couple months ago but didn't end up fully commiting to it.)
Anyway this is a pretty useful idea. What made you start off creating it?
You got the gist of it. Then it just kind of took off.
The TLDR:
Where it started: me standing in front of a long aisle of dog food bags at Costco, racking my memory for which kind I was supposed to buy next for my finicky golden retriever, Kilo.
How it ended: me building Rotation List, so nobody will ever have to forget again.
> With an AI assist, there was no reason to stop adding improvements as I thought of them, so I didn't.
That is the mantra of today, yes. In a similar vein, I made my initially personal C course into something I could make public-facing, with some refinements, I also kept adding features but them my "sanity"(?) kicked in and i squashed a couple to be only in dev mode. Perhaps they will return to the public version after a round of refinement.
The thing is, it's real. Or it was for the golden era of cheap tokens. When tokens get expensive, we'll see how that changes things. With AI, you can think in terms of features rather than implementation; that's a totally different way of working.
I first programmed in C on a PDP 11 many years ago. I'm curious what you mean by "public vs. dev mode"?
I started 5 years ago via a programming bootcamp here in Portugal. After finishing it, I dreamed of being able to make my own software, and solve all my programming and life problems in one fell swoop. Then the AI boom happened, I got laid off after 2 years of working at a software and consulting co., and swallowed my dream of making enough money to buy a house (lol).
Currently working in a place where I actually need to talk to people and do real life stuff: a store clerk. Not glamorous, but it allows me, in my own time, to tinker with the things i know, learn new things, and more recently, vibe-code stuff and release at a pace I've never worked before.
What i meant by the "public vs dev mode" is: i gated a feature or two behind only being present if im running my app locally (via npm run dev or what have you), because i was insatisfied with how that feature is currently implemented. I intend to refine it at a later point.
I did that because, even in the age of thinking "in terms of features rather than implementation", i am trying to be selective, and find a headspace where, if i feel that a certain aspect of a project (be it fully/partially vibe coded or not) is not ready to be presented in the live app, then it does not need to / should not be in prod. Could be that i was aiming too high and the feature was lacking, coule be my prompts that were misguided, or could be feature creep making me nervous.
I both welcome and fear the age where tokens get vastly expensive. I also hope for the time where we can run proper local models that don't require me to live in a data center.
Sorry for the long comment. It's my own writing at least.
"if i had more time, i'd have written a shorter letter"
According to app store optimization theory, that means you were never a potential customer anyway. If that's true or not, who knows?
None of my other apps have ever had a hard paywall, and success was not a result. So I tried something different this time.
In the end, I just couldn't go with a hard paywall; it's against my nature. So, on the paywall at the bottom, there's a "not now" button that lets you use all the features of the app without paying for 7 days.
Does a lot" is the opposite of what gets clicks on this kind of post: there are 50 ToDo apps already and people scroll right past generic framing. What's the one mechanic only your app has? Lead with that in the title and the first line of the description, then mention the rest.
Right now the App Store page also doesn't say it in the first paragraph
I've always sucked at marketing. For HN, I decided to be honest because that's the kind of people who read HN.
And it really does do a lot. That's not hype. It's full-featured as I could make it without turning into something it's not, like a calendar or "productivity system."
At the heart of it is the mechanic of a rotation list, not forgetting what's next, but that's just the beginning.
This is the epitome of "my idea didn't get stolen, it just got tired of waiting"! Just kidding (although I did have a similar idea for an app a couple months ago but didn't end up fully commiting to it.)
Anyway this is a pretty useful idea. What made you start off creating it?
You got the gist of it. Then it just kind of took off.
The TLDR:
Where it started: me standing in front of a long aisle of dog food bags at Costco, racking my memory for which kind I was supposed to buy next for my finicky golden retriever, Kilo.
How it ended: me building Rotation List, so nobody will ever have to forget again.
I explained more in:
https://www.indiehackers.com/post/ai-killed-the-mvp-whats-ne...
With an AI assist, there was no reason to stop adding improvements as I thought of them, so I didn't.
> With an AI assist, there was no reason to stop adding improvements as I thought of them, so I didn't.
That is the mantra of today, yes. In a similar vein, I made my initially personal C course into something I could make public-facing, with some refinements, I also kept adding features but them my "sanity"(?) kicked in and i squashed a couple to be only in dev mode. Perhaps they will return to the public version after a round of refinement.
The thing is, it's real. Or it was for the golden era of cheap tokens. When tokens get expensive, we'll see how that changes things. With AI, you can think in terms of features rather than implementation; that's a totally different way of working.
I first programmed in C on a PDP 11 many years ago. I'm curious what you mean by "public vs. dev mode"?
I started 5 years ago via a programming bootcamp here in Portugal. After finishing it, I dreamed of being able to make my own software, and solve all my programming and life problems in one fell swoop. Then the AI boom happened, I got laid off after 2 years of working at a software and consulting co., and swallowed my dream of making enough money to buy a house (lol).
Currently working in a place where I actually need to talk to people and do real life stuff: a store clerk. Not glamorous, but it allows me, in my own time, to tinker with the things i know, learn new things, and more recently, vibe-code stuff and release at a pace I've never worked before.
What i meant by the "public vs dev mode" is: i gated a feature or two behind only being present if im running my app locally (via npm run dev or what have you), because i was insatisfied with how that feature is currently implemented. I intend to refine it at a later point.
I did that because, even in the age of thinking "in terms of features rather than implementation", i am trying to be selective, and find a headspace where, if i feel that a certain aspect of a project (be it fully/partially vibe coded or not) is not ready to be presented in the live app, then it does not need to / should not be in prod. Could be that i was aiming too high and the feature was lacking, coule be my prompts that were misguided, or could be feature creep making me nervous.
I both welcome and fear the age where tokens get vastly expensive. I also hope for the time where we can run proper local models that don't require me to live in a data center.
Sorry for the long comment. It's my own writing at least. "if i had more time, i'd have written a shorter letter"
"start a 7-day pro trial today" this is where you lost me
According to app store optimization theory, that means you were never a potential customer anyway. If that's true or not, who knows?
None of my other apps have ever had a hard paywall, and success was not a result. So I tried something different this time.
In the end, I just couldn't go with a hard paywall; it's against my nature. So, on the paywall at the bottom, there's a "not now" button that lets you use all the features of the app without paying for 7 days.