Step 3 — Battle of the Boilerplates
Let me tell you a little about the development environment I will be using for this adventure now that we’re starting to get into some code.
- Windows 10
- VSCode
- Github
All right then.
Setting up Boilerplate Option 1
After forking, renaming, branching, and cloning the repo I was ready to spin it up in VSCode.
It is beyond the preview of this chronicle to go into such details as setting up a VSCode Flutter environment, but here’s a tasty link.
Next up I also had to spin up a new Firebase project at
Again, I will not go into this procedure, it is pretty straightforward and there is lots of info on the webs.
For the sample app to run there were a few steps to set up the Firebase project and a few modifications to the code and config files to match said project settings. I just followed the handy README instructions on the original repo.
And then I launched it as a web app and viola, it ran, so that’s a great start.
Setting up Boilerplate Option 2
Oh, brother. Read twice, code once. Upon reading the fine print (README) on this repo, I discovered that the web build doesn’t exactly work since it is using a different auth system (appauth.io) instead of Firebase and that system does not work on the web.
In theory, I could try to replace the auth with Firebase Authentication, but that defeats the purpose of doing as little as possible.
In the next post, I will dive a little bit into what comes with this boilerplate and the choices made by Mr. Code With Andrea in this handy little starter repo.
Stay tuned and stay chuegy friends.
