4 ms·
This is great for personal code, but anyone who tries deploying this to a wide audience on the App Store is risking a permanent ban by Apple.
by floatingatoll 6y ago
This is great for personal code, but anyone who tries deploying this to a wide audience on the App Store is risking a permanent ban by Apple.
- mrpelz 6y agoAnyone with a wide audience on the App Store already has the means of sending notifications to users via APNS…
- deleted 6y ago[deleted]
- chrisweekly 6y agoHuh? This is for webapps / PWAs, not native iOS apps.
- ruperp 6y agoFrom the Github: "What you will need: An Apple Developer Program account". That means you can easily be banned for abusing their wallet apis, and they'll probably also take down your other apps on that account.
- floatingatoll 6y agoThanks, this puts it better.
- chrisweekly 6y agoAh, of course. Thanks for clarifying.
- markh 6y agoMy thoughts exactly. Here’s hoping their anti-PWA stance might soften with increased antitrust scrutiny.
- ykat7 6y agoApp Store Guidelines [1] wouldn't apply here since this is for web apps opened in Safari. If anything, it'd be language in the Developer License Agreement that might cover this. [1] https://developer.apple.com/app-store/review/guidelines/ https://developer.apple.com/app-store/review/guidelines/
- FireBeyond 6y agoWeb apps opened in Safari. So if I build a web app on my own dime, on my own hosting resources, signing no developer agreements with Apple whatsoever... ... there's not a remote chance that I'm subject to any of Apple's whims, and there's very little they can do about it. Add my site to a Safari exclusions list? That will and should go down like a flaming mess.
- ficklepickle 6y agoThe first requirement is: An Apple Developer Program account. Presumably for creating the "passes".