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

put some "shine" on the ledger notifications #4019

Closed
mrose17 opened this issue Sep 15, 2016 · 10 comments
Closed

put some "shine" on the ledger notifications #4019

mrose17 opened this issue Sep 15, 2016 · 10 comments
Labels
feature/rewards polish Nice to have — usually related to front-end/visual tasks.

Comments

@mrose17
Copy link
Member

mrose17 commented Sep 15, 2016

example 1: if the client can't retrieve the data, how does it know that the account is under balance. seems to me that the "Your account..." status shouldn't be there:

0

example 2: at the top we're told we have less than 24h to review (great!), but the status gives a date for the next contribution (confusing). i suggest that when <=24h, that the status indicate how long until the contribution. (hint: use the magnificent moment package, e.g. moment.fromNow(true)):

1

example 3: when funds are pending, i don't think it makes sense to talk about a 'Next contribution':

2

example 4: if the contribution date is in the past (this screenshot was taken on 9/15), and the balance is sufficient, then instead of "Next contribution" we ought to have something like "Contribution being processed":

3

@mrose17 mrose17 added polish Nice to have — usually related to front-end/visual tasks. feature/rewards labels Sep 15, 2016
@mrose17 mrose17 added this to the 0.12.3dev milestone Sep 15, 2016
@bradleyrichter
Copy link
Contributor

example 1: Agreed. Status report should switch to something like: Status update not available. Please check your internet connection and try again.

example 2: seems like P2 polish to me.

ex 3: why not? If it's tomorrow, then hurry up!

ex 4: different problem - the contribution date can never be in the past. In this case, always make it the same day?

@mrose17 mrose17 changed the title put some "shine" on the ledger notifiations put some "shine" on the ledger notifications Sep 20, 2016
@mrose17
Copy link
Member Author

mrose17 commented Sep 21, 2016

also note that in example 2, there is no "Later" button. there should be. otherwise, the only way to get the notification to go away is to click "Review your chosen sites".

@bradleyrichter
Copy link
Contributor

One point I forgot to make here. Most likely, the top bar notifications will not be seen together with ledger screen until user clicks on the CTA button.

#2 needs an "Ok" button. I think 24h later is already later. No?

@mrose17
Copy link
Member Author

mrose17 commented Sep 21, 2016

i suspect that if the active tab is about:preferences#payments then notifications shouldn't be seen. i don't know whether they should be discarded or re-scheduled.

@diracdeltas & @ayumi - your thoughts?

@mrose17 mrose17 modified the milestones: 0.12.4dev, 0.12.3dev, 0.12.5dev Sep 27, 2016
@mrose17 mrose17 removed this from the 0.12.5dev milestone Oct 4, 2016
@mrose17 mrose17 added this to the 1.1.0 milestone Oct 17, 2016
@mrose17
Copy link
Member Author

mrose17 commented Dec 15, 2016

@bsclifton - can we close this issue now?

@bsclifton
Copy link
Member

bsclifton commented Dec 16, 2016

@mrose17 absolutely- @luixxiul has done a killer job with the CSS

From here on out, we can open issues as-needed 😄 There are existing issues for some of the above

@mrose17
Copy link
Member Author

mrose17 commented Dec 16, 2016

groovy!

@luixxiul
Copy link
Contributor

While I haven't tweaked something on the notification bar?

@mrose17
Copy link
Member Author

mrose17 commented Dec 16, 2016

@luixxiul - i think that as a part of some general refactoring, the notification bar issue above was polished... so, we're done with this issue!

@luixxiul
Copy link
Contributor

sweet!

@luixxiul luixxiul modified the milestones: 0.13.0, 1.1.0 Dec 16, 2016
@bsclifton bsclifton removed this from the 0.13.0 milestone Dec 16, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature/rewards polish Nice to have — usually related to front-end/visual tasks.
Projects
None yet
Development

No branches or pull requests

4 participants