01 · Start well

Your development environment and learning plan

Lesson 1 · 90 minutes including practice. Read, run the example, complete the task, then compare your work with the solution.

By the end of this lesson

  • Explain what Flutter and Dart each do.
  • Run a clean Flutter project and record the toolchain.
  • Use the course pack and checkpoints without skipping prerequisites.

What you are learning

Dart is the language in which you express data and behaviour. Flutter uses that code to describe an interface and coordinate input, rendering and platform services. Learning widget names alone is not enough: an app must also validate information, preserve state, handle failures and produce a release someone else can install.

Prepare a reproducible workspace

Use the official installation guide for your operating system. Install the stable Flutter SDK, an editor and one target device. Android requires the Android toolchain; iOS builds require macOS and Xcode. A web browser is useful for early UI work, but our SQLite capstone targets Android and iOS. Run flutter doctor -v and resolve the warnings for the platform you intend to use. You do not need every platform configured.

Create and inspect a project

Run flutter create learning_lab, enter the directory and run flutter run. Read lib/main.dart, pubspec.yaml and the generated test. The pubspec describes the package and its dependencies; it is not where application secrets belong. Use Git from the first working version. Commit the app lockfile so another learner can resolve the same dependency versions.

How to use this course

Follow the lessons in order. Each has an outcome, explanation, example, practical task and a hidden worked solution. Keep a learning log with the command you ran, the result and one question. The download contains exercises, reference solutions, an API lab and a complete capstone. Estimated practice time is 60–90 hours, depending on your starting point; it is not a claim about video length. Do not treat a completed reading as a completed skill.

Version discipline

Write flutter --version and dart --version into your log. Use the tested toolchain recorded in the download for reproducing the reference project. Current Flutter documentation describes the newer standalone Material library; the course explains the corresponding import and dependency rather than assuming every older tutorial still applies.

Worked example

The example below is a focused extract or command/configuration example, not a standalone program. Apply it in the context described by the lesson. Complete reference projects for the assessed builds are included in the course pack.

// terminal commands, not Dart
flutter --version
flutter doctor -v
flutter create learning_lab
cd learning_lab
flutter run
flutter analyze
flutter test

Your practical task

Run the generated app, change the visible title, and run the checks. Save a screenshot and a Git commit. Write down which doctor warnings matter for your chosen target and which do not.

Worked solution and reasoning — attempt the task first

The title change should appear after hot reload when the edit is inside the widget tree. A successful doctor check for Android does not make iOS builds possible on Windows. Your evidence is a running app, a clean analyzer and the generated tests passing. If the test expects the old UI text, deliberately update that assertion to match the intended behaviour rather than deleting the test.

Check your understanding

Does hot reload install a new Android permission?

No. Native configuration changes generally require stopping and rebuilding the application.

Why keep a lockfile for this app?

It records resolved dependency versions so the reference build can be reproduced. Review dependency updates as changes, then rerun the checks.

Official reference

Read the relevant official documentation. The reference extends this lesson; the exercise and explanation above are original course material.