Front-end is not Back-end

User behaviors and habits are complicated to change. We’re still at the stage where we struggle explaining what blockchain is or what crypto assets can offer to the world.

People need to touch or do something tangible. They won’t risk using long and unreadable addresses, nor try understanding an unknown crypto vocabulary. These type of sensitive interactions should be avoided cause it makes communication difficult, as the same as non-actionable crypto-data.

In contrast, many developers are doing the same mistake by thinking that back-end dialect has to be reflected on their front-end.

With many existing blockchain and crypto products they simply show you the code view of their blockchain as their user interface without reproducing actual Internet schemes and processes.

For such reasons, front-end has to be reflected in an easy way, with an ‘average’ wording to attract people of the real world, considering a user interface the starting point: the storefront of a blockchain product or service.

Furthermore, when it will be time to build DApps leveraging blockchain technology, companies who adopt a user-centered approach will be the acclaimed ones. And for this reason, some well-established patterns need to be respected, such as:

Try to abstract technical components;

Avoid back-end dialect(s)

Avoid non-actionable data, and get rid of what’s not necessary;

Bring convenience to early adopters;

Respect current UX patterns and layouts of the ‘Internet world’;

Guide with consistency;

Reduce “dead times” when a transaction is being validated by the chain, by notifying the user (turn understandable apprehension into legitimate expectation);

Show in an obvious way actions / call-to-actions to confirm sensitive data and final steps.

Everyday users don’t want to deal with private keys, seed phrases or incomprehensive wallet addresses. It brings complexity which is not necessary.

Show in an obvious way actions / call-to-actions to confirm sensitive data and final steps

Avoid back-end dialect

Additionally, everyday users don’t want to deal with private keys, seed phrases or incomprehensive wallet addresses. It brings complexity which is not necessary and looks risky to use.