Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Progressive Web Apps with React

You're reading from   Progressive Web Apps with React Create lightning fast web apps with native power using React and Firebase

Arrow left icon
Product type Paperback
Published in Oct 2017
Publisher Packt
ISBN-13 9781788297554
Length 302 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Scott Domes Scott Domes
Author Profile Icon Scott Domes
Scott Domes
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Creating Our App Structure FREE CHAPTER 2. Getting Started with Webpack 3. Our App's Login Page 4. Easy Backend Setup With Firebase 5. Routing with React 6. Completing Our App 7. Adding a Service Worker 8. Using a Service Worker to Send Push Notifications 9. Making Our App Installable with a Manifest 10. The App Shell 11. Chunking JavaScript to Optimize Performance with Webpack 12. Ready to Cache 13. Auditing Our App 14. Conclusion and Next Steps

Pages on pages


Luckily, saner heads prevail and the head product designer (the highest ranked of the five designers now employed by the company) says that they need only three views for the prototype: the login view (done!), the main chat view, and the user profile view.

Still, we clearly need a robust and extensible way to move between different screens in our app. We need a good solid routing solution.

Traditionally, routing has been a question of which HTML/CSS/JavaScript files are served up. You hit the URL at static-site.com and get the main index.html, then go to static-site.com/resources and get the resources.html.

In this model, the server gets a request for a certain URL and returns the appropriate files.

Increasingly, however, routing is moving to the client side. In a React world, we only ever serve up our index.html and bundle.js. Our JavaScript takes in the URL from the browser and then decides what JSX to render.

Hence the term Single-Page App--our user technically only ever sits...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image