Book Image

Offline First Web Development

By : Daniel Sauble
Book Image

Offline First Web Development

By: Daniel Sauble

Overview of this book

When building mobile apps, it’s easy to forget about the moments when your users lack a good Internet connection. Put your phone in airplane mode, open a few popular apps, and you’ll quickly see how they handle being offline. From Twitter to Pinterest to Apple Maps, some apps might handle being offline better—but very few do it well. A poor offline experience will result in frustrated users who will abandon your app, or worse, turn to your competitor’s apps Expert or novice, this book will teach you everything you need to know about designing and building a rigorous offline app experience. By putting the offline experience first, you’ll have a solid foundation to build upon, avoiding the unnecessary stress and frustration of trying to retrofit offline capabilities into your finished app. This basic principle, designing for the worst-case scenario, could save you countless hours of wasted effort.
Table of Contents (17 chapters)
Offline First Web Development
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Chapter 9. Testing and Measuring the UX

Congratulations! You've designed and written your first offline-first app. We've taken the principles of offline-first web development, seen how they apply to the realities of software development, and pushed the boundaries of today's technology. Keep in mind that the result of our efforts is a starting point and not the embodiment of everything an offline-first app can be. Where you go from here is up to you.

So, what's next? You've probed and prodded at the concepts, but now it's time to take what you've learned and apply it to your own applications where these lessons really matter. One reason why we explored the problems and design first is because technology is constantly changing, but human needs and behaviors remain relatively constant. By ordering the discussion in this way, you'll be able to separate the essence of the solution from the particulars of your software stack.

This said, I hope the technical details have been every bit as interesting...