Experienced Flutter devs, share your experience with those newer to Flutter and Dart. What are you looking for when reviewing code?
@FlutterDev decoupling of logic from UI, clean separation of concerns, no business logic in the UI.
@FlutterDev I code in Dart (Flutter) with @windsurf_ai and #Devin from @cognition_labs Building multi-platform apps in minutes. It's time to stop working so hard. Join me! @mVaraAI
@FlutterDev Don't be afraid or overwhelmed by different state management options. State Management == Data Management It is just 3 simple things. - Accessing state(data) easily - Modifying state(data) easily - Get notified when the state(data) has changed Just learn it and you are sorted
@FlutterDev Modularity of components. Determining if a file can be split into smaller widgets. Also if there's use of proper importing/exporting of related files.
@FlutterDev - How clearly is your project files and folder structured. - Instead of creating a method like _buildWidgetName inside a widget and then copying or referencing that method across multiple widgets, consider extracting the UI into its own standalone widget class.
@FlutterDev not necessarily a code review thing, but don't ship fully material apps on iOS, the Cupertino package has some great iOS-like widgets, I don't want to see a material dialog for example on iOS in an app I'm using, a Cupertino one is more fitting.
@FlutterDev Clean, testable, and maintainable code > clever tricks. When reviewing Flutter code, I look for: ✔️ Clear structure & naming ✔️ Separation of UI & logic ✔️ Tests + CI/CD ✔️ Linting & const widgets ✔️ Readable widget trees Good fundamentals always beat shortcuts.
@FlutterDev Having issues with deep link in flutter 😔 any guides?
@FlutterDev Less plugin more clean, modular code and custom widgets, best practices follow not strictly but human readable code.
@FlutterDev Some widget has the .adaptive constructor to be able to maintain the native look and feel, find those widgets and make your app look more native.
@FlutterDev Don’t commit secret keys in your apps! If you use Firebase, restrict it to bundle/package id with only the needed permissions.
@FlutterDev The libraries.. Prefer core libraries as much as possible.. And if 3rd party are used... they should have proper support
@FlutterDev Readability and clear separation of concerns
@FlutterDev Folder structure Naming (classes, functions, variables) Proper separation of UI and business logic Proper use of classes Readability and testability. How state is managed (ephemeral or app-wide) Widget reusability
@FlutterDev “Claude code please review everything and please be ultra sure everything is correct and will work on prod” 🤞
@FlutterDev If you understand state management everything will fall in place. It guides your design pattern including route. Once you understand state management you'll do a good job in flutter.
@FlutterDev There's a simple concept that any programmer should follow from the start, and that is Don't Repeat Yourself (DRY). I would also look at how the state is being rebuilt in the widgets.
@FlutterDev Explore about context, widget tree and lifecycle. These are very important.
@FlutterDev State Management: GetX, Provider, Bloc etc. Pick one then you are good to go 🔥
@FlutterDev Keep consistent flow for state management throughout application. VERY VERY VERY IMPORTANT.
@FlutterDev As a Flutter developer, I look for clean and reusable code, proper widget structure, and clear naming to make the app easy to understand and maintain.
@FlutterDev The most valuable thing i focus on is writing clean, maintainable code. When reviewing code, I’m not just looking for whether it works—I'm checking for: - Code readability - Proper use of widgets - State management -Dart idiom -File organization
@FlutterDev If they are newer then the coding convention is a must to check.
@FlutterDev Avoid implementations that would require you to run scripts to get your code working or require hard reload to work
@FlutterDev Clean architecture and proper state management utilisation.
@FlutterDev if your variable is named temp2, i’m assuming you gave up and so should i
@FlutterDev First! we've heard this phrase longer than Dracula's been alive: This is the end of Flutter or Flutter is dead. As for your code, inasmuch as I love separation of concerns, I look forward to your thinking process.
@FlutterDev Simplicity, if you can simplify your code and reuse
Separation of concerns: depending on complexity, try to extract state out of the widget and into state management, but use good judgment, some times you just go with a defacto widget and that’s the right way. Good design happens through iteration, consideration, and thoughtfulness. Try to abstract everything into simple interfaces that do the job well for most use cases with the least number of inputs & functions.
@FlutterDev My senior developer often tells me my code is too long and not modular enough.
@FlutterDev Actual refactored Widgets created through constructors rather than helper functions pumping them out as return objects
