Building the Minimum Viable Experience

[JimCollinson]

@andyypants

oh sweet no I had not seen this yet! Ya I think that deserves its own comment in the main section. @bones has a point if its in MvP its necessarily also part of the set of MvE features I was just looking though it and trying to pick out what were the new things being added now that MvE was the goal for Fleming and I could not spot much that would not have just been in the MvP anyways.

To quote myself from the dev update the other day:

@JimCollinson

So, there are multiple strands that run in parallel here, it’s not all sequential. But if you think of the MVP (roughly) being the infrastructure of the network, and the MVE being built on top, but encompassing the frontend and complete UX stack.

So if we just wanted MVP and no more then that would really be Maxwell (Fleming + the ability to upgrade it), but MVE is what we think is the minimum required a full launch. We’ll likely hit those requirements ahead of Maxwell, but and keep on powering through iterations and pulling in features, so we’ll have more than the minimum for launch time. But the game plan revolves around getting that MVE locked in, and then plowing on from there through the UX roadmap.