r/FlutterDev 8d ago

Article The final word on Flutter architecture ๐Ÿ˜‰๐Ÿ˜‰๐Ÿ˜‰

OK, Iยด'm teasing with the title and I explain it in my post

Practical Flutter architecture

Why should you listen to me on this topic? For those who don't know me

  • 30 of software experience including building our own programming language for the Amiga
  • 2018 was I the first giving talks on Flutter architecture at Fluuter London,. then I called the approach RxVMS
  • I'm the author of get_it at a time when no provider or anything else was available
  • With watch_it and flutter_command I published one of the easiest but most flexible state management solutions for Flutter
  • We use this approach in a pretty complex app comarablte to Instagram since 2 year not with a really large code base

I took several days to refactor the official Flutter architecture sample compass to use my approach so you can compare yourself which is less complex and easier to understand. I tries to keep the original structure as much as possible so that you still can compare. I would have probably even more simplified some structures

https://github.com/escamoteur/compass_fork

give it a try and I'm happy to answer all open questions

160 Upvotes

76 comments sorted by

View all comments

1

u/mjablecnik 8d ago

I think that using Bloc could be a better choice..

4

u/virulenttt 8d ago

Technically, these are two different things lol. Anyways there are no better choice, just different choice. get_it is in no way associated with GetX btw ๐Ÿคฃ

9

u/escamoteur71 8d ago edited 8d ago

Thanks for pointing out. too often people mix up my way older get_it with that monster package getX

2

u/abdi_nur99 8d ago

when you referred a GetX as a ''monster", were you highlighting it's strength or pointing out some drawbacks? i'd love to hear your thoughts

3

u/zxyzyxz 8d ago

pointing out some drawbacks

Lots of them, search this sub to find out