Skip to content
This repository has been archived by the owner on Aug 10, 2022. It is now read-only.

Unify push notification UX guidelines #4034

Closed
gauntface opened this issue Jan 11, 2017 · 3 comments
Closed

Unify push notification UX guidelines #4034

gauntface opened this issue Jan 11, 2017 · 3 comments
Assignees

Comments

@gauntface
Copy link

From @dandv

We have two documents on good push notification UX:

What Makes a Good Notification? on Web Fundamentals
and
Best Practices for Push Notifications Permissions UX (strangely, a Google Doc)

Would it make sense to bring the latter under /web and/or merge it into the former?

CC @owencm, @jpmedley

@ithinkihaveacat
Copy link
Contributor

Related: the Material Design notification guidelines.

@beverloo
Copy link
Member

Missing links:

There's also the Android UX guidelines.

@gauntface
Copy link
Author

When I wrote up the original permission UX, I had Owens doc in mind.

Is there a particular bit I'm missing here?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants