Create a Next.js app with Firebase Auth, Cloud Firestore, and Tailwind

About this guide

This development guide walks you through everything you need to do to build a high-quality Next.js app integrated with Firebase Auth, Cloud Firestore, and Tailwind. Check out the tasks below to get started. To save time, you can also use our boilerplate, which gives you a complete React codebase with all of these tasks done for you. Okay, let's dive in!

Tasks

• Setup your Next.js appGet the code

  Create a Next.js app using npx create-next-app and then run your project locally with the npm run dev command.

• Create a Firebase AuthProvider and useAuth hookGet the code

  Create an AuthProvider component that fetches the current user from Firebase Auth, subscribes to changes, stores the user in state, and then makes all this data available to child components using Context.Provider. Make sure to update your Next.js App component so that AuthProvider wraps all your pages. You'll then create a useAuth hook that reads the user with useContext and returns its value. This will enable any component to call useAuthto get the current user and re-render when it changes.

• ‍Protect pages with a Firebase requireAuth HOCGet the code

  Create a requireAuth higher order component for pages that should only be viewable by authenticated users. It should call your useAuth hook internally to get the current user, show a loading indicator while waiting on the response, and then either render the page or redirect to /signin depending on whether the user is authenticated.

• ‍Merge extra user data from Cloud FirestoreGet the code

  Update the useAuth React hook to automatically fetch extra user data from the Cloud Firestore users collection and merge it into the returned user object. This makes it easy to access extra user data (think username, subscription plan, etc) without needing to manage extra queries and loading states. Make sure to return an undefined user object while the query is pending so that the user isn't considered logged in until all data is ready.

• ‍Create a custom Firebase email action handlerGet the code

  Some Firebase actions, such as password resetting and email verification, will take the user through an email flow and then have them complete the process on a page hosted by Firebase. For a better experience, you can handle this within your own app. You ll need to create a custom Firebase email action route that reads the mode and oobCode params passed by Firebase and then display the appropriate UI (such as a form for selecting a new password). Make sure to handle success/error states with and display a message to the user.

• Build your authentication UIGet the code

  Create an authentication UI using Tailwind elements and Firebase Auth functions. You'll want routes for user sign-up, sign-in, forgot password, and change password. Make sure you properly validate inputs and display any errors returned by Firebase Auth. You may also want to use a library, such as React Hook Form, for managing form state.

• Link user to analytics sessionGet the code

  You can connect Google Analytics sessions to the current authenticated user with the User ID feature. This allows you to see what your users are doing across sessions and devices. You'll need to update your useAuth hook to set the user_id property whenever the user changes.

• Create Cloud Firestore query hooksGet the code

  Create React hooks that wrap your Cloud Firestore queries, such as useUser, useItem, and useItemsByUser. These hooks should subscribe to data using onSnapshot and return a query status of "success", "loading", or "error". The React Query library makes it especially easy to setup these hooks and have components re-render when data changes.

• Add Firestore rulesGet the code

  Be sure to specify your Firestore security rules so that your Firestore database is secure. For example, if you have a users collection you might ensure that the authenticated user can only update a doc if userDoc.uid matches their uid. If you have an items collection you might ensure that they can only update and fetch items where itemDoc.owner matches their uid. You'll also generally want to specify an array of fields that are writeable, as you wouldn't want a user to be able to change userDoc.planId without actually upgrading their plan.

• Build a data-driven UIGet the code

  Create a data-driven UI using Tailwind elements that reads/writes data to Cloud Firestore. The specifics will depend on the type of app you're building, but we generally recommend having a useItemsByOwner hook that fetches "items" in Cloud Firestore that are owned by the current user. You can then create a component for displaying that data in a simple list or table if more columns are needed. Finally, you'll want create a flow for creating and updating items utilizing Tailwind modal and form components.

• Install and configure TailwindGet the code

  Install Tailwind and add a tailwind.config.js file by following the Tailwind guide for Next.js.

• Ensure Tailwind link components hook into Next.js routingGet the code

  Make all Tailwind link elements hook into Next.js routing by wrapping them with the Link component from next/link.

• Create a persistent layoutGet the code

  Add any components that you'd like displayed across all pages (such asNavbar and Footer) to your Next.js App component. If you need multiple persistent layouts you can instead have each page define its own layout. In that case, create multiple layout components (such as LandingPageLayout and AdminLayout) and wrap the contents of each page.

• ‍Finish your app UI with TailwindGet the code

  Build out the rest of your UI using Tailwind elements and composing them into high-level page sections, such as HeroSection and AccountSettings. Use theming and dynamic classes for styling your components and overriding default element styles.

Get the code

You can get the code for this guide with our Next.js, Firebase Auth, Cloud Firestore, and Tailwind Boilerplate. You'll get a complete Next.js codebase with Firebase Auth, Cloud Firestore, and Tailwind integration, all the tasks listed above done for you, and a responsive multi-page template. It should save you about two weeks of development time.

Get the boilerplate