Privacy First Federated Login
We're building a privacy focused federated login to replace existing social logins that don't allow users to protect their own data. You can imagine as a user there's lots of opportunities here. So many I think we need to focus on core features.
For you users or as a user, what feature would you like to have the most?
Trending on Indie Hackers
Would be interested to take a look in detail. Today, I use DID for my product. Many first time users definitely find it difficult as it is a learning curve. Have a privacy first login as a same as email registration flow would be interesting to see if frictionless onboarding is possible.
There are some good things to be said for DID before they decided to pivot. There also some general attention lacking when it comes to good UX. We've found the alternatives focus on "developer experience" rather than a good one for the users. I think it's critical for both pieces to be exactly what they need to be.
For instance, session continuation and email registration are just two of the common missing pieces often requiring users to relog, go through a flow multiple times, or require development teams to re-implement all the missing features.
I have been interested in this lately as well. The two features that come to mind are:
Those are two of the core features that are in the works, when we get further. I will definitely reach and so that you can try it.