![](http://i.imgur.com/XuH6oX7.jpg)
After more than a month of development I'm releasing [version 0.10](http://steempunks.com) 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](http://steempunks.com)

![](http://i.imgur.com/AkYIMUj.png)

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](http://callingbullshit.org/tools/tools_misleading_axes.html)
* 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](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-3.html) for less frustrating JS development and to increase speed of future development
* [sparklines](http://github.com/borisyankov/react-sparklines) are great
* [mobx](https://github.com/mobxjs/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

<center>(∩^o^)━炎炎炎炎炎</center>