I might consider adding a backend server at some point, but I'd still want to keep the tool as simple and privacy-friendly as possible.
Right now everything works fully offline, and that's part of the appeal.
If I do add a backend, it would only be for optional things like syncing or sharing — and it would stay opt-in so the core experience remains local-only.
Still exploring the balance there, but thanks for the idea!
Thanks! Yes, everything is stored locally in the browser — no backend at all.
And that’s a great idea.
I’ve been thinking about adding an export/import option, and encoding the data into the URL hash actually fits the “offline + privacy-first” vibe really well.
I’ll explore it — would be super useful for sharing or backup without requiring any server.
A small suggestion that immediately came to my mind, why not try making it a JSON serialized data and base64 encode it just like JWT. So that it can be shared and loaded effectively.
Yep, it’s responsive — though the layout gets a bit tight on very small screens, so I’ll tweak that later.
About the “list above or below” part — what kind of list were you thinking of?
Like a separate to-do list outside the calendar, or just more space for notes?
Thanks for your support! IndieFollow.top is designed to stand out by focusing exclusively on products created and used by indie makers, ensuring a truly authentic and grassroots community. Unlike platforms like Betalist and Startuplist, which cater to a broader range of startups, IndieFollow.top is all about showcasing true indie products. Each product is hand-picked to reflect the creativity and passion of the indie community.
Additionally, we're trying to uncover the stories behind the products, connecting users with the real people who created them. We believe this approach makes the products feel more authentic and true, offering a deeper connection between creators and users.
Right now everything works fully offline, and that's part of the appeal.
If I do add a backend, it would only be for optional things like syncing or sharing — and it would stay opt-in so the core experience remains local-only.
Still exploring the balance there, but thanks for the idea!
reply