List view
## Problem (What) Developer Experience: The overall problem account details and transaction details pages have a lot of content, and they can at times be confusing and overwhelming. ### Scope (Approach) - This milestone is scoped to the *account details page*. See audit & naming convention of the explorer [here](https://miro.com/app/board/uXjVOSGfhaA=/?moveToWidget=3458764518560203012&cot=14) - The remaining Explorer pages are to be considered out of scope. Specifically, the Transaction (Activity) Details Page will be covered in another milestone (to be created) - The design requirements can be found [here](https://www.figma.com/file/Ggv0tYCcGwGnTH1vRUJb9S/Explorer-Redesign?node-id=1044%3A5281) - A brief delivery approach document can be found https://docs.google.com/document/d/1plqraPlEESOGZESL6bn6N2JWzTY6cV-aHQZ_uAnTC0M/edit ### How did we discover this problem? Internal and external developers. To be validated in conjunction with user research. ## User Stories (What & Why) Broadly we want a functioning prototype to test our hypothesis on the new Explorer design. The following broadly covers the user groups and the goals of the project: - As a developer interacting with the near blockchain, I want to be able to view accounts, and their activity, so that I can quickly understand the account and the transactions associated with it without having to query an indexer or the chain directly. - As a near account holder, I want to be able to see balances, activity, assets, etc. of my, and other near accounts in a transparent, and logical way so that I can trust and understand accounts, and transactions on the near blockchain ## Measuring Success - (TBD) High level: - User validation via customer interviews: Time to understand, and complete a task using the explorer should decrease. -- It will be challenging to empirically measure this on aggregate, so we will revisit measurement empirically in the future.
No due date•3/4 issues closed