SourceCred UI Design and Development

Agree that we want the whole UX in one place. Let’s consider the different UI pieces we want:

  • An interface for interactively diving into Cred (how much cred does this Initiative have? Where does that cred come from? Where does it flow to?)
  • An interface for exploring one’s own Cred and how it’s changed over time
  • An interface for seeing how much Grain one has and how it’s changed over time
  • An interface for boosting things (requires that the backend know how much Grain you have, and a way to commit the changes)
  • An interface for editing and creating artifacts/initiatives

I posit that many of these are basically impossible to build into Discourse. Therefore, as we build out the game, most of the key functionality will be outside of Discourse. Once that happens, since we will want the whole UX in one place, we’ll want to move the initiatives and artifacts out of Discourse and into our dedicated UI.

This will also be easier for beta users, who may not all be using Discourse.