-
Notifications
You must be signed in to change notification settings - Fork 405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI Iteration #345
Comments
it's in the figma file if that helps? :) @Jakic007 |
Yes, I have realized that immediately after posting that comment so I have removed it 👍 |
Updated the UI in the Figma, feel free to have a look and let me know your thoughts or if you have any questions. :) |
Updated the figma file according to what we discussed yesterday. :) Just missing the "stats/graphs" part, but I can work on something as soon as I have some numbers to play with. Could you send me some numbers (e.g. contracts verified with time stamps (over time)) etc.? Let me know if there's anything else I am missing! |
Right now we just have the number of full matches and partial matches in different networks. So with those stats we can only have something like this: We can discuss this next time, but I think that it would be great to have regular line graph that would show the number of contracts verified per day for the last month or three months for all supported networks. |
Is there a way to comment on figma? Could you make the "drop zone" a little less wide and add the list of uploaded files below it? |
Yes you can comment by switching into comment mode in the top nav bar (click on the speech bubble) and then clicking on the element where you want to leave a comment: I created a draft for what you were suggesting, but I don't think it will look that good design wise... Or did I not understand you correctly? |
Closing with #708 🎉 |
As discussed, I thought about how we could iterate on the UI.
I think it would make sense to separate more clearly between:
I started to brainstorm alternatives in the Figma file.
To properly outline everything and make sense of where what needs to go I need a better understanding of all the possible outcomes / errors during the verification process (a bit like a flow chart). Happy to simply jump on a call to collect all possible user flows and then implement it further in case this direction makes sense.
I think in any case it would be very useful to come up with a user flow chart to have the same understanding of the process. Happy to create one as soon as I have all the knowledge. :)
View in Huly HI-250
The text was updated successfully, but these errors were encountered: