-
Notifications
You must be signed in to change notification settings - Fork 308
reach out to content creators #737
Comments
We should go through the top user lists on YouTube and contact all of them. |
We lost this business. I'm taking this as a learning opportunity about what the market wants (this segment of it, that is). This is what the market wants: That is all about Brain Scoop and nothing about WePay. The Brain Scoop fan never has to leave that page and never has to know about WePay except briefly to know who's getting their credit card data. There are indicia of trust. We need to provide this kind of experience in order to be useful to content creators. |
The canonical instance of this of course is Stripe: |
From Chris Millard in email:
Email registration is at #89. |
If they're logged in on Gittip it should probably just give them the option to gift, shouldn't it? Otherwise maybe a two step thing: 1) Login/Signup, 2) Credit card (if one isn't linked) and gift amount. Also, does balanced let you charge with just the name, card number, CVC, and expiration? That would simplify the process if they did |
Re: Balanced: I believe they do, yes. And yes, if they're already logged in it's streamlined. |
I'm very interested in reaching out to these individuals. I feel a little shy in that they may not have a Github or Twitter account... but I'm willing to give Amanda Palmer a shot-since she does have Twitter :] Relevant: |
One of the barriers here was that our pricing was higher, because WePay competes with Balanced and we're a layer up, hence marking up. Now that Gittip is starting to receive it's own funding through Gittip, I've dropped the payment processing fees to cost (#1031), clearing the way a bit to make more sense for content creators. |
@whit537 |
There's a school of thought that says if you need a tutorial you've already failed. The product should be easy enough to use and learn without a tutorial. |
Well either that school of thought has no knowledge how low the lowest common denominator can be where technology is concerned, or we have some work to do. I am open to the possibility that both are true. But that doesn't leave me anywhere to help with this particular issue in the meantime then, I suppose. |
I guess what I mean is that the flow of giving either needs to lead from one step directly into the next until the process is complete and confirmed, or there needs to be a flow chart. (And I am not saying it can't be figured out and that we shouldn't give the user credit-- just that most people won't bother going to that kind of trouble.) |
A big part of reaching other communities is supporting other services for account linkage / login. Like, say, YouTube |
I'm closing this issue. It has served its purpose but it's not really actionable. Reticketed our own on-site flow as #1167. Community linking is ticketed elsewhere as well. |
Then they launched https://subbable.com/ (ht @nickgartmann via Twitter). |
I guess GitHub doesn't auto-link issues in README.md.
Ftr, Patreon won this one. |
Started thinking about this with Amanda Palmer, and really started thinking about this with Hank Green:
https://twitter.com/vihartvihart/status/312729706984267779
http://www.youtube.com/watch?v=IEYTFud4jBg
http://www.reddit.com/r/nerdfighters/comments/1adkeb/hanks_discussion_content_and_how_to_fund_it/
https://www.gittip.com/hankgreen/
Looks like he rolled his own:
http://nk.cm/brainscoop/
How can we go after this use case?
The text was updated successfully, but these errors were encountered: