Thus, here are a few lessons learned and how hopefully they can help you if you are also using it for the first time and especially if you are deploying an AngularJS app to Firebase.

Scenario 1: Your deploy is complete and you visit the URL and get this:

Here is the issue:

There is a prompt in the firebase init that asks: What do you want to use as your public directory? Choosing “public” because it is default is not really a good idea. You MUST choose the folder where your index.html is found. In many apps this is the root folder. In my case, with AngularJS, the index.html is not in the root directory. Where is it? Lets look at Scenario 2.

Scenario 2: Because it is AngularJS

When you run firebase init, choose your ‘dist’ folder as this is where your website is “built.” It also contains index.html. Note: On next prompt DO NOT overwrite index.html. Also choose Yes to single page app. After firebase init runs, make sure to run ‘grunt build’ in the Terminal before running ‘firebase deploy’ in order to update the build.

Scenario 3: Google font errors, Ionicons not showing

Next up, I had errors with Google fonts as well as my Ionicons. In the Chrome dev tools you can troubleshoot this by looking in the Network tab to see what is not running. Also you can see in Console that Google fonts and Ionicons are using http and Firebase is asking for https. Why? Who knows. Answer – change http to https in your head source files. Now re-deploy.

Conclusion

More may be added to this list as I send more to Firebase. Stay tuned!