⚠️ This lesson is retired and might contain outdated information.

Flutter Project Walkthrough

nader dabit
Instructornader dabit
Share this video with your friends

Social Share Links

Send Tweet
Published 5 years ago
Updated 2 years ago

In this lesson we’ll walk through the example project that the Flutter CLI created for us & discuss the files & folders that were created for us.

Instructor: [00:01] Now that we've created our Flutter application, let's open the project in our text editor and walk through some of the files and folders that were created for us.

[00:10] First, we have the Android and iOS folders which hold the platform-specific code for each platform. You shouldn't have to make many changes in these folders unless you're going to do any platform-specific customization.

[00:26] Lib is the main folder where you will write all of your application code. The default project configuration template only contains the main.dart file which is the entry point for the Flutter application.

[00:42] As the name suggests, the Test folder is used to store and manage testing code for the app. The gitignore file is used to store the list of files which need to be ignored when the source code is uploaded or checked into any Git versioning system.

[00:59] In many languages and environments, a package manager is used to manage third-party or resusable components and modules. In the case of Dart, the package manager is called Pub. This is style is used by Pub to manage the packages for this project.

[01:14] Just like .packages, pubspec.lock is used by the Pub package manager in order to get the concrete versions and other identifying information for every dependency a package relies on.

[01:26] Pubspec.yaml is the file that you'll use when you need to manage third-party packages or dependencies for your application. This file is used by the Pub package manager to get and load the packages used in the project.

egghead
egghead
~ 2 hours ago

Member comments are a way for members to communicate, interact, and ask questions about a lesson.

The instructor or someone from the community might respond to your question Here are a few basic guidelines to commenting on egghead.io

Be on-Topic

Comments are for discussing a lesson. If you're having a general issue with the website functionality, please contact us at support@egghead.io.

Avoid meta-discussion

  • This was great!
  • This was horrible!
  • I didn't like this because it didn't match my skill level.
  • +1 It will likely be deleted as spam.

Code Problems?

Should be accompanied by code! Codesandbox or Stackblitz provide a way to share code and discuss it in context

Details and Context

Vague question? Vague answer. Any details and context you can provide will lure more interesting answers!

Markdown supported.
Become a member to join the discussionEnroll Today