1
0 Comments

I just released my first Web3 app. Tell me what you think πŸ––πŸ½

Today I'm ready to show the world the project I've been working on.

It's far from being complete (and bug free πŸ˜…) but as many of you know, if you're proud of what you've developed, you're launching too late.

The project is called Tokenuity and is a set of tools targeted at non-technical users so they can take advantage of the blockchain and its technologies.

Being in its MVP stage, the only feature supported for now is the creation of ERC-721 smart contracts (NFTs).

The aim is to create and launch new tools every 3 months (or so).

From a business standpoint, I think that if successful, one of Tokenuity’s services will bring in most of the revenue (Pareto principle).

Adding a new service to the current offer instead of creating a completely different app will help speed up the development and validation process while potentially creating multiple streams of income.

Overwhelmed with micro decisions, I've decided to omit a few things on purpose:

1. There is no sign up or sign in page

I told myself there's absolutely no point in coding authentication logic if no one is interacting with the app or its core feature(s).
Once validated, I'll definitely add authentication to Tokenuity.

2. The welcome/home page is a landing page

Yes, you read that right. For the same reasons mentioned above, I think validating core functionality is more important than making the site look complete.

Perhaps I'm wrong but focusing on what really matters and having the end user in mind will help build the product from the inside out instead of wasting time on useless stuff.

I won't lie, bringing an app to life on your own is no easy task.
I hope the feedback I get here will be constructive.

Here's the link: https://tokenuity.com

PS: I'm building Tokenuity in public so let's connect on Twitter: @lpdahito

on April 3, 2022