4 ms·

You’re an engineer who wants to implement Apple features, yet you don’t want to spend maybe, what, $200 for a test phone? These kinds of complaints are really i

You’re an engineer who wants to implement Apple features, yet you don’t want to spend maybe, what, $200 for a test phone? These kinds of complaints are really irritating and disingenuous. My interpretation is that you’re more interested in complaining and finding problems than just buying a test phone and being done with it. It’s not that hard.

mobilemidget 7y ago
Well to be fair he wanted the app to have the same options everywhere. So regardless if he had a test iPhone, he wanted apple sign in to work on android. And probably vice versa too, google login on iPhone. Personally not a fan of either, separate email/passwords everywhere is what I prefer. But I cant say I have come across a non-apple service/site that offered apple login.
- munk-a 7y ago
  For the purposes of authentication the closest equivalent Android side is "Sign in with Google" which can be done with 0 dollars and is a pretty straightforward and well documented API call that has specific SDK support in a lot of languages and settings.
ubercow13 7y ago
My interpretation of this situation is that as an Apple user, Apple has done me a disservice by putting artificial barriers up that make it harder for third-party developers to provide me, an Apple user, good service. I don't see any reason to defend that, it seems to be only in Apple's best interest, not mine. Anyway, it's not $200 for a test phone, it's $200 just for a 2fa device. Meanwhile Yubikeys are $20 and have better battery life.
looperhacks 7y ago
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.
- capableweb 7y ago
  > 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 a key then.
  - ubercow13 7y ago
    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.
    - capableweb 7y ago
      > Apple is just gatekeeping access to their API to developers who buy one of their otherwise unrelated products I don't know how that's news for anyone, Apple has been doing this forever and they explicitly chase that goal as far as I know. If you're saying "yeah, I want to support iOS/Sign in with Apple/AirDrop/Screenshare/Any other Apple feature" then you're entering the need of having more things to do with Apple. That's the cost of joining and leaving the ecosystem they created for themselves.
      - LanceH 7y ago
        Depends on how you look at it, really. End users say, "I would like to be able to sign in with xxx." Developers say, "Your OS vendor doesn't want you to."
deleted 7y ago
[deleted]
jakobegger 7y ago
If I want to add "sign in with github" I need to read some docs, get an api key, implement the feature, done. If I want to add "sign in with apple", I need to read some docs, then read a bunch of forum posts because the docs are incomplete, then go out and buy a used iphone somewhere, and you think that is completely normal??

mobilemidget 7y ago

Well to be fair he wanted the app to have the same options everywhere. So regardless if he had a test iPhone, he wanted apple sign in to work on android. And probably vice versa too, google login on iPhone. Personally not a fan of either, separate email/passwords everywhere is what I prefer. But I cant say I have come across a non-apple service/site that offered apple login.

munk-a 7y ago
For the purposes of authentication the closest equivalent Android side is "Sign in with Google" which can be done with 0 dollars and is a pretty straightforward and well documented API call that has specific SDK support in a lot of languages and settings.

ubercow13 7y ago

My interpretation of this situation is that as an Apple user, Apple has done me a disservice by putting artificial barriers up that make it harder for third-party developers to provide me, an Apple user, good service. I don't see any reason to defend that, it seems to be only in Apple's best interest, not mine. Anyway, it's not $200 for a test phone, it's $200 just for a 2fa device. Meanwhile Yubikeys are $20 and have better battery life.

looperhacks 7y ago

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.

capableweb 7y ago
> 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 a key then.
- ubercow13 7y ago
  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.
  - capableweb 7y ago
    > Apple is just gatekeeping access to their API to developers who buy one of their otherwise unrelated products I don't know how that's news for anyone, Apple has been doing this forever and they explicitly chase that goal as far as I know. If you're saying "yeah, I want to support iOS/Sign in with Apple/AirDrop/Screenshare/Any other Apple feature" then you're entering the need of having more things to do with Apple. That's the cost of joining and leaving the ecosystem they created for themselves.
    - LanceH 7y ago
      Depends on how you look at it, really. End users say, "I would like to be able to sign in with xxx." Developers say, "Your OS vendor doesn't want you to."

deleted 7y ago

[deleted]

jakobegger 7y ago

If I want to add "sign in with github" I need to read some docs, get an api key, implement the feature, done. If I want to add "sign in with apple", I need to read some docs, then read a bunch of forum posts because the docs are incomplete, then go out and buy a used iphone somewhere, and you think that is completely normal??