As we get closer to Season 3 Proposals deadline, Content Gateway and Mobile App projects are compiling the results of all the discussions and polls to gauge community consensus, identify priorities, manage risks and ultimately figure out where the hell are we heading to.
These results aren't just to serve our projects, but hopefully to suggest ideas for other teams and their roadmaps. Both of our upcoming proposals rely on this research, so I came to conclusion that I should post this common part here, and then refer to it further in all the future documents.
In our most recent post we asked the community what features should be introduced in the new user-facing product — Mobile App.
Since Content Gateway is a fairly technical thing that's proven to be unintuitive to most people outside the Dev Guild, we had to employ the trick where we collected opinions through the prism of mobile user experience.
In order to do this, we crowdsourced the Mobile App roadmap, letting everyone vote for the shortlisted features, telling us how urgent they feel each of them is.
After collecting the votes, we assigned a score to each of the poll options and applied a simple formula to rank all the items, placing the most wanted at the top.
This gave us a nice list of priorities to work with, but we still can't possibly get them all addressed in one season. Plus, some of the features require more coordination with other actors in the DAO than other, which makes them riskier to take on.
To manage that, we applied another metric that we called Complexity Level, which helped us pick the top items up to the maximum allowed complexity total that we treat as an acceptable workload to include in our roadmap discussions.
The items we picked are highlighted with green colour, and the possible replacement items with higher assumed risk are highlighted with yellow colour.
Finally, in order to map the user experience features to Content Gateway scope, we've built a graph of architectural dependencies where we analyzed what components should be implemented in Content Gateway in order for the front end applications to build the target features on top of.
While at it, we also figured which of the features can be ported to the website as well, so that we can make friendly suggestions for the Website project roadmap and offer our help with Content Gateway integration.
Here's the resulting diagram, where green arrows represent the relationships between expected user experience, Mobile App functionality and Content Gateway capabilities that we are able to implement with relatively low risk. The yellow arrows represent opportunities that we are still exploring, but have identified as relatively risky in terms of integration and coordination.