Live data from Hacker News

How Popular Is “Sign in with Apple”?

daringfireball.net

141–150 of 340 posts

Re: How Popular Is “Sign in with Apple”?

#141

Earlier quoted context omitted.

Turns out it's only required if you already exclusively use FB/Google sign in (I thought it would also apply to your-app-auth+FB+G but I guess not) https://developer.apple.com/app-store/review/guidelines/#sig...

Huh, that was not my understanding, and your link goes on to state: > not required if...Your app exclusively uses your company’s own account setup and sign-in systems. So there’s no official guidance on the both/and case?

I interpret that as:

- If you only have social logins, you must implement apple sign in.

- If you only have your own login, you don't need to implement apple sign in.

- If you have both apple sign and your own login, you must implement apple sign in.

Re: How Popular Is “Sign in with Apple”?

#142
post #78

Earlier quoted context omitted.

> As an Android developer I have no reason to own either of those. Of course you do: Please implement this iOS application/feature in Android . Not being able to run an application from Xcode onto an iOS device severely hampers your career. I have to deal with so many Android developers and their output I absolutely cannot afford the luxury to not run Android apps from Android Studio. I don't think Sign In With Apple…

Anyone with a computer can get Android Studio for free in 5 minutes. You can't download a free iPhone.

The Simulator comes free with Xcode. And it's actually pretty usable in terms of performance compared to the Emulator you get with Android Studio.

Either you get a $75 iPhone SE or you have something for free with your MacBook. Anyone with a computer still wants to use a hardware Android device for any serious testing. And then there's the differences between all of the builds between the brands. I bet you want to test on a Xiaomi before you want to declare that push notifications work.

Re: How Popular Is “Sign in with Apple”?

#143

Earlier quoted context omitted.

As a application owner, I won't see the users email, instead Apple generates a unique address for each signup. That email also redirects any emails to the users email. For someone who doesn't like a lot of what Apple does, this is a really nifty feature. We just started integrating "Sign in with Apple" last week and are about to deploy it. Discovering the shielding of email addresses was a happy discovery, which I ha…

What happens when the customer contacts you for support and is using the shielded email service. You don't know the "real" email for the account, and the customer can't email you from the "shield" email. So you have limited means of verifying they are who they say they are. So how do you for disclose account information to them if you can't be sure they are the account owner?

I assume what Apple would like you to do is to build an "open a support ticket" flow into the app itself, which either asks for the customer's "contact email", or allows correspondence directly through the app. Such in-app support flows are already pretty standard for e.g. mobile carriers' apps, I've noticed.

Re: How Popular Is “Sign in with Apple”?

#144

Earlier quoted context omitted.

As a application owner, I won't see the users email, instead Apple generates a unique address for each signup. That email also redirects any emails to the users email. For someone who doesn't like a lot of what Apple does, this is a really nifty feature. We just started integrating "Sign in with Apple" last week and are about to deploy it. Discovering the shielding of email addresses was a happy discovery, which I ha…

What happens when the customer contacts you for support and is using the shielded email service. You don't know the "real" email for the account, and the customer can't email you from the "shield" email. So you have limited means of verifying they are who they say they are. So how do you for disclose account information to them if you can't be sure they are the account owner?

You send them an email to the address associated with to account with a verification code.

Re: How Popular Is “Sign in with Apple”?

#145
post #131

Earlier quoted context omitted.

Turns out it's only required if you already exclusively use FB/Google sign in (I thought it would also apply to your-app-auth+FB+G but I guess not) https://developer.apple.com/app-store/review/guidelines/#sig...

That's not true. Any social sign-up except given exceptions will require SIWA.

Where "given exceptions" are mostly limited to obvious situations, like using Twitter signin for a Twitter client.

Re: How Popular Is “Sign in with Apple”?

#146

Earlier quoted context omitted.

Why should anybody need to buy an iPhone to develop an android app? Using an API that is supposedly supported on android and shouldn't need an apple device? Btw $200 is not throwaway money for everybody.

> Why should anybody need to buy an iPhone to develop an android app? You don't, you can perfectly develop an android app without owning an iphone BUT, if you're using features from another ecosystem, let's say something like an authentication system that has requirements, you have to fulfill those requirements, otherwise skip the feature. Same goes if you want to support hardware-level U2F, you're gonna have to buy…

It's different having to buy a device to test a product you are developing for that device. Apple is just gatekeeping access to their API to developers who buy one of their otherwise unrelated products.

Re: How Popular Is “Sign in with Apple”?

#147
post #113

Earlier quoted context omitted.

What’s cool about that anonymized email address is that even if it gets leaked, only the registered service can use it to communicate with you.[1] [1] https://support.apple.com/en-au/HT210318

Does this just cement you too apple? I'm assuming if you lose your Apple address, you have lost all linked addresses?

I suppose it does. In the same way that using your gmail address to sign up for anything cements you to Google. But unless Apple or Google suddenly go out of business, I have a hard time seeing a problem with this.

Re: How Popular Is “Sign in with Apple”?

#148

Earlier quoted context omitted.

Huh, that was not my understanding, and your link goes on to state: > not required if...Your app exclusively uses your company’s own account setup and sign-in systems. So there’s no official guidance on the both/and case?

I interpret that as: - If you only have social logins, you must implement apple sign in. - If you only have your own login, you don't need to implement apple sign in. - If you have both apple sign and your own login, you must implement apple sign in.

I think you meant

> If you have both social logins and your own login, you must implement apple sign in.

which is my understanding as well! Would be nice if they explicitly handle this case as it's probably the majority.

Re: How Popular Is “Sign in with Apple”?

#149
post #97
post #78

Earlier quoted context omitted.

> As an Android developer I have no reason to own either of those. Of course you do: Please implement this iOS application/feature in Android . Not being able to run an application from Xcode onto an iOS device severely hampers your career. I have to deal with so many Android developers and their output I absolutely cannot afford the luxury to not run Android apps from Android Studio. I don't think Sign In With Apple…

This isn't really a fair comparison because any OSX user can just download and run Android studio for free, while your average Android programmer would require over a thousand dollars (to get a bottom-level Apple device with the worst specifications, or closer to two thousand+ to get competitive hardware) and then a yearly subscription to XCode at $100/year, and that's without having any actual iPhones to test on as…

Professionals in all fields have to spend money on tools. That’s business.

Re: How Popular Is “Sign in with Apple”?

#150
post #101

Earlier quoted context omitted.

> My understanding over the past decade or so has been they've used "standards" to stream, but just the standards Safari had implemented. It's just HLS, which Chrome didn't support

HLS can be rather readily supported with a JavaScript library that works just fine on Chrome. Imagine if Google would just "forget" to keep supporting H.264 on YouTube and only served VP9 unsupported in Safari and iOS.

Oh there are Chrome extensions which inject JS HLS libraries, adding support to Chrome.
Post reply on HN