Forem: Rafat Jamader Meraz

Avoid state management package in Flutter

Rafat Jamader Meraz — Mon, 15 Nov 2021 19:22:38 +0000

State management is one of the best hot topic in Flutter. In community nowadays most common question is- "What package should use for state management?". Specially beginner are really confused.

As I have mentioned in my title that you should avoid state management package for your next big project. There are some fancy way to avoid these package so that our project is not depend on a third party package which is maintain by community. Sometimes a major change is happens in these packages and we face a huge list of errors and warning by that time.

Then what's the solution for state management in Flutter? So answer is reactive programming. As you already know that Flutter provides Stream & StreamBuilder for Asynchronous programming. So you can use these features to make your app more reactive. With these feature you can also use a small package which is get_it as Service locator.

Another advice is to use Stateful Widget. Many of us are afraid of use Stateful widget because they think that will create a performance issue. But in few cases like a screen only rebuild for one/twice then you can use it. You don't need to write a huge number of boilerplate code to manage this simple task with a state management package like BLoC. Use Asynchronous programming for those screens or part of screen where it need to rebuild a several times.

Should I know Design Patterns as a Flutter Developer?

Rafat Jamader Meraz — Sun, 07 Nov 2021 17:50:39 +0000

YES, you should know about design patterns as a Flutter app developer. In current scenario, most of the Flutter developer are new to programming or just started learning a framework for developing mobile application and focusing on developing fancy User Interface with flutter. It's easy and we can do rapidly. But problem is when they try to understand the deep level knowledge about Flutter core architecture. Even most of them used to write a huge legacy code in their production application (Even I was one of them). In that case, the app faces several issue during the production lifecycle like-performance issue.

So what should we do now?

We need to learn the design pattern concept for understanding the proper way to handle Flutter framework & core architecture. Firstly, We need to understand the core concept of dart language. Then comes OOP(Object Oriented Programming) with dart to save us. We can write reusable code with OOP and can make a proper maintainable application. After OOP, we need focus on Design Patterns. We can learn design pattern from several resources. I am mentioning some of my favorite sites from learning it.

These resources could be your start point of Deep knowledge with Flutter.

You can find more resources in YouTube and you can add more valuable link/sites in comments.

Reasons Why Small Companies Should Adopt Flutter For Mobile

Rafat Jamader Meraz — Sat, 06 Feb 2021 06:09:04 +0000

Flutter is on the hype now. Almost most of the developers are learning Flutter as their second framework for mobile development. As we already know that we can use flutter for the development of cross-platform native apps that performs almost like a native.

Giants company like Alibaba has already shifted their app into Flutter. And I think small companies should also start developing their own apps in Flutter.

Let's see the advantages -

Cross-platform native app: We can develop app not only for Android but also for IOS. A more interesting feature is we will get the native performance from this framework. We don't have to update features for android and ios separately. Even we can write platform-specific code. For rapid development, Flutter is one of the best frameworks.
UI Kit: Actually Flutter is a UI kit for software development. So that it provides a huge number of UI widgets for impressive user interface design.
Packages: pub.dev is the official package manager site for Flutter. We can easily get any package from here and also upload our own package to the community.
Resources: Documentation of Flutter is well organized. Google provides great documentation for Flutter learners. There are also many YouTubers who are contributing for good content and these content are quite helpful for all level developer.
Easy to learn: Anyone can learn Flutter who has previous experience of mobile development with native Android or IOS. Flutter uses Dart and it's a really interesting language as well as easy to learn.
Community: Though Flutter released last 2017, the Flutter community is quite big already.
Small team: Small companies have a few amounts of developers. But they need to deliver product quite fast and Flutter is the best choice for this.

How to Organize A Flutter Project

Rafat Jamader Meraz — Sat, 22 Aug 2020 15:04:30 +0000

Flutter is a trending mobile framework in nowadays. Small & medium companies are focusing on flutter for it's awesome UI and native performance. We are not going to explain to you about Flutter here. Because the main purpose of this blog is to help you to organize your Flutter project more efficiently.

At first, I am gonna clear you about one thing and that is "There is no rule to organize a flutter project". But as a beginner, you should follow some basic project structure that will help your project more scaleable later. Moreover, you will able to maintain your project easily.

If you are a beginner, then maybe you have already faced some common issues during your medium size projects.

Unable to find a specific file
Writing a block of codes again and again
Mixing up User Interface and back-end code
Unlimited local variable
App causing of battery drain

So how to resolve these problems? Okay, you have to follow some basic rules for file structure as a beginner. Then You can minimize these problems easily.

Create a good project structure

The first and most important part of organizing your project is to make a good project structure. If you are unable to separate your codes for different segments then you be lost in at a point. So you need to maintain your code hierarchy properly. Let's see an example project code structure.

As you already know that all the codes for the Flutter project which we write in dart are located in lib folder. So let's see the inner package structure for our project one by one.

src

As you can see that the main.dart file is out of src and we will only write the application codes in this src package. When main.dart will execute as root file we will redirect it to the src\app.dart file which will contain all the MaterialApp/CupertinoApp components.

business_logic

All the logical parts of the project will be located in this package.

blocs: If you are following the BLoC pattern then you can keep your blocs here.
models: Models/Pojo classes.
services: There are three types of services - api_services, database_services, shared_prefs_services. You will put your specific types of codes in the specific type of service packages.
utils: This package contains all the constants files.

views

We will put our User Interface codes insides our views package.

ui: All the User Interface code files.
utils: This package contains the reusable widgets files and the constants value files.

There is another important folder which we have to organize and that is assets folder. As we know that there are no pre-defined assets folder in flutter default project hierarchy. We create a new folder as assets and initialize it into pubspec.yaml file. Then you can follow below the structure for your assets folder.

You can find this project structure in here