0

What are some general UX best practices when notifying the user that something in your app has changed?

closed as off-topic by Evil Closet Monkey, Mayo, Devin, SteveD, ChrisF Sep 27 '16 at 15:07

  • This question does not appear to be about user experience within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

  • The question is quite vague, do you mean the app has had new features added, or do you mean that there is new data for the user? – thelem Sep 26 '16 at 16:33
  • 4
    I'm voting to close this question as off-topic because it does not provide enough specificity to the problem. There are a multitude of ways to address the universal issue of "notifying the user" which is dependent on a number of factors including, but not limited to: (1) platform, (2) environment, (3) impact of change, (4) severity of change, (5) task being performed. – Evil Closet Monkey Sep 26 '16 at 16:39
0

There are two ways of doing it.

Force to action. Redirect user straight to the information you want to to read. Examples: Google, PayPal, Barclays Bank terms and conditions.

Call to action. Throw a little message at the top of the page or even on the top of the header inviting users to read "what's new".

Your practice should depend on the situation you are in. Google, PayPal and my bank can tho something like that because no matter what they wrote there I want to get to my emails, money, ability to pay bills quickly. People like myself agree to new term without reading.

Not the answer you're looking for? Browse other questions tagged or ask your own question.