Flutter App Developer

---
title: "Flutter App Developer"
description: "Build, test, and debug cross-platform mobile and web applications with Flutter and Dart — from project scaffolding through state management, platform integration, performance optimization, and app store deployment."
author: AgentArmory
license: Proprietary
---

# Flutter App Developer

Build, test, and debug cross-platform mobile and web applications with Flutter and Dart — from project scaffolding through state management, platform integration, performance optimization, and app store deployment.

## Table of Contents

- [When to Use](#when-to-use)
- [Triggers](#triggers)
- [Methodology](#methodology)
- [Dos](#dos)
- [Don'ts](#don'ts)
- [Pitfalls](#pitfalls)
- [Validate Before Shipping](#validate-before-shipping)
- [Cross-Skill Hints](#cross-skill-hints)

## When to Use

Use when asked to build, refactor, or debug a Flutter application. Also when planning a new cross-platform mobile project, choosing state management approaches, optimizing widget rebuild performance, integrating with native platform APIs, or preparing for app store deployment. Do NOT use for pure web applications (use web frameworks instead), backend code, or database schema design.

## Triggers

"flutter", "dart", "cross-platform mobile app", "flutter app", "iOS and Android app", "build a mobile app", "flutter widget", "dart language", "flutter state management", "flutter riverpod", "flutter bloc", "getx", "flutter firebase", "flutter performance", "flutter build", "flutter test", "flutter release", "app store deployment", "play store deployment", "flutter CI/CD", "flutter secure storage", "platform channel"

## Methodology

### Step 1: Project Setup & Architecture

Do NOT start writing widgets first. Set up the project structure and architecture pattern first.

1. **Create the project**:
   ```
   flutter create --org com.yourcompany --project-name app_name --platforms ios,android,web .
   ```
   Add platforms as needed: `--platforms ios,android,web,macos,windows,linux`

2. **Choose the dependency injection and state management approach**:
   - **Riverpod** (recommended for most apps): `flutter pub add flutter_riverpod riverpod_annotation dev:riverpod_generator dev:build_runner`
   - **BLoC**: Use for apps with complex event-driven flows. `flutter pub add flutter_bloc equatable`
   - **Provider** (legacy, still maintained): Only if maintaining an existing codebase
   - **GetX**: Controversial — avoid for new projects due to lack of type safety and implicit dependencies

3. **Set up the folder structure**:
   ```