Given that an user is downgrading his pricing plan, you could show a view just before the confirmation. In that view he can choose what to disable/delete. If there is nothing to choose, you may design the view to communicate with the user about all the features that will be disabled for his account.
All these points you mentioned are part of the reason why I choose Remix instead of NextJS at work.
Have you tried Flowtime instead of Pomodoro?
I'm gonna make an online microwave simulator.
features:
- realistic microwave sound effects
- +30 seconds button
- rotating turntable with internal lighting
Please, stop saving your external API's private and secret keys in the front-end.
#buildinpublic
Well done! 💯
From a UI/UX standpoint, of all the indie hackers projects I've seen, I like your wait list page better!
You may change the dot at the center with an icon that recalls social networks to communicate what you are capturing.
If everyone sells bread, who's going to buy it?
This is a great tool! Are you planning to support Remix in the future?
I see everyone launching, who is catching? #buildinpublic
Did you do it to flip it or to keep it?
What was your stack before/after? I'm just curious
I am seeing more and more "toxic productivity" posts. I hope that this platform will not become the next LinkedIn.
bsky.app/profile/matt...
That's why we had different opinions. Now that the definition of done is clarified, I get your points and I fully agree with your statements.
Oh I see, I misinterpreted your definition of done.
Well, then It's never complete.
If your product is free to use, and you have people that are currently using it, I think that you will never finish working unless you decide that you don't want to work on it anymore.
Thank you for calling me a youngster, I am young.
How is your opinion different from mine?
If there is no one paying for the work you are doing (directly or indirectly), unless you are doing OSS or a product you use yourself I don't see why you should continue working on it.
In SCRUM philosophy software can be considered done when the client is fully satisfied and declares there's nothing they'd like to add or modify.
If you have a paid public product today, whether it is a SaaS a PaaS etc. I think it is done when you don't have paying customers anymore.
For #dragonball fans:
The theory behind #Tenshinhan 's Shin Kikoho is flawed.
The idea that a rotating #reuleaux triangle can "draw" a square is incorrect. For this to happen, the center of the shape would also need to move in a circular path, which doesn't happen in the anime.
What is a lead magnet? Is it a type of landing page?
You can train the #bluesky #algorithm to not show a certain type of content by clicking on the three dots on top-right, then "show more|less content like this".
Your boilerplate should not have Privacy Policy and TOS implemented, I agree with you. It is something that must implement who uses it only if the law requires it, you shouldn't bother to add it — also because it is a cumbersome topic and too much time to spend for free.
In the EU we have to provide both, even if we have 0 customers/users and little to no traffic. Just the fact that we collect emails is enough for GDPR to be required by law.
EU #indiehackers — what are you using to write Privacy Policy and TOS for GDPR?
CSR
Take a look at this wait-list boilerplate, it's a good starting point.
For people from the EU, don't forget to add privacy policy and TOS to be GDPR compliant about the emails you are collecting.
Thanks for sharing this! I think I will integrate these in my own "should I consider this" checklist :)
Thank you for sharing your experience on this! I see you use Remix, a very good decision imo!