-
Notifications
You must be signed in to change notification settings - Fork 56
Explorer Design Explorations/Brief #660
Comments
I am amazed by the grounding work that has been done! 🚀 Here are my answers to the questions:
I have never thought in that direction. To me, those are two different services (like Gmail [personal] vs Google Search [public and read-only])
We have not started using them yet, but we track the usage and we can extract some patterns
Not yet
They are mostly about bringing new features, but they are not backed by metrics.
I don't believe so. However, it is currently one of the only tools that provide a sense of the fact that something is happening. It is like in the early days of the Internet, we needed those indicators that the connections are fine, but these days only tech people care about the connectivity and traffic questions.
Can you elaborate more on this? My take on building applications is that they should be self-descriptive, so any user can learn the thing through interaction with it (so far I cannot say we greatly succeeded with that in Explorer, but the small doc pages next to almost every term on every page at least provides some link up to the topics)
N/A
Search and navigation through history are the core features that we definitely need to focus on.
That might be useful, indeed
It started as a low-level view of the data, and it should also provide more high-level views (NFT, FT, and other application-level flows could be better represented on Explorer)
We definitely have some hierarchy of the data flowing in the NEAR Protocol (blocks comprise chunks, chunks are containers for transactions and receipts, and transactions/receipts get executed to apply some changes to the data and produce outcomes)
At the moment, I cannot think of any but the search history
What do you mean by "socialize"? People do share links to individual transactions and accounts these days
Maybe some of the accounts can be personally pinned, but users can use browser feature to keep bookmarks, I believe.
I will need to think more about personalization. I would not say it is a core feature for Explorer. ... (I will answer the rest of the questions tomorrow) |
(I assume you refer to delegation. It is unfortunate clash of NEAR Protocol staking with the process that Wallet calls "staking", which in fact is delegation of tokens to the staking pools / validators) Explorer is not the right tool to perform staking itself, but it can definitely educate people about the process (why it matters and how it works, and present the current state)
This term is also overloaded. Validator [1] is a person that operates nearcore node ( Validation process is the process of producing new blocks in the network according to NEAR Protocol specification.
I am not familiar with that.
I am not familiar with that.
I find it is quite interesting and catchy, but I cannot tell what problem that would actually solve.
I don't think it makes sense at this stage.
Explorer is too low-level to make the judgement on whether it makes sense to notify about certain transactions. Wallet might be a more appropriate place for balance change notification. Also, it could be a completely separate service (e.g. Telegram bot, e.g. learn more about tipbot).
Yes, I believe so.
Ideally, we want to support all the standards right in Explorer. We explore the ways to bring NFT and FT support to Explorer.
I am not sure what you refer to, but if you mean if we can search by substring of a transaction hash, then yes we can, though I feel like first characters are easier to lookup (as a human) or at least that is what
We can!
Given that Explorer represents tons of data, I believe we need accents and visual identificators for users. Currently, I fear that some users might be lost unable to get the primary information and filter out secondary details. Navigation through the history with filters is where we can improve significantly.
I am not sure if this is even a question. The process is quite involved, but Wallet had simplified the technical side of it, though it does not give any context as to why that thing even exists. The original and still referenced low-level documentation is available here (see "How to Use and Earn Rewards with the NEAR Token" section on the https://near.org/tokens/). There are also some third-party takes on it: |
@reefoh Let's go ahead and break the components of the brief out into the focused issues we went over yesterday just so we can track the different output more easily and have discussions that are scoped a bit tighter |
@frol Love the feedback and enthusiasm! I'm formally organizing things with Corwin's guidance and will nudge you when its complete. Look forward to collaborating man! |
I'm not sure is it the right place for it but I should leave this task here #817. The point is we have some issue with some transactions which is not so easy to resolve but that issue will outdated after new design |
Brief
Explorer Brief v1.pdf
Highlights
Categorized Search Suggestions
Surface useful data corresponding to results
Categorize Transactions for easier legibility
Personalize Landing
More to come!
The text was updated successfully, but these errors were encountered: