After more than a month of development I'm releasing version 0.10 with user interface completely redesigned and front end code rewritten from the ground up. Steempunks UI is not terrible anymore! From now on, Steempunks will be using a card-based design. It took a lot of iterations to come up with a design of a metrics card. Its' goal is to provide an accurate impression of medium-term context for the given metrics and it seems to be doing okay.
New 30 day dashboard
Thirty day dashboard is a first Steempunks dashboard to go live. It's designed for Steem stakeholders who pay attention to the daily changes of Steem ecosystem metrics and have internalized the long term context. At this moment I'm unsure if an all time historical view should be implemented at the dashboard level or at the card level.
Available metrics:
- USD and BTC volume weighted average price for STEEM
- USD and BTC volume weighted average price for SBD
- Nominal SBD payouts
- Real USD payouts (sbd * sbd_price_in_usd)
- Author count (commenters not included)
- Post count
Possible points of confusion
- Sparklines x-axis starts from the minimum value, not from zero. here's why
- Last point for metrics that are time-of-day dependent (posts count) may make a misleading impression of a steep decline. On the other hand metrics like SBD price are not time-of-day dependent are accurate. Reconciling those differences is a set of tradeoffs I'm currently researching.
Changelog
- frontend was rewritten in Typescript 2.3 for less frustrating JS development and to increase speed of future development
- sparklines are great
- mobx is now used for state management
- started testing a ~95% card-based design approach
- backend code was improved to support arbitrary data refresh periods
New tech stack
- Pipelinedb (postgres based)
- Postgrest
- Typescript
- React
- Mobx
- Elixir and Erlang/OTP
- Docker
- Semantic UI
"time-of-day dependent" - could this be disabled by checkbox? Messes up the data visually pretty badly. I don't mind looking at data that's one day old.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
The problem is that you would probably mind looking at price data that's one day old, wouldn't you? I've tried removing last day for time-of-day dependent metrics and keeping it for price metrics but it's inconsistent and misleading. One way to solve this would be to create a regression model and display a prediction of today's value using time of day as a parameter.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Yes, the price data could be left as is.
It's up to you really, I'm just providing my view as an possible user. I'd like to get general feel of the stats with just quick glance and these dips are really not helping to get that experience.
Also, leaving the visual data as it is right now could be just as misleading for users.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Looking forward to it.
Followed.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Great tool to keep an eye on Steem growth!
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit