3 ms·
In general, these might not be the best solutions - they are just the ones I found. I am always happy to learn and want to keep that post as a living list of fi
by rhazn 2y ago
In general, these might not be the best solutions - they are just the ones I found. I am always happy to learn and want to keep that post as a living list of fixed for myself in the future (so if anyone knows a better way, please let me know!). I am also not a native iOS user, so I might miss adherence to the iOS UX standards.
The reason for 1 was actually my mother who tried the PW, had her phone set to a different language and always triggered the translation overlay ;).
- maxbond 2y agoIt's not really that the solutions are bad but that a lot of these "problems" are fundamental parts of the UI, and shouldn't be taken away without a compelling reason. You may well have compelling reasons, I assume each of these is a response to an issue you encountered. But since the article doesn't present them, it leaves the audience scratching their heads and comes off as needlessly disempowering your users. These definitely aren't things you should be doing by default in every PWA, as "checklist" would imply. If I installed a PWA and I couldn't pull to refresh or select text, I would probably uninstall it. The points you made about specific issues were good though, like notches, favicons, and mimetypes.
- rhazn 2y agoThat's fair, the thought behind the checklist name was more for me to go through to double check if I need these... And only apply them if I feel it makes sense. But that's obviously lost if you read the list as not-me. I'll take that feedback with me for future note-to-self style blogs :).