Flutter Forward EXTENDED - Ashimi0x .pdf

Best Practices for
Flutter Development
Optimizing Flutter state management

The first rule of any technology used in a
business is that automation applied to an
efficient operation will magnify the
efficiency. The second is that automation
applied to an inefficient operation will
magnify the inefficiency.
— Bill Gates

Best Practices for Flutter Dev.
Optimizing Flutter State Management
Chief Technology Officer
Edu Karma & Kolhab Technologies
Abdulwahab Ashimi

Setup Code Linting Rule
Single Responsibility
Use asynchronous programming
Keep your widget tree shallow
Use stateless widgets whenever possible.
+
+
+
+
+
Title here

Code linting is the process of analyzing code to find potential errors and code style
issues. In Flutter, you can use a code linting tool like Dart Analyzer or Flutter Lints to
enforce code style guidelines and catch potential errors before they become issues.
By using a code linting tool, you can ensure that your code is consistent and
maintainable. You can also catch common errors and prevent them from causing bugs in
your app.
Avoid using var for declaring variables with explicit types.
Use final for variables that are not reassigned.
Use const for variables that won't change during runtime.
Use async and await for asynchronous operations.
Avoid using `this` unnecessarily.
#0: Setup Code Linting Rules

The single responsibility principle (SRP) states that a class should have only one
reason to change. In Flutter, this means that each widget should have a single
responsibility.
in a Flutter application, a widget that displays data and handles user input should not
also be responsible for fetching data from an API. This way, if the API changes or the
widget needs to be updated, only the relevant class needs to be modified, rather
than the entire codebase.
By following the SRP, you can create code that is easier to understand, maintain, and
test. When a widget has a single responsibility, it's easier to debug and refactor if
needed.
#1: Single Responsibility

Asynchronous programming is the process of running tasks concurrently in a
non-blocking way. In Flutter, you can use the async and await keywords to perform
asynchronous tasks.
By using asynchronous programming, you can create apps that are more responsive and
faster. Asynchronous programming allows you to run long-running tasks in the
background without blocking the user interface.
In Flutter, asynchronous programming is typically implemented using the async and
await keywords, which allow developers to execute time-consuming tasks in the
background while keeping the main thread free to handle user input and other important
tasks.
#2: Asynchronous Programming

// example code with synchronous function call
void getData() {
var data = fetchData();
print(data);
}
String fetchData() {
// code that simulates a long-running operation
Future.delayed(Duration(seconds: 2), () {
return 'Data fetched';
});
}

// example code with asynchronous function call
void getData() async {
var data = await fetchData();
print(data);
}
Future<String> fetchData() async {
// code that simulates a long-running operation
await Future.delayed(Duration(seconds: 2));
return 'Data fetched';
}

In Flutter, the widget tree is a tree-like structure that represents the user interface of
your app. Each node in the tree is a widget. The widget tree can get very deep if
you're not careful.
Keeping your widget tree shallow means that you have fewer layers of widgets. This
makes your app faster and more efficient. It also makes it easier to debug and
maintain your code
#3: Shallow Widget Tree

Stateless widgets are widgets that cannot change over time. They are easier to
understand and maintain because they don't have to keep track of any mutable state. In
Flutter, you should use stateless widgets whenever possible.
By using stateless widgets, you can create code that is easier to understand, test, and
maintain. Stateless widgets are simpler than stateful widgets, which makes them less
prone to bugs and errors.
#4: Stateless Widgets

Flutter Forward EXTENDED - Ashimi0x .pdf

Always code as if the guy who ends up
maintaining your code will be a violent
psychopath who knows where you live.
— John F. Woods

Flutter Forward EXTENDED - Ashimi0x .pdf

More Related Content

Similar to Flutter Forward EXTENDED - Ashimi0x .pdf (20)

Recently uploaded (6)

Flutter Forward EXTENDED - Ashimi0x .pdf