-
-
Notifications
You must be signed in to change notification settings - Fork 100
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
Always display a way to pay [$60 awarded] #281
Comments
I've started working on it! I'm currently developing it as a donate button, you can already see what that looks like in the repo. When the button is pressed, it will show a popover menu, the same as used in the HumbleButton, but with an added pay button. What do you all think? |
This is a nice idea 👍...friend of mine installs apps for $0 to try out and if he likes using it he wants to donate...this would solve that scenario of pay later... A screen shot here will be great 😀 |
"Donate" isn't really the correct word though, since both elementary and the developer are not "non-profit organizations" (And donations also mean that they're tax deductible) Maybe @elementary/ux would like to comment about copy, placement and other things? :) |
We definitely want to avoid the word "donate" since like Felipe said it implies tax deduction, which buyers in AppCenter are not eligible for. We've had this bite us in the past with customers feeling swindled due to the misunderstanding |
Maybe some version of "contribution" or "financial contribution"? |
Does this default to the suggested price from the developer? i.e. if a developer thinks the app is worth 5$ the dropdown should default to 5$ and so on! |
@bigfatbird Just checked and it currently does not. It should be noted that the only "default" there is, is the custom amount input. Do you think it would be worth it to implement that? I am moving the ETA as there are current issues that still need to be discussed, and I am also quite busy. |
I don't know. Sometimes people download the app without paying just to return to pay later. It could be a good indicator what a developer expects you to pay. I don't know where AppCenter fetches the price information, this might come from the houston backend? @btkostner |
Some other issues that I didn't think of:
|
Donation is not the correct term to use here. Maybe "Pay"? Why not just keep the suggested amount button, for example "$1.00", on the app pages in the AppCenter unless they have paid? This would be a much simpler update and still allow users to pay after they have downloaded the app. The text in the button would then be the suggested amount if they haven't paid and be "Pay More" if they have paid. Allowing users to pay more if they have already paid. |
Other terms are "Compensate", "Fund" or "Reward". |
The suggested price is from the appstream data. Use this function to get it. |
"Purchase" is the word we usually use, which brings up the idea of not being asked to pay twice for the same thing (which I think is what UX wants). |
So, (talking with @cassidyjames), we want to show a purchase button in the update list if the user has not already purchased it (#306). We also want to add a "Fund" button in the footer that would always show with the similar style as all the other footer links. I think for sake of this bug, the footer link should be the thing we focus on. The update list will have to be done after #306. |
Something to consider also is what we do about the appstream donate tag. Does this override that? Do we show both? My personal feeling is we only show one and use the AppCenter (stripe) one if it’s available. |
If someone already installed an app but wants to come back to the AppCenter listing, we should let them pay the developer there.
The $60 bounty on this issue has been claimed at Bountysource.
The text was updated successfully, but these errors were encountered: