There's definitely a benefit to developers. Hoomi provides an alternative to social login as well as an easy way to get single sign-on across their suites of applications. Furthermore, developers can adopt Hoomi rather than adding their own email/password-based login mechanism and avoid having to build screens for login, signup, email/phone verification, password reset, account management, etc. Essentially, developers can treat Hoomi as their login-as-a-service provider.
>> Hoomi provides an alternative to social login as well as an easy way to get single sign-on across their suites of applications
How does "an alternative to social login" itself benefit developers? Every other benefit you've listed out is already being provided by social login providers.
Users are reluctant to use social login given the context of social login being sharing. This sharing sometimes results in accidental sharing or over sharing with the application and its users or "friends" on the providers social network.
I'm not trying to be rude, but you're conflating developers with end-users, and didn't really answer my question.
I'm curious how developers specifically benefit from integrating with Hoomi, over other social identity providers.
Developers want to convert as many users as possible into their apps. Social login turns off individuals that care about their privacy. Developers that adopt Hoomi don't have to implement an alternative to social login.
