We have a set of matching widgets we use as a homepage for an app. The user can interact with those widgets causing various notification dialogs. I think these dialogs should match the look and feel of our app/widgets. My bosses have opted to have them match standard unstyled android notifications as they reason that it's easier for the user to understand that they are being prompted to do something.

My bosses also said if any users mention it then we can re-discuss the options.

How can we prompt users to give feedback on such things in user testing without telling them it's because we consider they might need to match and biasing their opinion?

I have a feeling users will not mentions such things. I can't convince the bosses to do AB testing which means we can never get feedback from the other perspective, only from the perspective of people using the standard notifications.

  • You say: "I think these dialogs should match the look and feel of our app/widgets." Why do you feel it is necessary?
    – CJF
    Commented Mar 2, 2014 at 17:14
  • Our apps are used together as an entire suite (including a custom launcher with widgets), it all has the same look and feel except these dialogs and I think if we break away from this suddenly for dialogs it's quite jarring to the user. The dialogs don't even seem to be part of the application and we are relying on these users to have had android experience Commented Mar 2, 2014 at 17:23

3 Answers 3


Based on your answer to my clarification question, I would suggest that you start by testing if the users are able to use the dialogs properly as-is. Split your test group in two, based on previous Android experience (or not). Set up scenarios that you think will be "jarring" (as you put it), and see which users struggle. Also set up scenarios that should be easy/straightforward (that also rely on the dialogs) and see which users struggle.

At the end of the tests, ask them (in an open-ended way) if they could suggest any improvements (do not mention the dialogs), both functionally and aesthetically. Then count how many highlight the dialog styling as being out-of-place. Make your case with the data. If the users are able to perform the tasks to your client's satisfaction, then maybe the styling isn't such a major concern.

I suspect that users will grow accustomed to the look and feel of these "system" dialogs, in much the same way that desktop users know what the standard "Open File" and "Print" dialog windows look like for their operating system. Your use-case may be more complex, in which case the tests should yield some meaningful insights.


Why not use UsabilityHub?

Test your designs and mockups on real people

Learn how visitors will interact with your design before launching. Find out what they think, what they remember, and where they make mistakes.

Create a usability test where you pair up your widget design and versus your boss'.

See who gets the better feedback and go from there.

  • No they dont want to do AB testing or anything similar, they want to make changes from system defaults only if the users suggest it Commented Jan 31, 2014 at 8:57

I know this doesn't answer your question but generally you should stick to the system standards when possible. A user, having never seen your app, should know a notification for what it is. If you can embellish it with your app's brand in the process, great. Good luck, the politics in this situation can be tricky, especially when you're proud of your work.

  • That's only partly true. OP should focus on following design pattern guidelines rather than default system interface.
    – abhinavc
    Commented Jan 31, 2014 at 6:31
  • Politics aren't an issue here, we discuss things and then at the end of the day, they get what they want, because they're paying. However I want to ensure that in the tests the users are likely to give feedback on such things vs just features. The issue is, if we prompt them it biases them Commented Jan 31, 2014 at 8:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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