We need to exert more pressure on apple and eu to not remove PWAs. Every signature counts, please sign and share EU has already started a preliminary investigation on this http://archive.today/2024.02.26-223134/https://www.ft.com/content/d2f7328c-5851-4f16-8f8d-93f0098b6adc

Magento, a company based in Berlin offering hosting and e-commerce platform, posted a video illustrating to their EU customers the significant impact of removing PWA support in iOS 17.4 on their services.

Source: https://twitter.com/mysk_co/status/1760585742655308077

Apple has decided to remove Progressive web apps from iOS in EU. If you have a business in the EU or serve EU users via Web App/PWA, we must hear from you in the next 48 hours!

Does anyone know if there are any plans to support signing and reproducible builds with PWAs? Voyager (https://github.com/aeharding/voyager) is now reproducibly built on F-droid, and, naturally, signed for distribution as a native app, which is awesome, but those using the PWA do not have such guarantees.

I honestly don't even know where in the web stack signing and reproducible build support for PWAs would be integrated. Browser level? w3c spec? Or just some open source project that provides tools to build and deploy a webapp in a reproducible and verifiable bundle? idk

Anyways, I guess I just feel like PWAs could benefit from signing and reproducible builds. Imagine clicking "add to homescreen" and seeing a checkbox verifying that the webapp bundle you're installing was built from a specific git SHA and signed by the developer. (This obviously might be too low level for a regular user, but I'm sure some UX sugar could make this better.)

It would also allow for secure app updates - for example, rejecting an update in case the server distributing the PWA is compromised.

What are your thoughts?

Thought I would share my experience releasing a web app to the Apple App Store using Capacitor.

They asked a bunch of questions and wanted a couple small tweaks, but the stickler was the following issue:

> Guideline 4.2 - Design - Minimum Functionality > > Your app provides a limited user experience as it is not sufficiently different from a mobile browsing experience. As such, the experience it provides is similar to the general experience of using Safari. Including iOS features such as push notifications, Core Location, and sharing do not provide a robust enough experience to be appropriate for the App Store. > > Next Steps > > To resolve this issue, please revise your app to provide a more robust user experience by including additional native iOS functionality. > > > If you cannot - or choose not to - revise your app to be in compliance with the App Store Review Guidelines, you may wish to build an HTML5 web app instead. You can distribute web apps directly on your web site; the App Store does not accept or distribute web apps. For more information about creating web apps, refer to the Configuring Web Applications section of the Safari Web Content Guide. For a description of the HTML elements and attributes you can use in Safari on iPhone, check out Safari HTML Reference: Introduction. Please see attached screenshots for details.

Luckily, I was able to address this by adding a companion watch app. ChatGPT helped a lot (I know nothing re watchOS or SwiftUI) but it went pretty smoothly and only took a couple days for a basic MVP that syncs login state with the main app (with a custom Capacitor plugin for managing state).

The Watch app is here: https://github.com/aeharding/voyager/tree/main/ios/App/VoyagerWatch%20Watch%20App

Looking back, it was quite stressful, especially before the Watch app was built.

Has anyone else released a web app to the Apple App Store? What issues did you run into, if any, and how did you address them?