π Hey, welcome to Scalable Flutter App.
Watch/star this repo to be notified when updates are pushed.
Scalable Flutter App is a starter template for Flutter apps.
It's designed to be scalable and easy to maintain. And should save you weeks of development time.
To get started, click on the green "Use this template" button on the top-right.
Always keep up to date:
- Flutter
- Cocoapods
- Firebase CLI
I'm Milos Jokic and I:
- built my first mobile app in 2007
- grew my apps to 214k users and $106,140 revenue.
- built apps for 10 Toptal clients.
And now I run a 6-figure devs agency where we launch MVPs in 4 weeks using Flutter & Firebase.
You can find me on:
Feature | Starter | Pro |
---|---|---|
Platforms: Android, iOS, web | β | β |
Scalable Architecture using flutter_bloc | β | β |
Navigation using go_router | β | β |
Scalable App Styling | β | β |
GitHub Actions - code and formatting check | β | β |
Responsive Design | β | β |
UserMockProvider | β | β |
Profile Page | β | β |
Settings Page: sign out, app version... | β | β |
Legal: Terms, Policy, Data Deletion | β | β |
Google Fonts | β | β |
Sign in and Sign Up Pages | β | β |
Input Validators | β | β |
Cached network image | β | β |
Email Support | β | β |
Lifetime Updates | β | β |
Firebase Project Integration | β | β |
Firebase Authentication | β | β |
Firebase Remote Config | β | β |
Firebase Crashlytics | β | β |
Firebase Firestore | β | β |
Firebase Analytics | β | β |
Firebase Storage | β | β |
Google Sign In | β | β |
Apple Sign In | β | β |
Common Cubits | β | β |
In App Purchases (RevenueCat) | β | β |
App Store Review Request | β | β |
Local Notifications | β | β |
Remote Notifications (Firebase) | β | β |
HTTP Requests | β | β |
Local Storage | β | β |
Permissions | β | β |
Environments | β | β |
Localization | β | β |
Dark Mode | β | β |
Connectivity check | β | β |
Hive - local database | β | β |
MixPanel - analytics | β | β |
Android - Release Signing | β | β |
Onboarding | β | β |
Forgot Password | β | β |
π BONUS: Scalable Firebase Backend Template | β | β |
Grab Scalable Flutter App - Pro Here
The code architecture is based on flutter_bloc architecture proposal.
There are 4 layers:
- UI (Flutter Widgets)
- BLoC (stateful business logic)
- Repository (high-level API)
- Provider (low-level implementation)
And there's only 1 communication rule that we must follow:
The layer can only call the one layer below it.
That means that:
- UI can only call BLoC
- BLoC can only call Repository
- Repository can only call Provider
- Provider can only call external services (Firebase, HTTP, etc.)
And we avoid same-layer communication (as it creates interdependencies):
UserRepository
callingAuthRepository
is not allowed.UserCubit
callingUserRepository
andAuthRepository
is allowed.
When creating Providers, Repositories, and Cubits we follow this rule:
- Providers are created top-level (so that they can be used in multiple Repositories)
- Repositories are created top-level (so that they can be used in multiple Cubits)
- Cubits are created in the router builder callbacks (so that they're accessible only where needed)
- Cubits that are used in multiple screens are created top-level
Styling is based on Google's Material Design.
App-wide styling is defined in core/app/style.dart
and is easy to update.
Here's a quick tip on custom Widget params. There are 2 Widget param types:
- data (user, title, ...)
- style (colors, paddings, ...)
Our custom Widgets should only hava data params.
And the style should be done app-wide (in style.dart
).
That way all of our UI is consistent and easy to update.
To change the font:
- Go to Google Fonts and select a font.
- Download the font files.
- Add the font files to
assets/fonts
(remove the old ones). - Update
style.dart
with the new font (i.e.return GoogleFonts.rubikTextTheme(textTheme)
).
I've found that turning on these 2 settings in GitHub repo settings helps a lot:
Always suggest updating pull request branches
Automatically delete head branches
While GetX, Provider, Riverpod, MobX, Redux, etc. are all great solutions, most of them are too forgiving. They allow us to access and change state globally.
Whereas flutter_bloc forces us to have BuildContext
in order to access and change the state. The stricter the rules, the harder it is to make mistakes.
And flutter_bloc has a great architecture proposal that scales well.
Scalable Flutter App is for developers, agencies, and founders who want to:
- build scalable Flutter apps
- save weeks of development time
- learn best practices
I can only recommend what I've used myself:
- Flutter Codelabs
- Flutter YouTube
- Effective Dart
- and just keep building apps and getting better with each one :)
If you don't need a feature:
- delete its imported package in
pubspec.yaml
- delete the code that uses the feature
If you want Firebase integration, notifications, in-app purchases and more, get the Pro version here:
Build your app icon in minutes (free): Icon Kitchen
Cool illustrations that match your app's colors (free): unDraw
CI/CD for mobile apps (free & paid): Codemagic
Want me to launch your MVP in 4 weeks (premium)? Go to App Launch Program
Need a Flutter Expert (paid)? Go to Flutter Devs Board
Found an issue or want to request a feature? Open an issue
Have a question? Ask me on LinkedIn or Twitter.
Enjoying Scalable Flutter App? Leave a testimonial