tezblock Weekly Update #1
We will start to communicate weekly updates for the current state and progress of the tezblock MVP development. Our goal is to include the community as much as possible along the way.
We’ve set an aggressive timeline to release a Minimum Viable Product of tezblock in order to get an initial version into the hand of users as soon as possible. This version will create the foundation for the block explorer and will be at first quite bare bone, focused on essential features.
The Tezos Block Explorer Survey
To get some insights in how block explorers are used we’ve created a survey and shared it with the Tezos community. If you haven’t participated yet, please find a few minutes to complete it. On this note a big thank you to everyone who participated.
We’ve had a great response with 72 submissions so far at the time of writing out of which 35 participants signaled availability for a 15 minute user test and feedback call.
A Summary Of The Survey:
The detailed anonymized results will be published shortly.
How are you involved with Tezos?
A lot of the people completing the survey are interested in the technology aspect of Tezos and are involved with either building or validation of the protocol.
Which block explorer are you currently using the most?
The Tezos block explorer tzscan.io is definitely taking the crown here and is currently the established standard in the Tezos ecosystem.
Overall, how would you categorize the block explorer that you’re using.
A large portion of this question can be attributed to tzscan due to the outcome of the previous question. It is quite apparent that the data provided by tzscan is top notch but could be optimized in terms of usability and design.
How would you rate the importance of the following features.
In terms of different features we can see the tendency of importance in general lies with the primary protocol data and baking related stats.
Because the “Mobile Application” question had quite mixed responses, we wanted to clarify this with a Twitter poll as the question might have been misinterpreted.
What would be your preferred way to use a block explorer on a mobile device?
As we see in these result the tendency is now towards a website based solution instead of a native application. It’s still not entirely clear if users would want to have a mobile application they have to install.
The participants also came forward with numerous suggestions and feature requests which we’ll examine closely.
Done, Ongoing And Upcoming Tasks
We’re currently working in parallel on the requirements engineering from a technical, usability and design perspective for the protocol indexer and the frontend.
Usability & Design
- Tezos Block Explorer survey
- Mockups for the user tests, improvements and additions
- We’ll reach out shortly to schedule an initial set of user feedback calls, please note that due to the great response we won’t be able to get in touch with everyone.
Protocol indexer
- Requirements engineering and evaluation of Conseil, Kiln and Tezos lib-indexer. A detailed write-up will be published in the next update.
- Local setup of protocol indexer
Frontend
- Requirements engineering and evaluation of tech stack
- Proof of concepts in terms of page loading speed
- Initial setup and connections to APIs
