Payments and Credential Management:

Payment API Credential Management API

TABLE OF CONTENTS

1. Introduction to Progressive Web apps

2. Why Progressive Web Apps?

3. Objective of the Project

4. Advantages of Progressive Web App

5. Advantages of PWA over Native Apps

6. Benefits of Progressive Web App

7. Use Cases

8. The Future of PWA

9. Software Requirements

10. Reference

11. REQUIREMENTS GATHERING

12. Introduction to PWA Architectures

13. Introduction to PWA Architectures

14. Using libraries to code service workers

15. Add to Homescreen

16. Push Notifications

17. Payments and Credential Management

18. Recommended patterns for PWAs

19. CLUSTER AND OUTLINE OF PAGES

20. Code Base

21. Serve the app shell from the cache

22. Automate development tasks

23. Creating a package.json

24. Customizing the init process

25. Managing dependency versions

Payments and Credential Management

● Payment API

● Credential Management API

Ø Progressive web apps can also simplify e-commerce. Instead of filling in a form with payment and address details, the browser pops up a simple UI for choosing these then creates a secure transaction for the merchant server.

Ø The Credential Management API can securely remember the login details for a site and provide one-tap login.

Ø Both of these depend on the user being authenticated to the device, either by password or biometrics.

Building high-performance PWAs

Caching can speed up our application, but we should not depend on caching alone for speed. Users with browsers that don't support service worker, or users who are seeing our app for the first time, can suffer slow downloads if we're not careful. Caching can only improve performance on subsequent page loads.