This week we started focusing some of our design efforts back to our first smart contract, Tabby Pay, which is currently live on the Mainnet.

Iterative dApp Design & Development

When we first launched Tabby Pay, one of our biggest goals was to get a fully-functional product into our users’ hands as quickly as possible, which would allow us to analyze the real-world usage, collect feedback and create a better user experience (and product) over time.

Credit: MetaLab

The biggest benefit of this approach is that it allows us to provide value immediately and iterate over time.

Andrew Wilkinson from MetaLab shared a fantastic post on this methodology, aptly titled Skateboard, Bike, Car. If you have any experience in development, you might also recognize this approach as ‘lean’ or ‘agile’ — but at the end of the day, the concept is this:

1. Release an MVP

2. Provide immediate value

3. Collect and analyze feedback

4. Continue to optimize and improve.

We really resonated with this approach to dApp development, which is why we’re aiming to build our Ethereum smart contracts in a similar fashion.

Tabby Pay UI Redesign

When it comes to Tabby Pay, one of the pieces of feedback we received was that it wasn’t 100% clear to some users what actions they were supposed to take first. Although we designed and implemented a modal system for the wallet selection, the actual payment step still wasn’t clearly articulated.

To address this, we began re-designing the Tabby Pay UI with a visual and informational hierarchy in mind. We feel like the overall layout of the app is still very functional, we just need to focus users’ attention to the correct areas to make the process of sending payments a little more straight forward.