Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evolution of the donation form #1584

Open
Changaco opened this issue Sep 19, 2019 · 4 comments
Open

Evolution of the donation form #1584

Changaco opened this issue Sep 19, 2019 · 4 comments
Labels
discussion issues that are undecided or for which feedback is invited UI issues concerning the User Interface
Milestone

Comments

@Changaco
Copy link
Member

Changaco commented Sep 19, 2019

This issue is about the shortcomings of the current donation form and how it should evolve. The previous thread about this was #569.

It's unlikely that the next version will completely replace the current one, instead it should probably be possible for creators to choose which variant of donation form they want their potential patrons to see by default.

The current problems include:

We have to figure out a new design that can accommodate everyone, or multiple designs optimized for various use cases and personal preferences.

@Changaco Changaco added discussion issues that are undecided or for which feedback is invited UI issues concerning the User Interface labels Sep 19, 2019
@Changaco Changaco added this to the Donation form milestone Sep 19, 2019
@Changaco
Copy link
Member Author

One suggested alternative design is to ask the donor how much money they want to send right away, instead of asking for a periodic amount and then asking for a payment amount in a second step.

From @mattbk in #1581 (comment):

It seems like the UX could be changed to something like:

  • How much to give bob: $12
  • When would you like to be reminded to donate again: 3 months
  • This averages out to: $4 per month, $1 per week, and if you renew, $48 per year

@trebmuh
Copy link
Member

trebmuh commented Sep 20, 2019

Sounds fine to me 👍

@mattbk
Copy link
Contributor

mattbk commented Sep 20, 2019

To clarify, the last bullet would be generated on the fly based on the previous two fields.

I wasn't even thinking about how the pledge/send forms were on different pages. Glad you're here to translate for me ;-)

One thing that will be affected is this call to action:
image

The call to action is related to a weekly donation amount, which may be confusing when you can enter any amount and any period of time.

I know the next page is (right now) structured to go through all the donations, but it would be nice to have the three payment buttons on the same page as the donation form.

Last thing I can think of is how to include one-off donations when calculating a weekly amount. How many weeks should you amortize over? A year?

@Changaco
Copy link
Member Author

@mattbk

The call to action is related to a weekly donation amount, which may be confusing when you can enter any amount and any period of time.

The goal is only weekly because we don't yet allow the creator to specify another period, but the potential confusion will still exist after that's fixed.

I know the next page is (right now) structured to go through all the donations, but it would be nice to have the three payment buttons on the same page as the donation form.

By “three payment buttons” I assume you mean the payment method selection (card, direct debit, paypal).

Last thing I can think of is how to include one-off donations when calculating a weekly amount. How many weeks should you amortize over? A year?

That's one of the big problems with one-off donations. Open Collective computes an “Estimated Annual Budget”, described as “Projected annual budget based on total financial contributions from the past 12 months.”, and shortened to “Yearly Budget” in profile boxes. My guess is that they count any non-recurrent donation as an annual one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion issues that are undecided or for which feedback is invited UI issues concerning the User Interface
Development

No branches or pull requests

3 participants