Over the past year we have seen a lot of excitement around Progressive Web Applications. Browser evangelist are selling developers and business owners on their advantages and promising future. But what is the real story? What are the details to proper execution? What do engineers need to know to make their web sites into Progressive Web Applications that not only meet the minimum criteria, but meet the sales hype?
Searching the Pokedex offline is fun, what is the real experience like caching a business application? Caching application assets and data can be complex, especially for larger applications. What to cache, how long to cache and how to cache are all valid questions. Often, in an effort to just ship something, we cache nothing. When we don’t cache, we disappoint the customer and miss a key promise of progressive web applications.
In this session we will cover real details about caching reality based on real world experience in bringing Progressive Web Applications to market. This is not a session to sell the concept, but a session to highlight caching nuances you don’t see until you sit down to write the code.
Sure the Chrome engineers know the node modules, sw-precache & sw-toolbox, they developed. But what happens when you, the general developer uses them? How do you use the sw-precache and sw-toolbox modules to craft a caching strategy for your application? How do you even determine what to cache? How can you get yourself in trouble? And more importantly, how can you get out of trouble and prevent hours or days of frustration?