Introduction to the course, prerequisites, and goals

About this course

Introduction

About Module 2

Overview of the technology used in this course

About Flutter and Dart

Everything you need to start building Flutter apps

Hardware & software setup

\`flutter create\` and the Flutter project structure

Creating a Flutter app

How to build your app for emulators and physical devices

Running your app

Integrating external packages and libraries

Pub packages

Setting the app name, icon, and bundle ID

Packaging for the App Store and Google Play

Setting up your environment and packaging apps

Getting Started

About Module 3

A 5-minute introduction to the Dart language

Dart cheat sheet

Flutter in a nutshell

Setup: State

Setup: Theming

Setup: Navigation

Setup: Scaffold

Learn the basics you need to build any kind of app

Creating A Seed App

About Module 4

Text, app bar actions, and widgets that wrap every page

Creating the widget and route

Stubbing data

Widgets that wait for data

Column, Row, Padding, spacing, and alignment

Layout basics

Image

Table layouts, expansion panels, and rich text

Responsive layouts, part 2

ListView, SingleChildScrollView, and Scrollbar

Scrolling layouts

How to think about layout, infinite constraints, and unbounded size

Layout problems

TextButton, OutlinedButton, FilledButton, ElevatedButton, and button styles

Buttons

The Profile Page

About Module 5

VoiceOver on iOS

Testing accessibility on an Android emulator

TalkBack on Android

Accessibility Widgets

Making sure your app works with a screen reader

Accessibility

About Module 6

Shared preferences

HTTP requests

Login and authentication

State management with Provider and Consumer

Managing user state

Storage and HTTP

About Module 7

Building and sorting a DataTable with DataTableSource

Data tables

Using fl_chart for responsive visualizations

Charts and graphs

Building data visualizations that impress

Tables and Charts

About Module 8

Simple animations

Custom paint

Custom animations

Off-the-shelf transitions, custom drawings, and fine-tuned animations

Animations

About Module 9

flutter_test and the Flutter unit testing API

Unit tests

Testing UI interactions on individual widgets

Widget tests

Testing your entire app with automated interactions

End-to-end tests

Unit tests, widget tests, and end-to-end tests

Testing

Congratulations

Wrapping up

Flutter is a popular cross-platform development framework. It's packed with off-the-shelf features and focused
on developer ergonomics, which means you can build faster and deploy to more platforms with fewer dependencies.
Some parts of the framework will catch you by surprise, though, especially if you're used to developing for the
web or writing native apps. This course will walk you through the creation of a Flutter app from setup to
final package and help you develop a mental model that will carry you through the most common problems Flutter
devs encounter.

By the end of these 10 modules you'll have built:
- A Flutter seed project that can manage state, swap out color palettes, and handle deep links
- An accessible, error-resistant profile page that fetches data from a web API
- A responsive data table and data-driven visualizations
- A complete app ready to deploy to iPhone and Android

This course includes sample code, explained step-by-step, that you can reuse for any Flutter app you build.

It's taught by Isaac Lyman, author of _Your First Year in Code_ and Top 10 Author on The DEV Community.

After completing Line-of-Business Apps with Flutter 3, developers have the skills to build mobile apps backed by their
choice of server technologies, taking advantage of the incomparable performance, speed-to-value, and developer
experience of Flutter and Dart.

What developers are saying

Flutter

Dart

Bring your mobile app ideas to life on every device

### Build Better Mobile Apps with Flutter

Smartphones are the most popular computing devices in the world, and mobile apps are the best way to reach
technology consumers. But building fully native apps means learning two or more completely different sets of
programming languages, UI frameworks, layout systems, and developer toolkits. Other cross-platform frameworks
have tried to make this process easier, but none of them have achieved the popularity, performance, or resilience
of Flutter.

With Flutter, you'll avoid several problems you may have had with other app frameworks:

- Publish native app packages for iOS, Android, Windows, macOS, and Linux, all from a **single codebase**, without
writing a single line of native code.
- Write **faster, safer code** with the familiar syntax, type safety, and null safety of the Dart programming language.
- Flutter is an **all-in-one component library and toolkit**: spend your time building components and writing application logic
instead of fiddling with toolchain configuration and searching for 3rd-party packages.
- Never worry about the way your app looks on different devices; with Flutter's **built-in rendering engine**
and **logical pixel scaling**, your app will look the same on every screen, everywhere.

### Be Prepared for Any Challenge

Flutter is an easy-to-learn, top-rated technology for developers, but it doesn't come without gotchas. In this course, you'll
learn to breeze right through some of the hardest parts of Flutter development:

- Responsive design, complex layouts, and breakpoints
- Layout errors and infinite constraints
- Hand-drawn components
- Custom animations, tickers, and tweens
- State management and data persistence

### Start Building Real Apps Faster

This course won't waste any time teaching you what an `if` statement is. You'll be able to use the
programming experience you already have and jump straight into building mobile apps with Dart and Flutter.

Along the way, you'll build skills you can use immediately for any app you dream up:

- By the end of Module 2, you'll have already packaged a Flutter app for distribution on the iOS and Android
app stores.
- By the end of Module 3, you'll have a seed app you can use for any project.
- By the end of Module 4, you'll know how to build responsive layouts and use the most common types of widgets.
- By the end of the course, you'll have built an **accessible**, **interactive**, **server-backed** app with **custom animations**
and **three types of automated tests**.

Along the way, you'll discover Flutter's secret: it's not only the easiest way to build cross-platform mobile
and desktop apps, it's the easiest way to deliver **any* kind of technological experience, **period**. Not even the web, with
its variety of frameworks and tools, can match the development speed and polished UI of a Flutter app.

Build cross-platform iOS and Android apps faster than you thought possible

In this course you'll build a corporate app and package it for iPhone and Android from a single codebase.

Flutter is a popular and feature-rich multi-platform development toolkit, but it's got some surprises for
traditional web and desktop developers. You'll learn how to think in the Flutter way and build fast, maintainable,
visually appealing apps.

Line-of-Business Mobile Apps with Flutter and Dart

Build a secure login modal with HTTP authentication and persistent cookies

Build responsive, nested layouts and intuitive user interactions

Build fast, informative data visualizations

How to build and package apps for iOS and Android from a single codebase

Why Flutter and Dart are a perfect match for multi-platform apps

The Flutter paradigm for layout and components

How to keep your Flutter app fast and responsive

State management, server requests, accessibility, and more

Now that you have some data to work with, you can switch out your "Profile page works!" text for the (stubbed) user's name. Once you have data coming through, you'll lay out the page in more detail.

You'll need to get the RevExUser object you created in the last lesson. Remember that it's returned after a short delay.

To wait for data in a build method, you can use the 

 widget. FutureBuilder accepts a Future and rebuilds its child every time the state of the Future changes, so you can deal with each possible state:

Update your RevExProfilePage build method like this:

@override
Widget build(BuildContext context) {
  return RevExScaffold(
    title: "Profile",
    body: FutureBuilder(  // <= FutureBuilder added here
      future: myFuture,
      builder: (context, snapshot) {
        return const Text(
          "Profile page works!",
        );
      }
    ),
  );
}

 widget will get you most of the way (reminder: you can see context actions using 

 in Android Studio). You can then replace 

 will be underlined in red, of course, because it doesn't exist. You may be tempted to do this:

// BAD IDEA
future: revExGetUser(),
// BAD IDEA

The reason you shouldn't is that RevExProfilePage will get rebuilt (that is, the build method will be called) any time it needs to change—theoretically, as often as once per frame. You don't want to call 

 won't want to do that when you have it talking to a real web server. Ideally, you should call it only once each time the user visits the Profile page.

To achieve that, turn RevExProfilePage into a StatefulWidget. If you click 

 in the class declaration and pull up your context actions, you'll see a 

 option, which handles the whole process for you. This is the result:

class RevExProfilePage extends StatefulWidget {
  const RevExProfilePage({super.key});

  @override
  State<RevExProfilePage> createState() => _RevExProfilePageState();
}

class _RevExProfilePageState extends State<RevExProfilePage> {
  @override
  Widget build(BuildContext context) {
    return RevExScaffold(
      title: "Profile",
      body: FutureBuilder(
        future: myFuture,
        builder: (context, snapshot) {
          return const Text(
            "Profile page works!",
          );
        }
      ),
    );
  }
}

Now RevExProfilePage has two parts: a StatefulWidget subclass and a State subclass. The first one is for constructor fields (stuff the parent widget will pass in), and the second one is for state the widget itself needs to handle. Since you want to get a Future from 

 and preserve it across frames, you'll need to put it in State.

Create a field to hold that piece of state:

class _RevExProfilePageState extends State<RevExProfilePage> {
  final Future<RevExUser> user;
  ...

 Write a trailing initializer statement on the constructor:

---
title: Widgets that wait for data
description: Futures and widget state initialization
privateVideoUrl: 
isPublicLesson: true
code: https://gitlab.com/fullstackio/books/newline-course-apps/isaac-lyman-line-of-business-apps-with-flutter-3/-/tree/main/App/revenue_explorer_complete_app
---

Now that you have some data to work with, you can switch out your "Profile page works!" text for the (stubbed) user's name. Once you have data coming through, you'll lay out the page in more detail.

## FutureBuilder and StatefulWidget

You'll need to get the RevExUser object you created in the last lesson. Remember that it's returned after a short delay.

To wait for data in a build method, you can use the [`FutureBuilder`](https://api.flutter.dev/flutter/widgets/FutureBuilder-class.html) widget. FutureBuilder accepts a Future and rebuilds its child every time the state of the Future changes, so you can deal with each possible state:

1.  Waiting
2.  Success (non-null value)
3.  Success (null value)
4.  Error

Update your RevExProfilePage build method like this:

```dart
@override
Widget build(BuildContext context) {
  return RevExScaffold(
    title: "Profile",
    body: FutureBuilder(  // <= FutureBuilder added here
      future: myFuture,
      builder: (context, snapshot) {
        return const Text(
          "Profile page works!",
        );
      }
    ),
  );
}
```

:::tip
The **Wrap with Builder** context action on the `Text` widget will get you most of the way (reminder: you can see context actions using **cmd + period** in VS Code or **option + return** in Android Studio). You can then replace [`Builder`](https://api.flutter.dev/flutter/widgets/Builder-class.html) with `FutureBuilder`, add the `future` field, and add the `snapshot` argument to the `childBuilder` function.
:::

`myFuture` will be underlined in red, of course, because it doesn't exist. You may be tempted to do this:

```dart
// BAD IDEA
future: revExGetUser(),
// BAD IDEA
```

The reason you shouldn't is that RevExProfilePage will get rebuilt (that is, the build method will be called) any time it needs to change—theoretically, as often as once per frame. You don't want to call `revExGetUser()` 60+ times per second, and you _really_ won't want to do that when you have it talking to a real web server. Ideally, you should call it only once each time the user visits the Profile page.

To achieve that, turn RevExProfilePage into a StatefulWidget. If you click `StatelessWidget` in the class declaration and pull up your context actions, you'll see a **Convert to StatefulWidget** option, which handles the whole process for you. This is the result:

```dart
class RevExProfilePage extends StatefulWidget {
  const RevExProfilePage({super.key});

  @override
  State<RevExProfilePage> createState() => _RevExProfilePageState();
}

class _RevExProfilePageState extends State<RevExProfilePage> {
  @override
  Widget build(BuildContext context) {
    return RevExScaffold(
      title: "Profile",
      body: FutureBuilder(
        future: myFuture,
        builder: (context, snapshot) {
          return const Text(
            "Profile page works!",
          );
        }
      ),
    );
  }
}
```

Now RevExProfilePage has two parts: a StatefulWidget subclass and a State subclass. The first one is for constructor fields (stuff the parent widget will pass in), and the second one is for state the widget itself needs to handle. Since you want to get a Future from `revExGetUser()` and preserve it across frames, you'll need to put it in State.

Create a field to hold that piece of state:

```dart
class _RevExProfilePageState extends State<RevExProfilePage> {
  final Future<RevExUser> user;
  ...
```

There are two ways to initialize the `user` field.

**Option 1:** Write a trailing initializer statement on the constructor:

```dart
class _RevExProfilePageState extends State<RevExProfilePage> {
  final Future<RevExUser> user;

  _RevExProfilePageState() : user = revExGetUser();
  ...
```