5 Things I do when starting a new Flutter project

Thinking about a project name

Although it sounds trivial, the first thing I do when creating a new Flutter project is to think about how I want to * name the project*. This is necessary for naming the project directory.

The name of the project will also be part of the bundle identifier in iOS and the package name in Android. They can be a bit tiresome to change, so better think of a meaningful name right away.

Project name and platforms are the first things that I check when creating a new Flutter project

2.) Clean up pubspec.yaml

By default, pubspec.yaml includes a tremendous number of comments. Although they might be useful if you are new to Flutter, I like to get rid of all of them. In my opinion, the comments make it hard to understand the content of the file.

3.) Clean up main.dart

Next, I like to remove all the sample code from the main.dart file. Usually, this is what my main.dart file looks like when I start a new project:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18

import 'package:flutter/material.dart';
import 'package:simple_riverpod_architecture/home_page.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      debugShowCheckedModeBanner: false,
      home: HomePage(),
    );
  }
}

Additionally, I added a new file called home_page.dart and added the most basic implementation:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12

import 'package:flutter/material.dart';

class HomePage extends StatelessWidget {
  const HomePage({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return const Scaffold(
      body: Center(child: Text('Hello World')),
    );
  }
}

4.) Run the app

Now, that I have the most basic app possible, I will run the project. This way, I make sure everything is set up successfully. Since Flutter supports hot reload, I now also see my develop process immediately as I code along.

5.) Initialize git

Lastly, I initialize version control on the project. This can be simply done by running

git init
git add .
git commit -m "initial commit"

This initializes git on the projects, adds all files and creates a first commit. Having set up version control allows me to check what changes I have made since the last commit and lets me roll back changes.

I do not set up an origin right away, this I do later when I decide I want to have my project saved in a repository.