Knowing that NFT's draw new users into the crypto space, it was time to modernize our NFT Manager, and fortalize it with more robust capabilities.
Take a look at the following design. Both the title and number of each NFT collection is being shown twice. Nothing terribly wrong with that, but could it be optimized? I believe so.
...
Next, take a look at how the user has to click on each collection title to view just a few NFT's. That's a lot of clicks to just view one or two NFT's in each collection. Could we optimize this? I believe so!
...
And lastly, let's explore the features of this NFT Manager. What can it do? and what can it not do?
Looks like the only feature is to Send NFT's. For an NFT Manager, could it be more robust. I think so!
...
Next, let's do a bit of research to find out if my concerns have any weight, and get some ideas on how to solve for these problems.
Click next tab
Let's test our most popular competitors
...
When testing our competitor wallets, I could see all my NFT's at once, and did not have to click on each individual collection title.
This eliminates duplicate titles and reduces the number of clicks!
...
Let's take a look at competitor features
Metamask includes the ability to "Hide" NFT's. This feature is important as more and more, users are seeing advertisements and scams being airdropped into their accounts in the form of NFT's without their knowledge.
...
Enkrypt lets users favorite their NFT, creating a separate category at the top of the page, so users with many NFT's dont have to scroll to find them.
...
More popular features are sort and filter options. By giving the user more ways to customize their wallet, it can increase ease of use and increase their satisfaction with the product.
...
NFT details
When the user clicks on an NFT, it often expands into a detailed view. Let's see what information our competitors show:
Click next tab
B User needs and company needs
B User needs and company needs
...
Next, let's brainstorm ways that we can achieve these goals by identifying possible content and features
...
Once we have outlined our goals, let's draft a rough strategy of how we will achieve them.
...
And lastly, let's explore the features of this NFT Manager. What can it do? and what can it not do?
Looks like the only feature is to Send NFT's. For an NFT Manager, could it be more robust. I think so!
Next, let's do a bit of research to find out if my concerns have any weight, and get some ideas on how to solve for these problems.
Click next tab
I first proposed updating our UI to show all the user's NFT's at once.
However, during a technical interview with the dev lead, he told me this would be very hard to do. The API pulls 20 NFT's at a time and if the user has thousands of NFT's, we would have to do multiple requests until the list was completed. This could take way too long to load, and we have to pay for each request.
They also told me that in one single request, they could pull all the NFT collection titles. So the developers proposed something different:
Pull the entire collection list in one pull, and when the user clicks on a collection, then we make all the necessary pulls until we get all the NFT's for that collection.
But this does not solve our UX problem. It was time to get back to the drawing board
...
What about lazy load?
So far I knew this: We can pull all collection titles, and NFT's would load 20 per request. So what if we request all collections in one pull, and we only do the first pull of NFT's. Then, as the user scrolls, we make the next pull, and the next, and the next etc?
In our second technical interview, the lead dev told me this would work perfectly and gave me the go, hoping that:
Lazy-loading open collections would improve UX and save the company money.
...
Click next tab
I first proposed updating our UI to show all the user's NFT's at once.
However, during a technical interview with the dev lead, he told me this would be very hard to do. The API pulls 20 NFT's at a time and if the user has thousands of NFT's, we would have to do multiple requests until the list was completed. This could take way too long to load, and we have to pay for each request.
They also told me that in one single request, they could pull all the NFT collection titles. So the developers proposed something different:
Pull the entire collection list in one pull, and when the user clicks on a collection, then we make all the necessary pulls until we get all the NFT's for that collection.
But this does not solve our UX problem. It was time to get back to the drawing board
...
What about lazy load?
So far I knew this: We can pull all collection titles, and NFT's would load 20 per request. So what if we request all collections in one pull, and we only do the first pull of NFT's. Then, as the user scrolls, we make the next pull, and the next, and the next etc?
In our second technical interview, the lead dev told me this would work perfectly and gave me the go, hoping that:
Lazy-loading open collections would improve UX and save the company money.
