nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 you asked my opinion on PWAs. Allow me to answer in public ...

As a mobile app developer since the early days of Android, the biggest decision when starting a new project always was: "How can we provide our product for Android, iPhone and maybe even desktop?" The answer was one of these:

* Single Code Base using web technology: The UI will be poor and not adjusted to the respective platform. The performance will be poor as you don't get to use multiple threads.

* Single Code Base using some proprietary framework: The UI will be poor to ok. The performance will be good. You pay the framework provider forever and/or struggle when they go out of business.

* One dev team per platform: This is expensive of course.

The advances in mobile phone performance and the advent of web frameworks such as Svelte moved the dial more and more towards web technology in recent years.

You asked in the context of Apple dictating Damus modifications to not get removed from the App Store and some argue that Apple could do the same with a PWA but I would argue that the hurdle to block certain websites would be much higher than to remove certain products from their store front.

With apps being removed from App Store, users usually don't protest but with some links not working ... what would users do? Imagine links to my blog at habla.news not loading on iPhones? Imagine links to your posts on snort.social not working on iPads? How would users feel about that? I think it rings very differently than a removed app. But ultimately, if Apple really did remove access to these sites, the work that went into developing them would not go to waste. Users would know how to consume them and Apple would know they know.

For me, the browser is a dearly needed compatibility layer and PWA is just the topping that makes these browser apps even better on mobile devices. If possible, I would always opt for "PWA" or "a website".