Skip to content

1. Lab: Setup & Flutter

Estimated time to read: 13 minutes

In this lab we’ll verify that your Flutter environment is set up correctly and you’ll build your first app.

1.1 Preparation

Please complete the following tasks before your first lab session. Estimated time: 4 hours.

1.1.1 Flutter Setup

Individual preparation

  1. Install Flutter. If you already have Flutter installed, ensure it is up to date by running flutter upgrade.
  2. Familiarize yourself with the fundamentals of Dart, focusing on its similarities to and differences from other programming languages you are familiar with. Then, create a simple console application that showcases some of Dart's unique features.
  3. Copy the code of Counter App, run the application, try to understand it and make one minor modification. The application should run in your browser and in the Android Emulator. If you run into any problems: We will fix them during the lab.
  4. Complete the Flutter Codelab by reading through the material and coding along as needed. This will give you an overview of how Flutter differs from other programming environments you may be familiar with.

1.1.2 Gitlab

If you are not familiar with gitlab, watch my video 📹 git-Kurzeinführung (Basics) and learn the basics of markdown and project management with gitlab.

1.2 During the lab

  • We will address any questions and installation problems you have.
  • You run your console application.
  • You run your flutter application.

1.2.1 Use Gitlab

Clone the repository and take your first steps in the shared project:

  1. Create an issue (use one of the templates provided) describing your console application, and move it to Doing.
  2. Copy your console application into an appropriate directory, then commit it — referencing the issue number in your commit message.
  3. Move the issue to Done.
  4. Repeat this process for your Flutter application.

fetch/pull

Before every change, new file, or new directory: always run fetch/pull first to incorporate your teammates' latest changes.

Take care with your commit messages — they should be clear and descriptive. Take a moment to discuss them with your neighbour and agree on a consistent style. Read and discuss the conventional commits. Include the related issue number in your commit message. This automatically adds a comment to the issue, providing clear visibility into the progress and status of that issue.

1.2.2 Why GitLab Matters

The GitLab repository documents the development process of your project.

  • Issues organize the work
  • Commits make progress and individual contributions visible
    • mention the related issue number in your commit!
  • MkDocs pages document and explain the project

Important:

GitLab issues manage the work.
MkDocs pages document and explain the work.