Book Image

Firebase Cookbook

By : Houssem Yahiaoui
Book Image

Firebase Cookbook

By: Houssem Yahiaoui

Overview of this book

Do you feel tired just thinking or even hearing about backend technologies, authentication or the tedious task of deployment? Firebase is here to change the way you develop and make your app a first-class citizen of the cloud. This books takes a solution based approach by providing you recipes that would help you understand the features of Firebase and implement them in your existing web or mobile applications. We start-off by creating our first Firebase application and integrating its services into different platforms and environments for mobile as well as web applications. Then we deep dive into Real-time Database and Firebase Storage that allows your users to access data across various devices with realtive ease. With each chapter you will gradually create the building blocks of your application from securing your data with Firebase Rules to authenticating your users with O-Auth. Moving along we would explore modern application development techniques such as creating serverless applications with Firebase Cloud Functions or turning your traditional applications into progressive apps with Service workers. Finally you will learn how to create cross-platform mobile apps, integrate Firebase in native platforms, and learn how to monetize your mobile applications using Admob for Android and iOS.
Table of Contents (15 chapters)
14
Firebase Cloud FireStore

Implementing file serving and downloading

In the previous recipe, we discussed how we could upload files to the Storage bucket. In this part of the chapter, we're going to see how we can deliver and download our files directly from the Storage bucket.

How to do it...

Typically, we don't have a way to showcase all the files we have within our bucket. We do have files and folders in Firebase; however there's no API to showcase folders, but only to showcase files.

Bear in mind that the notion of folders doesn't have a meaning within the platform. This means that there's nothing called a folder within the API or logic--it's just a basic path reference to our files.

Thus, we need to have our own custom...