I've been working on TYR (Track Your Routine), a Flutter-based task and routine tracking app. It's open source and built with Firebase for auth and data sync.
Key features:
- Task creation with date/time scheduling
- Local notifications for reminders
- Real-time sync across devices via Firestore
- Category-based organization (work, vacation, events)
- Clean dark theme UI with Material Design 3
Tech stack: Flutter/Dart, Firebase Auth, Cloud Firestore, local notifications.
The app is still under active development, but the core functionality is working. I built it to solve my own need for a simple, privacy-focused task tracker that works across platforms (Android, iOS, Web, Desktop).
What I'd love feedback on:
- The notification system implementation
- UI/UX improvements
- Feature suggestions
- Code quality and architecture (it's my first larger Flutter project)
The codebase is MIT licensed and contributions are welcome. I'm particularly interested in feedback from Flutter developers on best practices I might be missing.
The project started May 3, 2023 - you can see the commit history on GitHub. The README was just updated for this post, but all the code was written manually over the past year+. I'm learning Flutter as I go, so any code review would be appreciated!
Fair enough. It would probably be worth mentioning right at the top of the readme that the code is human and the readme is AI, because there's so many projects getting posted here lately that are all AI and many people will just close the tab as soon as they see that readme.
I’m not sure this as widely held a practice as you would think. For an app as low stakes as this I couldn’t care less who wrote the code, as long as it does what it says (and only what it says) on the box.
It may say more about me than the person writing these type of README's, but if I see more than one or two emojis in a README, I immediately assume it was fully generated rather than written.
It’s funny that almost all vibe coded software have this detailed tree project structure in README. If I recall correctly, this was not common in pre-LLM era. It was too much burden to maintain.
I'm happy for you building this app, it's tremendous effort to build a flutter application, and this should feel like an achievement for you.
However, task management apps are so unbelievably common nowadays. Nothing that can't be solved by notepad on PC, or the clock/calendar app on my phone / and if I really need a task app, I'll use google's or build my own.
Your next step should be to take what you have learned from building this app, and focus on fixing a real problem that people around you face.
I've been working on TYR (Track Your Routine), a Flutter-based task and routine tracking app. It's open source and built with Firebase for auth and data sync.
Key features: - Task creation with date/time scheduling - Local notifications for reminders - Real-time sync across devices via Firestore - Category-based organization (work, vacation, events) - Clean dark theme UI with Material Design 3
Tech stack: Flutter/Dart, Firebase Auth, Cloud Firestore, local notifications.
The app is still under active development, but the core functionality is working. I built it to solve my own need for a simple, privacy-focused task tracker that works across platforms (Android, iOS, Web, Desktop).
What I'd love feedback on: - The notification system implementation - UI/UX improvements - Feature suggestions - Code quality and architecture (it's my first larger Flutter project)
The codebase is MIT licensed and contributions are welcome. I'm particularly interested in feedback from Flutter developers on best practices I might be missing.
GitHub: https://github.com/MSF01/TYR
What do you think? What features would make this more useful for your workflow?
I can't seem to find any disclosure of it all being AI coded, but the readme style is a dead giveaway.
The project started May 3, 2023 - you can see the commit history on GitHub. The README was just updated for this post, but all the code was written manually over the past year+. I'm learning Flutter as I go, so any code review would be appreciated!
Fair enough. It would probably be worth mentioning right at the top of the readme that the code is human and the readme is AI, because there's so many projects getting posted here lately that are all AI and many people will just close the tab as soon as they see that readme.
I’m not sure this as widely held a practice as you would think. For an app as low stakes as this I couldn’t care less who wrote the code, as long as it does what it says (and only what it says) on the box.
Screenshots in the README would we nice :) + the writing style in the README gives slop smell
I was coming to look for a comment like this.
It may say more about me than the person writing these type of README's, but if I see more than one or two emojis in a README, I immediately assume it was fully generated rather than written.
I don't mind low stakes vibe-coded applications per se, but the readme is LLM slop that I couldn't bring myself to keep reading.
It’s funny that almost all vibe coded software have this detailed tree project structure in README. If I recall correctly, this was not common in pre-LLM era. It was too much burden to maintain.
Yeah, and why would you even have it when the full tree is right there on GitHub on top of it?
> low stakes vibe-coded applications
what gives you the confidence to express judgment that this is a low-stakes vibe-coded app, rather than something lovingly put together by a human?
IMO if it didn’t have copious emoji, it would feel less sloppy. It’s a pet peeve I have with coworkers’ work lately, too
Are Claude and ChatGPT coworkers of yours? :)
It's not an app I need but in which way is the README a "slop"? It's quite to the point and contains everything one needs to know.
also this ai slop never seems to include screenshots.
I'm happy for you building this app, it's tremendous effort to build a flutter application, and this should feel like an achievement for you.
However, task management apps are so unbelievably common nowadays. Nothing that can't be solved by notepad on PC, or the clock/calendar app on my phone / and if I really need a task app, I'll use google's or build my own.
Your next step should be to take what you have learned from building this app, and focus on fixing a real problem that people around you face.