Book Image

A Blueprint for Production-Ready Web Applications

By : Dr. Philip Jones
Book Image

A Blueprint for Production-Ready Web Applications

By: Dr. Philip Jones

Overview of this book

A Blueprint for Production-Ready Web Applications will help you expand upon your coding knowledge and teach you how to create a complete web application. Unlike other guides that focus solely on a singular technology or process, this book shows you how to combine different technologies and processes as needed to meet industry standards. You’ll begin by learning how to set up your development environment, and use Quart and React to create the backend and frontend, respectively. This book then helps you get to grips with managing and validating accounts, structuring relational tables, and creating forms to manage data. As you progress through the chapters, you’ll gain a comprehensive understanding of web application development by creating a to-do app, which can be used as a base for your future projects. Finally, you’ll find out how to deploy and monitor your application, along with discovering advanced concepts such as managing database migrations and adding multifactor authentication. By the end of this web development book, you’ll be able to apply the lessons and industry best practices that you’ve learned to both your personal and work projects, allowing you to further develop your coding portfolio.
Table of Contents (13 chapters)
Part 1 Setting Up Our System
Part 2 Building a To-Do App
Part 3 Releasing a Production-Ready App

Supporting toast feedback

Toasts (called Snackbar in MUI) can be used to show feedback to the user that doesn’t relate to a direct element on the page. Good usage of a toast is showing an error message if a request to the backend fails, as shown in Figure 4.5, or showing a success message after the user changes their password, as there is no direct confirmation via the page content. A bad usage would be to report that the entered email is invalid as, in this case, the email field should show an error.

Figure 4.5: An example of a toast error

To support toasts, we need to be able to add a toast from any component in the app and have that toast displayed. Crucially, if there are multiple toasts, they should be displayed one after another so that there is never more than one toast displayed. This is another React context use case, much like the authentication context added earlier. So, let’s start by adding the following toast context to frontend...