Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ideas #23

Open
xaur opened this issue Feb 14, 2017 · 0 comments
Open

Ideas #23

xaur opened this issue Feb 14, 2017 · 0 comments

Comments

@xaur
Copy link

xaur commented Feb 14, 2017

Not sure of the intended target audience of this page. If it is just for developers and tester then I guesss it's okay. If it is for wider and less technical audience, my feedback below.

My personal first impression is: complex, hard to follow what's going on, many new words. I'll try to dissect this general feeling.

  • Replace the vertical 'stack' version chart with pie chart. I find the 'stack' harder to read, but maybe it's just me.
  • 'stack' totals charts and the donut chart are too big.
  • Some axis tick labels and legend labels are white, some are gray. Why?
  • Bigger PoW chart time scale to show that something has actually changed. Late visitors will only see full 100% (all nodes upgraded) spanning the entire timeframe.
  • Another take on 'late visitors' problem: add textual timeline of what already happened (what the visitor has missed): "$time PoW v4 first seen on the network", "$time PoW v4 reached 75%" "$time PoW version locked to v4", etc.
  • PoS chart: remove the sharp drop to zero at the end of the chart. I mean, do not connect the latest data points (with highest Y) and the zero Y point.
  • PoS chart: some terms are confusing: 'votebit versions', 'SVI', what are v2 and v6? A tooltip explaining that 'someone is just playing' would be nice.
  • PoS chart: "v3 is still the current vote version. But v3 has received 44.34% of the votes in the latest static window." -- I think the latter should be "v4".
  • Add real numbers besides just the percentages. That makes the data feel more 'real'. For PoW/PoS charts it's the count of nodes. For voting charts it's the real counts of votes.
  • Step 2: Note under "Quorum" says "Danger" but it doesn't look dangerous to me. Perhaps just "Note"?
  • Step 2: it's confusing that charts show 100% abstain, even if the voting has not even started yet, and the votes are not being counted yet. Maybe hide them or gray them out.
  • Space utilization: Less scrolling to view the data. Ideally some simplified 'meta chart' or 'overal progress' at the top encompassing everything, then more detailed charts below.
  • Alternatively, consider two versions of the page: simple and advanced.
  • UI: the bright info blocks do not match overall style. Dark background perhaps?
  • Add clear statuses to each phase. Currently, PoW upgrade is FINISHED, PoS upgrade is IN PROGRESS, and voting is NOT STARTED.
  • Add labels explaining chart axis units.
  • Simulate time faster (like 10x) to see a moving log of upgrades and votes without waiting for 4 weeks (this could present incorrect dynamics to the public, so just an idea).
  • Another take on 'faster time to feel dynamics' problem -- add a playable (with Play button) animation or video that shows voting dynamics in fast forward.
  • Show realtime changes as they happen (miner upgrades, votes).
  • Show that voting for more than 1 agenda is possible.
  • davecgh made some great explanations on #hfvoting_test, I wish to see those as tooltips or side-baloon-tips on the demo page. Example:

That is the same as it is in Bitcoin. However, the difference here is that upgrading to the new version does NOT alone cause the new rules to take effect. It just means that everybody is ⁠⁠⁠capable⁠⁠⁠ of enforcing the new rules ⁠⁠⁠if⁠⁠⁠ they ultimately get voted in.

But of coruse there is a limit of how much info we can stuff into the page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant