Project Highlights:
- Deliver an application for both platforms extremely quickly
- Increase transparency and efficiency with BLoC architecture
- Reasons to choose Flutter for this solution
Designing a Mobile CRM With Flutter
Client and Business goals:
Landscape Management Network Inc. (LMN), is the leading business management software provider in the landscape industry. Their goal is to provide simple, but powerful SaaS solutions that help landscape contractors manage and build profitable businesses.
Project Description:
The product is a mobile CRM application integrated with the existing web CRM for landscape contractors to manage the leads and clients in their sales pipeline.
Applied Technologies:
Flutter for both iOS & Android platforms, Dart as a programming language, Google Places integration, Business analysis, UI / UX Design, Quality assurance, Fixed Price Scope Controlled project flow.
Deliver an Application for Both Platforms Extremely Quickly
- The goal was to design an app and integrate it into the existing software ecosystem. This was not hard to do due to a stable API that was used to integrate the new app over. Most of the difficulties were related to the timeline, which we had to contend with. So, when choosing the technology to go with, we were focused on the development speed each option offered. Flutter was the fastest to design this app among stable and scalable cross-platform frameworks.
- After succeeding with the release, MobiDev team went ahead with new features design and became involved in сurrent Web CRM updates and improvements.
Increase Transparency and Efficiency With BLoC Architecture
- For the architecture design, we separated UI and business logic. We developed classes to communicate with the server-side along with using asynchronous programming with futures. It brought us the ability to code “page templates” and speed up the development of application screens.
- Such advantages eventually lead us to a significant efficiency during design, development and polishing stages.
Here are the reasons why we've chosen Flutter for this project:
Dependencies: There was no "legacy" or dependencies within existing components and there was nothing we had to take into account.
Design: There's a variety of standard Flutter UI widgets (Material and Cupertino design). So, for the design stage, we were primarily using standard Flutter components. It minimizes the development timeline.
Performance: Flutter performs the same as a native Android or iOS app due to Dart language and Flutter architecture with no bridging with native components.
Asynchronous architecture: As there were plenty of server/app communications to be handled, it was important to build the app to be able to run smoothly. Additionally, Flutter provided the means to separate UI from the business logic.
Stable: It's officially released and tested. Moreover, Flutter policy claims to provide compatibility with its updates and not to "break" older apps with new features.
I like working ahead of schedule with my projects. And with this particular one, Flutter allowed us to go beyond the speed of light. It definitely would take us at least 30% more time with native development if we were not using Flutter.
