Progressive web apps (PWAs) combine web and app features, offering a unique URL for distribution and enhancing user experience over time. They require specific technologies such as web manifests and service workers for optimal functionality and should prioritize speed, integration, and reliability. Current challenges include finding quality PWAs, compliance with store policies, and improving developer messaging and engagement with the PWA community.

2. Progressive Web Apps
Speaker Name

4. Partner
Application
Experience

5. Apps in the
Enterprise
Photo by Janson G: pixabay.com/en/spaceship-model-isolated-enterprise-2749360/

6. Progressive Web Apps

7. twitter.com/codepo8/status/954311316113690624

8. “But, what is a PWA?”,
I hear you ask.
Yeah, OK, a developer can dream…

9. A PWA is
Discoverable Installable Linkable
Network
Independent
Safe Re-engageable
Progressive Responsive App-Like Fresh

10. Asking that much is a bit
of a stretch…

11. Let’s make this simpler…
A PWA is a web-technology
based application. It mixes the
best of the web and the app
space.

12. Let’s make this simpler…
A PWA has a unique URL. This
can be used as a distribution
model. The link.

13. Let’s make this simpler…
PWAs are progressive.
They don’t work and behave
the same everywhere.

14. Let’s make this simpler…
PWAs are progressive.
They improve over time and
with the ability of the host
environment.

15. Let’s make this simpler…
If you choose to install PWAs
they behave like we expect
apps to behave. Without any
of the annoying bits…

16. Bridging the gap between
apps and web needed
good technology

17. PWAs use the
current web,
progressively
aka.ms/webcando

18. Additionally, we needed
two new technologies.

19. Web
Manifest

20. Service
Workers

21. We talk far too much
about the nuts and bolts.

22. E
Engaging
Let’s concentrate on
how our apps appear
to the user.
F
Fast
I
Integrated
R
Reliable

23. Let’s talk about things
that need work…

24. Speed

25. E
Engaging
F
Fast
I
Integrated
R
Reliable
Empty shells are fast, but not useful...
twitter.com/codepo8/status/954308397809184768

26. E
Engaging
F
Fast
I
Integrated
R
Reliable
PWAs should be faster, not slower...

27. Integration

28. E
Engaging
F
Fast
I
Integrated
R
Reliable
PWAs should play well with the OS…

29. E
Engaging
F
Fast
I
Integrated
R
Reliable
Alas, it is the web and user choice...

30. E
Engaging
F
Fast
I
Integrated
R
Reliable
We have some work to do...

31. E
Engaging
F
Fast
I
Integrated
R
Reliable
Great integrations less mentioned
aka.ms/pwa-on-win10

32. E
Engaging
F
Fast
I
Integrated
R
Reliable
Search engine integration...

33. E
Engaging
F
Fast
I
Integrated
R
Reliable
From web to app store via manifest...

34. E
Engaging
F
Fast
I
Integrated
R
Reliable
Yes, the manifest matters...

35. Reliability

36. E
Engaging
F
Fast
I
Integrated
R
Reliable
Embracing the web shareability...

37. E
Engaging
F
Fast
I
Integrated
R
Reliable
Avoiding known annoyances

38. E
Engaging
F
Fast
I
Integrated
R
Reliable
Availability in the worst scenarios...

39. E
Engaging
F
Fast
I
Integrated
R
Reliable
Let’s be mindful of Service Workers…
homebrewery.naturalcrit.com/share/SyZ4Sxms5b

40. Engagement

41. E
Engaging
F
Fast
I
Integrated
R
Reliable
Engaging, not annoying…

42. E
Engaging
F
Fast
I
Integrated
R
Reliable
Not all re-use is advisable...

43. E
Engaging
F
Fast
I
Integrated
R
Reliable
Going too basic isn‘t helping either...

44. E
Engaging
F
Fast
I
Integrated
R
Reliable
Let’s build progressive interfaces…

45. E
Engaging
F
Fast
I
Integrated
R
Reliable
Same app, different environment…

46. This isn’t new - our web
best practices apply…
E
Engaging
F
Fast
I
Integrated
R
Reliable

47. PWA tooling is great!
(as always, it is tough to build tools for an open stack)

48. ServiceWorker
Cookbook
(Mozilla)
aka.ms/serviceworkers

49. Workbox
(Google)
aka.ms/workbox

50. Lighthouse
(Google)
aka.ms/google-lighthouse

51. Sonar
(Microsoft)
aka.ms/sonartool

52. Not everybody
cares about the nuts
and bolts…
twitter.com/headjs_ru/status/955333399564161024

53. PWA Builder
(Microsoft)
aka.ms/pwa-builder

54. PWA Builder
(Microsoft)
aka.ms/pwa-builder

55. Why is it hard to
find great examples?

56. Why indeed?

57. developer.apple.com/library/content/releasenotes/General/WhatsNewInSafari/Articles/Safari_11_1.html

58. Our PWA messaging is
at times awful and
short-sighted
E
Engaging
F
Fast
I
Integrated
R
Reliable

59. Moaning travels
upwards and takes a
long time to arrive.
Photo by Janson G: pixabay.com/en/spaceship-model-isolated-enterprise-2749360/

60. It is tough to find
PWAs on FIRE
(that aren’t demos)

61. PWA Stats
(Cloud Four)
aka.ms/pwa-stats

62. ▪ Web App Manifests should suggest quality:
we found 1.5 million manifests across 800k
domains. Most are not ready. We will be
looking for non-boilerplate manifests that
include a name, description, and at least
one icon that is larger than 512px square.
▪ Sites should be secure (“HTTPS”)
▪ Service Workers should be an
enhancement: we expect experiences to
degrade gracefully if Service Worker is
unsupported.
▪ Sites should consider automated testing for
quality.
▪ PWAs must be compliant with Microsoft
Store policies:
PWA need to be
high quality
aka.ms/pwa-on-win10

63. Please help the PWA effort

64. Don’t assume your
experience is normal
E
Engaging
F
Fast
I
Integrated
R
Reliable

65. Give feedback and take
part in tools and docs
E
Engaging
F
Fast
I
Integrated
R
Reliable

66. Keep up-to-date before
telling people about PWAs.
E
Engaging
F
Fast
I
Integrated
R
Reliable

67. Promote and celebrate
great examples.
E
Engaging
F
Fast
I
Integrated
R
Reliable

68. I try to stop people to
package awful websites
into containers - again.

69. Please, help!

70. Thank you!
Thank you!
Chris Heilmann
@codepo8