Thank you for this. I am in the process of creating my CV as a PWA, so I will use some of you points mentioned here as good practices.
Be careful. PWA is meant to enhance a device's features. It's meant to be used on daily basis, just like every other app. I personally think that PWA could be just amazing for your blog, but not for CV.
For presenting content, regular websites are best because they was meant for it.
CV is basically just a piece of paper. CVs are often printed and presented like that. What app-specific features are you planning to implement?
I am in the process of getting myself back to the web development. The last three years I am working with something completely independent from web, that I have started missing front end part. Now because of that, I thought to start simple and create my CV as PWA (because it's simple 'project'), just for representative purposes, and afterwards to convert my website/blog to a PWA.
That’s nice. But you might want to omit service worker completely because if you don’t, your content will cache and your visitors may be stuck with an outdated version of your cv.
Well thought! We'll see how it goes :)
CV, I didnt think of this use case for a PWA. What a good idea.
"Native apps doesn't allow text selection, so mobile PWAs shouldn't." I'm sorry, what?!? I saw there's other people disagreeing as well, but I think it's worth disagreeing... again. :) On top of that there are plenty of great use-cases for text selection and highlighting, especially in education oriented apps.
This... "Native apps doesn't allow text selection, so mobile PWAs shouldn't." is an overly sweeping statement, and I'd be careful with those. :)
Otherwise great article!
I'm sorry but I think that all mobile apps and PWAs SHOULD allow text selection, and I'm stating this explicitly.
Only the meaningful text should be selectable tho – there is no need to select the button text or something like that. Article text or message are the entirely different story – disallowing selection there is a bad practice.
That's true and I agree, only content should be selectable in terms of text. I thought you meant disabling it all over the place. Good to know we're on the same page! :)
Edited the article. You're right – my initial explanation is pretty unclear. Thanks again
Nice write-up, I believe disabling text selection would impact accessibility, it’s not true that all native apps disable text selection
...and that's where you start having fun overriding the contextmenu
Yes, browsers being native apps don’t. It’s an opinionated aspect, but when you select text on mobile, it forcefully scrolls to the selection, and your whole UX or animations could break.
Respectfully, which mobile browser force scrolls when you select text? On iOS for example the only time force scroll happens is when inputs are focussed. There is a strong business case for accessibility w3.org/WAI/business-case. Fluid animation is achievable with many front-end frameworks for example PopMotion Pose that wouldn't break with scrolling. If visual styling is the issue you can also style the text-highlight colour, or remove text selection for certain elements (not the whole body, or even create your own text selection or sharing interface Medium.com style
Safari on iOS.
Yes, you're right about removing selections not for the body ,but I still think that mobile user don't really need to select any text of your interface. For example, if you're building Twitter, enable text selection only for tweets.
Yes that's a nice solution, this way there's still some accessibility, it's worth mentioning that when viewing an individual post on Twitter text selection is allowed
Hello Miloslav, thanks for the sharing this article.
Greetings from Mexico.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.