DApp customers today want more than a great product. They expect a frictionless experience, and preferably a delightful, shareable one. But with new platform-based “experience providers” taking an increasing share of blockchain transactions, how can a DApp browser brand stand out?

In this paper, we examine what DApp browser brands must do to compete against disruptive delivery, subscription, and other platforms.

DApp browsers are at a crossroads, facing an existential challenge. The browsing experience has evolved, and so have the experiences that people are looking for. First wave browsers risk being surpassed by new, platform-based “experience providers” seeking to own the category experience, often redefining it in terms of functional convenience and utility. The question is: will DApp browsers reinvent themselves as “experience brands” in a way that allows them to continue to own and, indeed, enhance the customer experience? Or will they become mere commoditized product providers in the service of organizations that do? Let’s take a detailed look at Status UX architecture and see if there is space for improvement.

Status network is strategically positioned to lay a foundational framework for mass adoption of Ethereum and is often referred to as Ethereum’s mobile OS. It is an open source messaging platform and mobile interface to interact with decentralized applications that run on the Ethereum Network.

Achieving Status mission ultimately requires one thing: widespread end-user adoption. Status Network Token is used to design mechanisms for growth that have been tried and tested in Web 2.0, whilst providing greater transparency and better alignment of incentives for participants.

By default Status is free to use and communicate with. Users are identified by a SECP256k1 public key. Since the Ethereum Foundation’s Ethereum Name Service is specifically designed to map string to DApps and addresses, it is a natural fit for Whisper-based identities. A username- to-SECP256k1 public key resolver is created on ENS that allows stakeholders to register usernames on a first-in, first-out basis, with a social recovery mechanism. This gives stakeholders a human- readable and recoverable access point should phone or private keys be lost.

Rather than delegating other addresses to recover, the recovery process is abstracted by allowing the stakeholder to create 5 signed messages, that can then be shared out-of- band with friends or stored in a safe location. A default of 3 of 5 signed messages will be required to change the username owner, but can be optionally changed by the stakeholder.

An account must be holding The Status Network Token in order to reserve a username. This username is used to identify themselves within the greater Status community, and signal participation in the network. Should a stakeholder wish to leave the network they can withdraw their tokens and the username will be unreserved and claimable by any other stakeholder.

This system will then depend on uPort for KYC/AML requirements where required, as a completely optional step, for users who wish to interact with regulated financial tools and DApps within the application.

Stakeholder A, a casual user, wishes to register the username @david inside of Status so his friends can easily find him, and more easily recover his account should he lose his mobile device.

Stakeholder B, a DApp developer, mandates only registered Status users to post on his discussion board DApp, in order to mitigate sock puppet accounts using his decentralized application and increase the quality of content.