Flutter Conventions & Best Practices
Flutter Conventions & Best Practices
Dart 3.x Features
Pattern Matching
String describeUser(User user) {
return switch (user) {
User(role: 'admin', isActive: true) => 'Active administrator',
User(role: 'user', isActive: true) => 'Active user',
User(isActive: false) => 'Inactive account',
_ => 'Unknown status',
};
}
Records
(int, String) getUserInfo() => (123, 'John Doe');
final (id, name) = getUserInfo();
Sealed Classes
sealed class Result<T> {}
class Success<T> extends Result<T> {
final T data;
Success(this.data);
}
class Error<T> extends Result<T> {
final String message;
Error(this.message);
}
File Naming Conventions
- Files:
snake_case.dart - Classes:
PascalCase - Variables/Functions:
camelCase - Constants:
lowerCamelCaseorSCREAMING_SNAKE_CASEfor compile-time constants
// user_controller.dart
class UserController extends GetxController {
static const int maxRetries = 3;
static const String BASE_URL = 'https://api.example.com';
final userName = 'John'.obs;
void fetchUserData() {
// ...
}
}
Directory Organization
Layer-first (recommended for Clean Architecture):
lib/
├── domain/
├── data/
└── presentation/
Feature-first (alternative):
lib/
└── features/
├── auth/
│ ├── domain/
│ ├── data/
│ └── presentation/
└── profile/
Null Safety
// Use late for non-nullable fields initialized later
class MyController extends GetxController {
late final UserRepository repository;
void onInit() {
super.onInit();
repository = Get.find();
}
}
// Use ? for nullable types
String? userName;
// Use ! only when absolutely certain
final name = userName!; // Use sparingly
// Prefer ?? for defaults
final displayName = userName ?? 'Guest';
Async/Await Best Practices
// Use async/await for asynchronous operations
Future<User> fetchUser(String id) async {
try {
final response = await client.get(Uri.parse('/users/$id'));
return User.fromJson(jsonDecode(response.body));
} on SocketException {
throw NetworkException();
} catch (e) {
throw UnknownException(e.toString());
}
}
// Use Future.wait for parallel operations
Future<void> loadAllData() async {
final results = await Future.wait([
fetchUsers(),
fetchSettings(),
fetchPreferences(),
]);
}
// Use unawaited for fire-and-forget
unawaited(analytics.logEvent('page_view'));
Code Organization Within Files
class MyClass {
// 1. Constants
static const int maxRetries = 3;
// 2. Static fields
static final instance = MyClass._();
// 3. Instance fields
final String id;
final _isLoading = false.obs;
// 4. Constructors
MyClass(this.id);
MyClass._();
// 5. Getters/Setters
bool get isLoading => _isLoading.value;
// 6. Lifecycle methods
void onInit() {}
// 7. Public methods
void publicMethod() {}
// 8. Private methods
void _privateMethod() {}
}
Widget Best Practices
// Prefer const constructors
class MyWidget extends StatelessWidget {
const MyWidget({Key? key}) : super(key: key);
Widget build(BuildContext context) {
return const Text('Hello');
}
}
// Extract widgets for reusability
class UserCard extends StatelessWidget {
final User user;
const UserCard({Key? key, required this.user}) : super(key: key);
Widget build(BuildContext context) {
return Card(
child: _buildContent(),
);
}
Widget _buildContent() {
return Column(
children: [
Text(user.name),
Text(user.email),
],
);
}
}
More from kaakati/rails-enterprise-dev
getx state management patterns
GetX controllers, reactive state, dependency injection, bindings, navigation, and best practices
52tailadmin ui patterns
TailAdmin dashboard UI framework patterns and Tailwind CSS classes. ALWAYS use this skill when: (1) Building any dashboard or admin panel interface, (2) Creating data tables, cards, charts, or metrics displays, (3) Implementing forms, buttons, alerts, or modals, (4) Building navigation (sidebar, header, breadcrumbs), (5) Any UI work that should follow TailAdmin design. This skill REQUIRES fetching from the official GitHub repository to ensure accurate class usage - NEVER invent classes.
39mvvm-architecture
Expert MVVM decisions for iOS/tvOS: choosing between ViewModel patterns (state enum vs published properties vs Combine), service layer boundaries, dependency injection strategies, and testing approaches. Use when designing ViewModel architecture, debugging data flow issues, or deciding where business logic belongs. Trigger keywords: MVVM, ViewModel, ObservableObject, @StateObject, service layer, dependency injection, unit test, mock, architecture
36rails localization (i18n) - english & arabic
Comprehensive internationalization skill for Ruby on Rails applications with proper English and Arabic translations, RTL support, pluralization rules, date/time formatting, and culturally appropriate content adaptation.
34rspec testing patterns
Complete guide to testing Ruby on Rails applications with RSpec. Use this skill when writing unit tests, integration tests, system tests, or when setting up test infrastructure including factories, shared examples, and mocking strategies.
31ruby oop patterns
Comprehensive guide to Object-Oriented Programming in Ruby and Rails covering classes, modules, design patterns, SOLID principles, and modern Ruby 3.x features
31