Skip to content
This repository has been archived by the owner on Dec 26, 2019. It is now read-only.

RFC: MVP goals #7

Closed
jtu0 opened this issue Dec 13, 2017 · 5 comments
Closed

RFC: MVP goals #7

jtu0 opened this issue Dec 13, 2017 · 5 comments

Comments

@jtu0
Copy link
Member

jtu0 commented Dec 13, 2017

Time constraints

  • Fast turnaround to support creators who are looking for something like Nourish right now
  • Cohere hackathon runs roughly Dec 20 - Jan 3
  • Launch goal roughly Jan 4-7

MVP goal

Empower individual and communities of authors, writers, artists, streamers, technologists, etc to own and expand their sustainable revenue-generating mechanisms. They will not be beholden to a service provider whose terms may change (other than for payment processing and hosting). If they are so moved, they might give us a toast at our own Nourish party.

MVP contents

what should a creator (host? as in party host?) be able to do?
what should a subscriber (consumer? fan? attendee as in party attendee? partygoer?) be able to do?
(maybe the verb for contributing is to WHOO or CHEER or TOAST? oooh, toast! it's a party!)

Personas

Host - Creator looking for revenue
Admin - Person managing the nourish.party instance
Partygoer - Person who wants to pay for access
Content Provider - A Service, such as Wordpress or YouTube or what not.

Features

  • Host may specify a single financial tier for recurring access to their party
  • Host may setup stripe credentials to receive payments
  • Partygoer may subscribe to toast the Party Host
  • Partygoer may unsubscribe from toasting the Party Host
  • Admin may approve a Host to party on their site
  • Potential Host may request to party on the Admin's site
  • Content Provider is notified when a partygoer pays for a subscription
  • Content Provider is notified when a partygoer cancels their subscription
  • Partygoer's subscription is cancelled when payment fails
  • Nourish.Party exists as a Nourish Site
  • nourishparty.org exists as a landing page describing nourish and encouraging people to set up their own. Also has documentation, links to github, a "heroku button" for the latest production release, and a way to download the latest release as a zip.
@zspencer
Copy link
Member

The primary goal, from what my perspective at least, is to encourage individual and communities of authors, writers, artists, streamers, technologists, etc to own and expand their sustainable revenue-generating mechanisms.

There are tons of great platforms for creating and sharing creative work, but almost all of them attempt to capture as much of the value created as possible. Channels such as YouTube, Twitter, Udacity, Twitch, Tumblr, Flickr, InstaGram, Reddit, etc. tend to extract as much revenue from the content as possible via advertising while leaving as little as possible to the creators. We are seeing an uptick in "$ per unit of attention" as YouTube and Twitch fight for streaming eyeballs, but we're not seeing an increase in creator-owned streams, which seem to be the differentiator between someone making "beer money" and someone making "rent money" based upon their creative expression.

@zspencer
Copy link
Member

@jtu0 - I think we want to avoid the "Signing someone up for Stripe/Heroku" side, as most of these companies have really good onboarding processes that actually give a lot of useful information. Instead, we should make it really easy to enable stripe via the hosted app; and use a deploy to heroku button on the web site to make it easy to get set up.

@jtu0
Copy link
Member Author

jtu0 commented Dec 13, 2017

@zspencer - sounds good - do you mind updating the issue description?

@zspencer
Copy link
Member

@jtu0 I've adjusted the feature list and will start putting them into github issues.

@zspencer
Copy link
Member

I've broken these out into independent tickets and placed the rest of the issue content in the 1.0.0.rc1 milestone: https://github.com/wecohere/nourish.party/milestone/2

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants