iOS 17.4 & EU DMA changes

Hi, Thank you for reaching out to us, and we apologize for the delayed response. We understand your concern about this article. Here’s our official response to this change:

This has only occurred in the EU; it works perfectly fine in the rest of the world.

Apple is obligated to comply with the Digital Markets Act, which necessitates changes that involve an “entirely new integration architecture” deemed impractical by Apple. As a result, Apple has adjusted the behavior of Progressive Web Apps (PWAs) for EU users. While EU users can still access Home Screen web apps, they will now do so within their browser window rather than as standalone apps, and certain functions like Push notifications may be unavailable.

This adjustment represents a minor change in behavior, nothing more. There’s a possibility that Apple will find a better way to comply with the law, or the law may offer more favorable options for PWA development within compliance. However, it’s important to note that Apple has not diverted its focus from PWAs, and the future prospects remain promising.

We will continue our development on PWA at full speed. We hope this addresses your concern. If you have any further questions or concerns, please feel free to let us know. We’re here to assist you.

Thank you.

“While EU users can still access Home Screen web apps, they will now do so within their browser window rather than as standalone apps, and certain functions like Push notifications may be unavailable.”

Does that also apply to PWAs built & published for the App store, using pwabuilder.com for example, and your Super PWA plugin? Would it be wise to wait for now before building & publishing a PWA through pwabuilder.com? What would you suggest?

Hi, thank you for reaching out to us. Regarding your concern about PWAs built and published for the App Store using pwabuilder.com or our Super PWA plugin, it’s important to note that PWAs cannot be published on the App Store, neither now nor in the past. This limitation stems from Apple’s policies established long ago. Have you ever attempted to publish a PWA on the App Store before?

I have personally NOT tried to publish a PWA on the App store before, however, according to quite a few articles it is definitely possible using pwabuilder.com.

If your web app meets a few baseline PWA requirements, you can use PWABuilder to validate, score, and package your application for stores.

• Your PWA needs to be published at a public URL.
• It must have a complete?web app manifest.
• The app has to be served with HTTPS.

Source: https://web.dev/articles/pwas-in-app-stores

Hi, you can add it on the Play Store through our plugin, but the App Store isn’t available right now. However, we are working on implementing this feature, and we have raised a ticket regarding this concern. It will be addressed in the upcoming update. We kindly request your patience in the meantime.

Here is the ticket: https://github.com/SuperPWA/Super-Progressive-Web-Apps/issues/516

Apple reverses decision to kill home screen web apps in the EU

Apple has?announced?that it’s?reversing?its previously?announced decision?to no longer support home screen web apps, also known as Progressive Web Apps (PWA), on the iPhone. As of Friday, March 1, 2024, EU users will continue to be able to install and use home screen web apps on iOS going forward.?

https://mashable.com/article/apple-reverses-decision-home-screen-web-apps-pwa-eu

Yes, we are aware of this news, and it’s a good thing for all of us. However, we are still working on the above task. Once we release a new update, we will notify you here. We appreciate your patience in the meantime.

• This reply was modified 7 months ago by SuperPWA.

Patiently waiting for that, thank you.

I’ve recently submitted my web app to both the Play store and App store and the app has now been approved by both platforms, which is very nice.

The Play store did notify me of the following:
Your highest non-compliant target API level is Android 13 (API level 33). To ensure you can continue updating your app, do the following:

• Update your app to target Android 14 (API level 34) or higher.
• Publish a new version of your app in production. Before you do this, you can test your app with internal, closed, or open tests.

What would you recommend?

Hi, thank you for sharing this. We have raised a GitHub ticket regarding this concern, and it will be addressed in the upcoming update.

Here is the ticket: https://github.com/SuperPWA/Super-Progressive-Web-Apps/issues/537

The upcoming update you referred to, is that SuperPWA 2.2.29 released on August 2nd?

Hi, yes, this concern has been addressed in our latest update, version 2.2.99. Kindly update the plugin and recheck.