Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

Improve navigation to payment methods #3906

Closed
rohitpaulk opened this issue Jan 24, 2016 · 9 comments
Closed

Improve navigation to payment methods #3906

rohitpaulk opened this issue Jan 24, 2016 · 9 comments

Comments

@rohitpaulk
Copy link
Contributor

We seem to be leaking the exchange_routes terminology into our UI

screen shot 2016-01-24 at 4 11 52 pm

It isn't obvious what the Routes tab will lead to. I think we should term this as Payment Routes/Payment Methods in the UI.

screen shot 2016-01-24 at 4 12 52 pm

For the tab though, we could use just 'Payments'

screen shot 2016-01-24 at 4 13 24 pm

##

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@techtonik
Copy link
Contributor

I think that it is good that we're leaking it. =) It provides transparency to people on how the funding actually works.

Sticking to Payment narrows Gratipay to being just accounting system. With Gratipay 1.0 Routing concept meant that people can reroute the donations to other people, and now they will be able to get transparent view on how money are moving, and how routes are setup and track fees on the way.

Yes, the UI is not there yet, because Gratipay 1.0 is shut, but I think that Routing is still more useful menu item than Payments. It you want to de-clutter interface, I would move Emails into Settings, renamed History into Balance (I believe @Changaco did that already) and moved that balance out of Settings.

@Changaco
Copy link
Contributor

(I guess @techtonik is talking about liberapay/liberapay.com#67, but it's only tangentially related to this ticket. Liberapay has a Money I/O label for issues related to routes, but we don't have a Routes page, we have a Payin and a Payout page instead.)

@techtonik
Copy link
Contributor

Yes, but this ticket is labelled improve navigation, so it is related to user experience when they need to find a way to what:

  1. "add money to their account"
  2. "need to pay"
  3. "need to setup the source of payment"

@rohitpaulk
Copy link
Contributor Author

but this ticket is labelled improve navigation

Exactly, @techtonik. As a first-time user who isn't familiar with Gratipay terminology, would you expect the Routes tab to lead to any of the 3 options you mentioned above?

@aandis
Copy link
Contributor

aandis commented Jan 24, 2016

When I was working with #3887, it took me a while to understand that Routes actually means Payment Routes. If Payments doesn't exactly describe it, I think Payment Routes is a better option than just Routes. It at least makes it clear that it has something to do with payments.

@aandis
Copy link
Contributor

aandis commented Jan 24, 2016

That is the reason that I added Payment Routes instead of Routes in 86ca3d8.

@chadwhitacre
Copy link
Contributor

It isn't obvious what the Routes tab will lead to.

I agree that "Routes" is confusing to users (and I like "Money I/O" as a developer-facing term). I didn't go with "Payment Routes" originally because it was so long relative to the other nav items. "Payments" is maybe okay—probably better than "Routes"—though that's still ambiguous: is that payments I've made in the past? recurring payments I want to make in the future? oh, it's ... my bank account and credit card.

Looks like PayPal handles this with a "Money" page (which could start to move us towards #1063):

screen shot 2016-01-24 at 9 43 20 pm

screen shot 2016-01-24 at 9 43 25 pm

@chadwhitacre
Copy link
Contributor

Not sure how deep we want to set the plow here, though. We could spend a lot of time and energy if we stir the pot on navigation and IA, and I think we have bigger fish to fry. I'd accept a simple PR that changes "Routes" to "Payments" as @rohitpaulk proposes.

@chadwhitacre
Copy link
Contributor

+1 on Twitter:

Was looking all over for "payment methods". It's hidden under "routs" which doesn't mean anything to me. Reword?

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

6 participants