ORE ID was a product spin off from AIKON's previous marketplace project, API.market, due to the continued positive reception at the seamless login solution that we had built into API.market. With many decentralized applications being built at the height of the crypto market, the problem we heard across the board from everyone we talked to, was that user adoption was one of their largest struggles with over 90% of people dropping due to the complicated and scary mechanisms required to create and maintain a blockchain account and wallet.
With ORE ID, we wanted to extend upon the learnings and simple UX that we had created with our API.market onboarding, and package that into a solution available for any other projects to utilize. For everyone in the blockchain space, mainstream adoption is one of the largest looming questions, and we were excited to be able to play a part in breaking down that barrier for the everyday user.
For ORE ID, I worked on end to end product delivery and design, including delivery of front end code, scoped out data analytics tracking, setup of support channels (Hubspot), knowledge base and configuring the onboarding lifecycle Drip email campaigns. The design work comprised of building a design system for the UI, UX prototypes to share and iterate on with the product team, and final front end code delivery working with the engineers on our internal style guidelines and React components.
Starting out, the requirements for ORE ID were fairly straight forward. We wanted to refine the end user's onboarding experience that our customers would be sending their users through, and to develop a simple developer dashboard to see the important metrics for their user growth and manage any settings as needed for their integration.
1. Provide a simple white label interface for users to finish creating their wallet
2. Use industry best practices for password/PIN input
3. Provide simple white label interface for users to enter their PIN to sign transactions
4. Create a simple developer onboarding experience allowing devs to try out ORE ID
5. Provide helpful analytics to help customers monitor their user growth
6. Provide a simple interface to edit any necessary app settings
7. Provide guidance to developers users with their app integration
8. Provide a UI or tools to help developers test their integration
The resulting layouts included two on-boarding portals. One to allow ORE ID end users to login, which also acts as the white labeled onboarding experience for users to create their new accounts for an app, and their user profile where they can see their apps and manage their wallets and user settings. The other on-boarding portal is for developers to sign up and try out the ORE ID integration for their app.
The user portal is where the user can go to see and manage their settings and wallets for all of their ORE ID apps. Still barebones in production currently, we hope that as a user starts to use more ORE ID enabled apps, that this will be the place to manage their tokens, app settings and security settings including GDPR compliant data takedowns.
The developer portal has been more of a focus at the start of this project as we first needed to get customers up and running with our integration before we would expect to see end users enter the system. Below was a simple stepped onboarding requested the basic info to create an app registration for the developer and allow them to get a dashboard and start setting up their app integration.
We considered putting larger hurdles here in the beginning like asking for credit card information to allow developers to sign up for the "Free Tier", however we felt that it's better to get a larger sample size from which to learn from as we iterated on our solution.
The developer dashboard was initially designed to help developers complete their integration with next steps and then help track the growth of their user base. The settings page also provides a way to change most of the basic settings for the app such as brand color, logo and most importantly callback URLs.
Since working with the blockchain continues to be a complex undertaking for everyone, we also launched a couple tools that help the developers test their integration, specifically one that allows devs to run OAuth for their app for any of the provided auth platforms, and to sign a test transaction.
Metrics for Success
The metrics for success for ORE ID are fairly straightforward for a Sass product.
1. # of Customers
2. # of users onboarded
3. % rate of successful user onboarded
4. % rate of returning users
We tracked these metrics in a few simple Mixpanel graphs.
The reception has been favorable for ORE ID, and we do have continued interest as everyone in the blockchain space struggles with user onboarding issues and UX. We've had a healthy growth in onboarded users as our existing customers continue to scale their operations with us supporting on the backend.
Some of the downfalls has been in launching new partners due to the fragmented nature of the blockchain space and the worries over specific chain dependencies with regards to individual Dapp development, ie. developers need to make a hard decision when committing to a blockchain to develop for and EOSIO, the EOS blockchain technology we based our ORE ID platform off of, was not always the first choice or due to certain circumstances with the main net, fell out of favor for some of our planned partnerships.
Pushing forward with our product, as we are essentially and identity provider, we see some real possibilities to providing differentiated GDPR compliance solutions suitable for large enterprises and have begun ideating and pitching those proposals to external parties.