7 ms·
> Furthermore, if there are platforms where AnyList doesn’t support Sign in with Apple, like Android, and someone wants to log into their account, they’d have t
by WorldMaker 6y ago
> Furthermore, if there are platforms where AnyList doesn’t support Sign in with Apple, like Android, and someone wants to log into their account, they’d have to know their privaterelay.appleid.com email address. (And that certainly won’t be easy to find if you no longer have an iOS device.) And then they’d have to create a password with us, since they wouldn’t be able to sign in using Sign in with Apple.
The easy answer is: they should just support "Sign in with Apple" on every platform. (That absolutely works. Sign in with Apple is a [mostly] standard OpenID Connect provider and has a web frontend that should work on every non-Apple platform just fine, just like FB/Google/etc.)
You wouldn't think to only support "Sign in with Google" only on Android devices? Maybe "Sign in with Facebook" should only apply to web browsers?
It's an interesting misconception or miscommunication that so many developers think "Sign in with Apple" should only show up on Apple devices.
- tech-historian 6y agoSure, except there is no documentation for it. From the article: "For example, Apple vaguely states that you can implement Sign in with Apple on Android, but there is no direct documentation on how to do it. We understand that Apple probably doesn’t care much for Android, but if they are going to provide a login system, and are going to force developers of multi-platform apps to adopt it, then providing no real support for a major platform that these multi-platform apps run on is not acceptable."
- WorldMaker 6y agoApple has provided documentation, it seems like the article describes a lack of attempt at trying? On the Getting Started [1] page it lists three options: Apple platforms [use AuthenticationServices], Unity [use the asset from the Unity Asset Store], and "Web and Other Platforms" [use Apple JS/REST]. That "Web and Other Platforms" link provides a wealth of useful documentation [2]. Tbf, the exact word "Android" is missing, but this is an elementary school-level process of elimination that maybe Android is inferred in the words "other platforms". [1] https://developer.apple.com/sign-in-with-apple/get-started/ https://developer.apple.com/sign-in-with-apple/get-started/ [2] https://developer.apple.com/documentation/sign_in_with_apple/sign_in_with_apple_js https://developer.apple.com/documentation/sign_in_with_apple...
- lstamour 6y agohttps://developer.apple.com/documentation/sign_in_with_apple/sign_in_with_apple_js/incorporating_sign_in_with_apple_into_other_platforms https://developer.apple.com/documentation/sign_in_with_apple... is more “direct” than most of the documentation I’ve seen on how to implement “OAuth” with other providers. (Trying to figure out how to integrate with “Microsoft 365” is particularly painful...) Eventually you might realize it’s based on an open standard https://openid.net/2019/09/30/apple-successfully-implements-openid-connect-with-sign-in-with-apple/ https://openid.net/2019/09/30/apple-successfully-implements-... and that it’s relatively similar to other such standards, except with the option to mask your email, etc. As an geeky end user, the only way I trust these services for login is if I can link more than one, or even more than one email from the same provider. That way I know I’ll have a backup in case I lose access to the social network or email address that I signed in with... it’s annoying when I can’t add a password or set an email just because I also want to login without a password sometimes...
- ummonk 6y agoWow you're not kidding that's actually surprisingly clear documentation and it should be very easy to implement.
- draven 6y agoIt was way worse when I had to implement it a few months back. It's still incomplete, their implementation deviates from the standard or use some lesser used mechanism like the form_post response_type, requiring custom code. Implementing this was not a pleasant experience.
- on_and_off 6y agoAlso, even if they support it, it does not look like Apple has released an app or SDK for Android. So there would be no apple account registered on the phone. So each app wanting to implement apple login would have to : - pretty much implement it from scratch - still have a very subpar experience compared to any other login mechanism (even way worse than email + password) since they would have to ask users to find their obfuscated apple email address.
- WorldMaker 6y agoSign in with Apple asks for your normal iCloud email address. It's Apple's servers that look up your app-specific obfuscated relay email address if you've used one for the app.
- on_and_off 6y agoduh ! I blame my sleepiness for missing that. Still pretty meh that it is the only solution of its kind without an sdk
- tatersolid 6y agoThey don’t need an SDK if they’re using protocol-compliant OpenID Connect. Any OpenID Connect (or OAUTH2) library of the devs choice is the SDK. The Facebook/google SDKs are simply there to add trackers and bloat.
- on_and_off 6y agoA good sdk means that it is both quick to implement and that it can integrate with the OS account feature (meaning users only have to authentify once for their apple account)
- Karupan 6y agoThat’s what I was thinking as well. Why not just treat it like any other OpenID provider and show it for all platforms?
- stevepike 6y agoHeck, I've been happily using "Sign in with Apple" on linux anywhere I can.
- dahfizz 6y agoThey directly address this point. In the article they say they considered adding sign in with Apple everywhere. Besides the fact that it's more code to write and test, they say the documentation is very poor for other platforms, as it's not even great for iOS.
- WorldMaker 6y agoIt seems sufficient to me? https://developer.apple.com/documentation/sign_in_with_apple/sign_in_with_apple_js https://developer.apple.com/documentation/sign_in_with_apple...
- dahfizz 6y agoAbsolutely not. Compare the native ios documentation[1] with their "other platforms" documentation[2]. Their native documentation has code snippets, helpful links, and explains in depth what is happening. The "other platforms" documentation is "make this request, store some data, follow redirects". No code, no helpful links on how you might accomplish these things, nothing. You get the bare minimum. I'm not saying its impossible, and neither is the article. I'm saying that Apple clearly doesn't care about supporting a platform as huge as Android, and that clearly signals to multi-platform developers that they are on their own. [1] https://developer.apple.com/documentation/authenticationservices/implementing_user_authentication_with_sign_in_with_apple https://developer.apple.com/documentation/authenticationserv... [2] https://developer.apple.com/documentation/sign_in_with_apple/sign_in_with_apple_js/incorporating_sign_in_with_apple_into_other_platforms https://developer.apple.com/documentation/sign_in_with_apple...
- pwinnski 6y agoThe nature of "other" platforms means that example code could be in any language at all. The fact that their iOS documentation is so much better than average doesn't mean their "other platforms" documentation is inadequate. It just means there's plenty of room for third parties like indie bloggers to documentation their own approaches in JavaScript, Python, Ruby, Rust, or whatever.
- l3s2d 6y agoI agree in principal, but in practice this isn't as easy as one would hope. Each IdP has slightly different requirements and parameters for connecting clients. There may be significant code non-overlap across providers, not to mention across platforms. Facebook, for instance, doesn't actually implement OpenID Connect, but has a custom layer on top of OAuth. Their recommended method of connecting is a client SDK for each platform.