MPA

Release considerations

Last saved by Pierre henri Seylan on December 5, 2015


INTRO:

The Client app has been developed since a long time and is very feature-rich, however many of those features are incomplete and present many bugs, which can quickly alter the usability and experience.

It is now important that the company releases a product, therefore it will be necessary to make big compromises and cut edges, to be able to ship a first minimum viable product (MVP), within few weeks.

It is clear that the app will contain bugs when being shipped, however it must have some functionalities that works very well.
Furthermore:

This document is meant to give an overview of the situation in order to make the best decision about which version to ship first.


1. FEATURES OVERVIEW

The app has the following main components:

Those components are related to the following functionalities:

NOTE:
The notifications are considered as a general component, and will be shipped in every cases of the V0.1


2. DIFFERENT MVP'S COMPONENTS:

This paragraph describe how the app could function with the minimum set of features, every component is meant to be able to run alone (without other functionalities)

2.1:  Open source projects:
Product allows to browse, pull and create OS projects

It turns out that the functionality that implies the least component, and stay consistent with the Soundslates platform concept is the open source projects.
The OSP functionality is contained in 2 tabs:

A MVP for this feature would include:

A little bit more advanced MVP would include:


2.2:  Personal project management:
Product allows to track and backup projects files 

This part covers one of the most advanced functionality of the app, however it already implies more components.
This functionality is essential contained in 2 tabs of the app:

MVP: 


2.3: Collaborations:
Product allows to collaborate on projects.

This already implies other functionalities in order to work, such as the project management functionalities, however collaborations are the essence of the SS platform, this means that it should be shipped as soon as possible, but it must have a certain degree of completion as well...

Furthermore, the collaborations module include many components, such as:
Basics:
Advanced:


2.4 Media library:
The media library can't be a product in itself, unless the whole concept is changed, in the current collaboration platform concept, the media library is seen as an add-on, to increase the workflow and backup user's assets.



3 CHOICE OF MVP:
 
This paragraph lists the possible combinations of features in order to ship the product asap, it combines each time the different MVP's component listed in section 2

3.1 OSP

3.2 Personal project management:

3.3 Project management and collaborations:

3.4 Project management and OSP:



4 UPDATE POLICY:

Once the first MVP has been shipped, the development will be articulated depending on the next update of the app, with 2 kinds of updates: