Thinking…just thinking out loud
When building web apps, a user-first approach is a key factor that any great software engineer should consider - it’s a good-to-have skill that’s “hard” to find among so many software engineers
The digital well-being of your target users should drive your innovation - or product development to be precise; lol - this is just how I see it - no pun intended
Fast, speed
Let your target users find that web resource they look for in the shortest time as possible. It’s not about having a user spend a lot of time on your site. That’s not the Web we want.
Use techniques like:
- code splitting and lazy loading
- image optimization and compression
- minimal javaScript bundles
Integrated
User experiences on the web should feel like an integrated part of the user’s device; whether the user chooses to reach through a browser window or not, the experience should feel true to how the user interacts with the device.
Use features like:
- native web share dialog
- install prompts
- native-like navigation patterns
Reliable
The web must be reliable. Using some of the pre-cache and cache strategies available, avail resources that the user requests for even in the poorest internet connection.
Use strategies like:
- service workers for offline support
- cache-first and network-first strategies (workbox is cool here)
Engaging, users in sync
Avoid using push notifications to push away your users. Use push notifications in the right manner. Push value to your users. Push what’s necessary and promptly.
Find more resources and examples on docs.pwafire.org
Originally published on Medium