User must be able to sign up, sign in, sign out and recover password in a secure manner. This feature also includes send confirmation emails upon registration and password recovery. Maybe using "Mandrill" will make this easier. Registration will be disabled for the private beta. (Using some sort of Social Auth is up to discussion)
Through Oauth, user must be able to easily give permissions to Prudio so it can manage one account with access his slack team.
User must be able to create, inspect, update and delete widgets.
##Administration Backend must provide a small administration to Prudio staff, so they can manage existing users and accounts (more features and utilities can be added later).
The chat app must be able to provide all the assets needed to add the widgets to the websites of Prudio users.
The chat-app must handle the widgets and make the bridge between the JS client (widget) and slack. (almost done, contents in prudio-chat repo)
The chat app must be able to validate the widget and the domain with the database in order to assure it is running the correct website and acquire the information it needs to connect to slack.
##Static Pages Backend should be able to serve static pages (or dynamic ones) that will constitute the basis of the Prudio website. Some of those pages might be: landing page, pricing, about, features, contacts, documentation.
A blog should be made available in order to communicate with the users and to publish relevant announcements. (Ghost?)
Prudio website should have a demo widget running. Users this way will be able to try it or get support from the team.
The documentation should be searchble and organized. Probably in a subdomain (docs.prud.io).
This should be enough for the first iteration and to allow some users test it and provide some feedback. I left for future iterations the following feature:
- Allow for users to subscribe (and remove the subscription) to plans
- Implement limits in the number of widgets based on the selected plan
- Integrate with a payment system / gateway (Stripe?)
- Allow user to manage billing information and access payment history
I'm not sure the availability of the team and what other people might join to work in the bounties but this dates seem to be feasible (based on the above information and 6 weeks release cycles):
- Private Beta: 26/01/2015 (Taking into account we have Christmas and some holidays in between)
- Be able to accept payments : 02/03/2015
Note: The dates above were added when this document was first written.
I just covered the core of what i think should be the MVP and what i think we should focus first. Feel free to suggest modifications and other stuff that i might have missed.
I didn't got into technical details since it should be discussed in each bounty.