For example, when they get back to a previous page, you should retain the position of content or listings.īe careful about rich touch interactions – it’s quite hard to code them very well and a bad implementation can ruin your UX. Users will expect your PWA to behave like a typical app. A safe choice is to keep a small and easy to use navigation bar in your app. You must think about your own navigation. Remember that the back button is the most frequently used navigation element in the web. Without a Browser, there is no safety net for you – no address bar, no progress indicators, no SSL icon, no navigation buttons. This makes apps look good, but this also creates some risks. When a PWA is running in full-screen mode there are no Browser functionalities to help the user. See how apps show this type of information and use this approach instead. Start from familiarizing yourself with native mobile components.Īvoid web-based UI elements like footers, for example. This is why native apps will be your inspiration and your benchmark. It’s good to think about a PWA as a native app when you design it. So you should think about extending and training your frontend development team. A PWA is more like a website from a technological point of view and more like a mobile app from the user experience point of view. The most interesting challenge will be to educate your web-team about PWAs and mobile design. For many businesses there will be only one App of course. This is all about customer expectations and you should think about this before start.

For example, eCommerce, Product Magazine, Customer Care, etc.

You can split your websites into subdomains and then prepare a separate PWA for each domain. So the first question is – how many PWAs do you need, and is a one PWA development enough for you? On the other hand, there is only one Facebook website.

The worst ux apps of 2017