<aside>
Celatone is a smart-contract developer tools which allow users to deploy their smart contracts through intuitive user interfaces, interact with deployed contracts to query and execute the contract functions, and also able to explore the network blocks, contracts, validators, transactions, etc.
Landing Site: Home – Celatone
** Required the Cosmos-network wallet **
After the time at Terra, working on Nebula Protocol. We’ve been watching how painful our smart contract developers have to suffer due to the bad developer experience using the available software to deploy and interact with their contracts.
Instead of adapting to usability problems, we came up with this side project to tackle these problem by ourselves with the belief that these complicated works can be simplified through intuitive user interfaces.
<aside>
I involved in this project from scratch as the lead designer with the full-loop of works from user interview, contextual inquiry, create as-is journey and to-be journey, craft the app’s information architecture, wireframing, to hi-fi prototypes.
We created the fully organized design system that allow scalability and reusable in the most convenient way that even a new designer join the team can get used to it in just a week.
I frequently discussed technical feasibilities with developers and worked to align prioritized user stories with the Product Manager
I was responsible for creating tickets for developers, complete with user stories and acceptance criteria, and conducted acceptance tests to ensure that every task was thoroughly completed.
</aside>
We began by conducting comprehensive user research, which actually with our smart contract developers, to understand the pain points of individuals interacting with current available software. This included:
We’ve done the user interview and contextual inquiry to define the current user journey, which involving several apps so it is very fractured flow for users to do.
Interviews with both technical and non-technical users to identify common challenges.
“If I want to deploy my smart contracts, there are several features I need to use in the same manner for every single time. I wonder if there are any ways to get through these features without switch context between many apps and features.
“Development tool should help things to go smoothly. I found them become the things that devs need to handle instead.”
Contextual Inquiry to observe how were their daily lives would be as a smart contract developer. After several inquiries, we can define the common users journey that they will need to doing things in sequential. However, there were no such software that allow them to
Competitor Analysis to study existing solutions and identify opportunities for improvement. Through this research, we discovered that most users struggled with non-intuitive user interfaces such as less findability for each use cases, or the information is not visualized in the shape that the users can understand easily what they should do next.
Basically to deploy smart contract and check out if it works properly, they need to
<aside>
Users must download Terra Station to deploy a smart contract to the Terra network. However, the contracts section remains hidden until users discover how to enable the "Developer Mode," which is not easily found. Even the developers aware that the feature exists. Additionally, there is no mention in the documentation about how to activate this feature.
</aside>
<aside>
For the new users, they might not understand that the need to upload the file first and instantiate the stored file. UI provides only options to “Upload” or “Instantiate” which is not self-explanatory enough and does not indicate the steps.
</aside>
<aside>
See the transaction in the Terra Finder (need to open another app) and find the code ID in the event section, which require a lot of scrolling and hard to find as the user interface require users to do conjunctive-based search.
This issue has been voted the most annoying touchpoint by our users, as it unnecessarily increases interactions without any intentional resolution through design.
</aside>
<aside>
Both new and advanced users find the lack of guidance for each input field problematic, as there is insufficient information on how to fill them in correctly. Additionally, there is no validation feedback for the inputs, and the error messages provided are non-specific and unhelpful for correcting mistakes. Furthermore, required fields are not clearly marked as such, adding to the confusion.
</aside>
<aside>
After instantiating the contract, developers typically try to query information from the contract to verify its functionality. However, the UI does not guide them towards querying or other actions, resulting in users having to navigate to Terra Finder to copy the address and then paste it on the Contract page to access the “Query” button. Additionally, the query functions are not automatically retrieved, forcing users to rely on memory ("recall") rather than visual recognition ("recognize") to identify available functions.
</aside>