EU is the “important customer”, the users of PWA are “other customers”.

Using your example, you would implement tracking for that important customer (and comply 100% to the requirements as Apple did) but because of this additional bloat, the website would load 2 times slower.

After a discussion with your colleagues, you would realize that:

- Most users won’t care about the slow loading (including the important customer)

- Re-architecturing the website to keep the same level of performance while adding the necessary tracking required by the important customer would delay shipping the tracking by 1 year, past the 2 months deadline required by the important customer.

Back to your desk, you start implementing the tracking that will incur a 2x slower load time.

I'd love to one day work for a place where I can dismiss monetization as "the other customer". But alas, my career hasn't been that friendly.

>Using your example, you would implement tracking for that important customer (and comply 100% to the requirements as Apple did) but because of this additional bloat, the website would load 2 times slower.

Given how the topic is:

>Following developer complaints and press reports about how PWAs were no longer functional in the EU after installing the most recent iOS betas

I fail to see how the EU is the "important customer" here. And not the powers that be in Apple telling me to maliciously comply.

The EU said "allow other app stores to exist" and my theoretical manager at Apple is saying "okay, PWAs can exist but they don't have to run well. Add in unnecessary security (because the NA version doesn't have it) that disables functionality". I don't even see how it has to do with complying with the EU, unless it's soke long term OS lock down for future app stores.

Tell me how the EU here is the one telling me to slow down my OS/browser?