Recent searches
Search options
Administered by:
I'm sorry to say that (again), but: Everyone would be better off if we'd just drop the BS idea of "apps" and embrace #PWA as the architecture to build products.
- Oh you want to use our platform, we're terribly sorry but it's iOS only.
- Oh you want to use feature-X on web? Sorry, but we prefer that you install our supper-crappy-app so that we have some vague vanity metrics for ourselves and on you.
- Ah feature-Y? Yeah that exists only on web.
Oh you think that you have to use [platform X], because it's polished animations, OS integrations, and advanced APIs? Welp.
Nobody. Gives. A. Crap.
People want your app to [do the thing] and be able to never open it again.
@MichalBryxi@veganism.social does pwa work the same on all browsers?
Yes it does*
*: Unless you hit some super shitty edge case on Safari or are using non-polyfilled version of an API that is not mainstream yet.
@stephan I also don't understand this argument: When you go native you literally lock yourself to one platform and version and nobody seems to care about this. Well built PWAs somehow work in some shape or form on virtually any device. So, in my mind, you are _always_ getting a better theoretical reach.
In practice, however, thanks to shit practices (mainly from Apple) you will be bashed for trying to get your PWAs to AppStore. And that's what is huge differentiator that IMO made PWAs not mainstream yet.
@MichalBryxi@veganism.social I use it for my Sharkey instance… but somehow I use safari (prefer Firefox in general). (Forgot why)