The Minimum Viable Experience (MVE) is what we are working on first, so we can have all the basic components of a fully functioning and usable Network ready to go prior to launch, and then iterate and improve, from there. It’s the first set of features we’re designing and building, before we rattle on through the rest of the UX Roadmap.
As I mentioned in last week’s Dev Update, we’ve been working toward an MVE, prioritising, designing and developing the essentials first, lining up the stretch goals, and working through which features don’t quite qualify.
So here it is, detail of all the features that we feel should comprise the MVE, and how we’re prioritising them, in a live Figma File:
The features are grouped in to some seeming fairly arbitrary categories, but really they are just a useful way for us to consolidate feature sets when putting prototypes together.
What you’ll see here is also work that has been completed from a Design standpoint, what is underway, and what has been conceptualised, but not been through the design process yet.
There are also corresponding boards for Frontend code, APIs and Safe Client Libs, and also the Backend code required to enable these things. I’m afraid I didn’t manage to assemble those boards in time to publish them today, but I’ll add them in due course.
I hope it helps paint a picture of what you can expect, and how we are choosing to order and prioritise development.
Fire in with any questions, and please do let us know your thoughts… we’d expect nothing less!