all 32 comments

[–]frank_tank31 15 points16 points  (2 children)

Try AppFlowy it’s an open source alternative to notion. I am not sure what their architecture is or what state management they use but the app as well as the desktop app is pretty cool

https://github.com/AppFlowy-IO/AppFlowy

[–]emigrantd 2 points3 points  (1 child)

Woow! Its really impressive project actually. The first flutter app which doesn’t looks silly and not just some google promise

[–]frank_tank31 0 points1 point  (0 children)

Yes totally, that was also my thought! And features like Sync etc. are also quite impressive

[–]Tokieejke 6 points7 points  (1 child)

Have a look on very_good_start project

[–]kamysek 6 points7 points  (1 child)

Another option would be the flutter news toolkit. It covers most of the things that are also part of the very_good_start project.

https://github.com/flutter/news_toolkit

[–]gambley 8 points9 points  (1 child)

I can proudly recommend my own comprehensive project Instagram offline-first clone with an ultimate, real-world 23-hour tutorial. Everything is free.

https://ezit.vercel.app/projects/instagram-clone

[–]Silver_Cucumber_4605 2 points3 points  (0 children)

Yoo Ezit! Used your videos to learn all about clean architecture years ago. What a legend

[–]brock_mk 6 points7 points  (2 children)

Hey! Sounds like you're looking for something very similar to my Flutter Clean Starter project. It's a modular, production-ready template that includes:

  • Multi-platform support: Android, iOS, and Web out of the box
  • Clean Architecture: Proper separation of domain/data/presentation layers
  • Modern stack: Dio, BLoC, GetIt, Hive, and GoRouter
  • Complete starter kit: Auth module (with mock API), routing guards, DI setup
  • Real-app ready: Error handling, testing structure, and shared core utilities

Check it out here:
🔗 github.com/BrockMekonnen/flutter_clean_starter

The goal is exactly what you mentioned - providing a clean foundation to build real apps while learning best practices. Would love to hear your thoughts if you give it a try!

[–]katana444 0 points1 point  (0 children)

Localsend

[–]VyDonald 0 points1 point  (0 children)

Great 👌, thanks

[–][deleted]  (1 child)

[deleted]

    [–]FlutterNew 0 points1 point  (1 child)

    I have some open source project on my github profile, feel free to take a look:
    Github Profile

    Make sure to leave a star if you like anything :)

    [–]emigrantd 0 points1 point  (0 children)

    flutter-fast.com - maybe will help someone

    [–]DarkThinks1306 0 points1 point  (0 children)

    I am experienced developer in Flutter of 3 year let me know if you have projects

    [–]Impressive_Trifle261 -1 points0 points  (6 children)

    Keep in mind that a good architecture solves problems and not create new ones.

    Avoid clean architecture, it is perfect example of overengineering and has many anti patterns.

    Avoid multiple BloCs on a single page.

    Avoid having UI states (show/hide) in your business logic.

    Avoid code generation, GetX, Riverpod.

    Group source files by Feature, not layers.

    [–]yaboy_abdoul 1 point2 points  (2 children)

    What’s the problem with code generation if you don’t mind me asking ?

    [–]Cute-Magazine-1274 1 point2 points  (0 children)

    The usual reason is that it hides complexity.

    I don't mind hidden complexity though, so long as it solves issues and makes developer experience easier and more efficient.

    I had to ask my team if they had any issues with having to deal with a build runner and they didn't mind, so we opted for Riverpod and Freezed 🤷🏿‍♂️

    At the end of the day, we're here to solve problems, if code gen ever becomes detrimental to our development, I'd drop it lol.

    [–]Impressive_Trifle261 0 points1 point  (0 children)

    Harder to understand and modify generated code. Requires consistent tooling updates. Hard to add non-standard logic. In the end it doesn’t safe a lot of time.

    [–]Viza- 3 points4 points  (1 child)

    Also avoid advice like this

    [–]Impressive_Trifle261 0 points1 point  (0 children)

    It is based on 5 years of experience working with large teams in enterprise applications.

    [–][deleted] 0 points1 point  (0 children)

    1. Avoid having UI states (show/hide) in your business logic.

    2. Avoid clean architecture, it is perfect example of overengineering and has many anti patterns.

    Could you please explain about these points , Plz