I was just poking around on a Shopify store on my Firefox browser and saw Apple Pay button showed up, first thought it's a front-end bug on the website but tapped on it and the widget slid up and you can legibly make the purchase!
Tried on Chrome too and it worked there too!
Tried a few other website and can confirm it works everywhere Apple Pay is offered. is it a feature? bug?
Wanna try it yourself? you can check this Stripe test page https://stripe.com/docs/stripe-js/elements/payment-request-b...
Haven't installed Beta 4 yet to see if it is still working.
As a short summary, here are some of the new EU requirements on gatekeepers such as Apple.
Gatekeepers must:
- Allow users to install apps from third-party app stores and sideload directly from the internet.
- Allow developers to offer third-party payment systems in apps and promote offers outside the gatekeeper's platforms.
- Allow developers to integrate their apps and digital services directly with those belonging to a gatekeeper. This includes making messaging, voice-calling, and video-calling services interoperable with third-party services upon request.
- Give developers access to any hardware feature, such as "near-field communication technology, secure elements and processors, authentication mechanisms, and the software used to control those technologies."
- Ensure that all apps are uninstallable and give users the ability to unsubscribe from core platform services under similar conditions to subscription.
- Give users the option to change the default voice assistant to a third-party option.
- Share data and metrics with developers and competitors, including marketing and advertising performance data.
Gatekeepers may no longer:
- Pre-install certain software applications and require users to use any important default software services such as web browsers.
- Require app developers to use certain services or frameworks, including browser engines, payment systems, and identity providers, to be listed in app stores.
- Give their own products, apps, or services preferential treatment or rank them higher than those of others.
- Reuse private data collected during a service for the purposes of another service.
- Establish unfair conditions for business users.
Here comes the Meta App Store to bypass all iOS privacy protections :(
I really like the idea of an eject button to run arbitrary code and operating systems on my pocket computer, but 99% of the time I want it to "just work." If I valued the former over the latter I would have bought an Android phone.
Here comes F-Droid to further enhance iOS with privacy respecting applications
> Here comes the Meta App Store to bypass all iOS privacy protections :(
> I really like the idea of an eject button to run arbitrary code and operating systems on my pocket computer, but 99% of the time I want it to "just work." If I valued the former over the latter I would have bought an Android phone.
> - Give developers access to any hardware feature, such as "near-field communication technology, secure elements and processors, authentication mechanisms, and the software used to control those technologies."
> Here comes the Meta App Store to bypass all iOS privacy protections :(
> I really like the idea of an eject button to run arbitrary code and operating systems on my pocket computer, but 99% of the time I want it to "just work." If I valued the former over the latter I would have bought an Android phone.
i value choice. no one is forcing you to download meta
Any provisions to allow sideloading unsigned apps?
Because if you can sideload, but it still needs to be signed by Apple, the whole thing is largely moot.
Perhaps it doesn't go as far as you'd like but it's not moot either.
Do third-party app stores have to pay fees to Apple for each purchase? Can they change the rate from the current 30%? That's what I'm wondering about.
https://www.tomsguide.com/news/malware-hits-10-million-andro...
I just wish it'd work on Firefox on my Mac. If not that, I'd love a popup that told me the page supports Apple Pay, so I can checkout with Safari instead.
[0]: https://webkit.org/blog/8182/introducing-the-payment-request...
[1]: https://developer.mozilla.org/en-US/docs/Web/API/Payment_Req...
But this would mean you could use ApplePay from the current FireFox app.
Firefox, Chrome, anything Apple will allow is just Safari in a different costume.
As a data point from an online retailer, we kept seeing a significantly high (I think it was something ridiculous like 30%) drop out at the check out payment screen for all Facebook/Instagram ad customers.
What was happening was they were clicking on ads, coming to our site, going to purchase and then when they reached payment didn’t have access to Apple Pay or there saved card details. The in app browsers have an “open in Safari” button, they were clicking that - so they could use their prefers payment method - and loosing their session and shopping cart. It was catastrophic!
We ultimate fixed the issue with a warning message to customers who are within an IAB.
IABs are bad for advertisers, they only serve to keep users within the social media app.
Anyone with the Beta, I would love to know if either Apple Pay or key chain saved cards are available now in social media IABs.
This is one of the few instances in which Android went to some lengths to provide a good UX. An IAB can transition into the real thing without even re-rendering or blinking - and it has all the user data of the main browser.
More: https://developer.chrome.com/docs/android/custom-tabs/
I want something that syncs to all my devices and supports extensions on all my devices.
TBH not allowing safari extensions to work in non-safari browsers felt almost anticompetitive, but I do recognize that there are some UI challenges to solve. Apple Pay was the other big feature I was missing out on.