![]() While Hunter concedes that AnyList could certainly request that users provide their actual email address when signing up, that obviously defeats most of the purpose of using Sign in with Apple in the first place. In fact, it creates an even more potentially confusing situation for users, since if you’ve signed up for AnyList with a private relay address and a friend tries to share a list with your actual email address, you’ll get an email inviting you to sign up for an entirely new account. This creates a situation where it becomes even more difficult for a developer to look up the user’s actual account when there’s a problem.įor example, if you sign up for a service with “Hide My Email” enabled, the developer will only know you as something like and although it’s possible for the user to find this on their iOS device, it requires an extra step.įurther, since AnyList is heavily focused on sharing lists with other people, the use of private relay addresses makes this very difficult, since your partner or friends may not have any idea which email address to use to share a list with you. This is exacerbated even further with Apple’s “Hide My Email” feature, which generates a special email address to hide the user’s real identity. Our reply was going to their iCloud email account, but they didn’t see it because they only ever looked at their Gmail account, in the Gmail app. So people would ask for help, we’d reply, and they’d contact us again later, angry that we never replied. When the customer raises a support issue, the only identity that the developer has for them is their Apple ID, with its associated email address, which may not be an account that the user ever thinks to check. This naturally becomes the email address that’s associated with their Sign in with Apple profile, and when a user signs up for a service like AnyList with their Apple ID, that becomes their contact information. For one, even though it’s possible to use any email address to set up an Apple ID, many users don’t realize this and create their Apple ID using an address, rather than their actual email address. However, Sign in with Apple also offers the potential for even more problems. ![]() Even simple things like password resets become far more complicated than they should be. The crux of the problem is that users often can’t remember which login system they originally used to create their account, and the developers can’t really do much for those users who get locked out of their accounts, since those problems have to be solved at the third-party provider. This isn’t a problem that’s specific to Sign in with Apple, but rather impacts every third-party authentication system, including Facebook, Google, and others. ![]() Customer Experience ProblemsĬhief among these, Hunter notes, is that all third-party login systems generally cause more user experience and customer support headaches than they solve. Such is the case with popular shopping list app AnyList, which recently published a fascinating blog post explaining exactly why they won’t be supporting the new authentication system, and they make some pretty good points.ĪnyList developer and co-founder Jeff Hunter explains that the company considered the advantages of using Sign in with Apple, but ultimately decided against it as there were more cons than pros in regard to the technology. However, it’s not without its problems, and as much as Apple is trying to promote its adoption among iOS developers, there are some valid reasons why some are reluctant to adopt it. ![]() For the most part, the Sign in with Apple feature that Apple introduced in iOS 13 last year has generally been of benefit for most users, providing a private and secure alternative to remembering more passwords or falling back on authentication through more invasive providers like Facebook.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |