Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Temporary In-App User Notifications #495

Closed
roryabraham opened this issue Sep 15, 2020 · 4 comments
Closed

Temporary In-App User Notifications #495

roryabraham opened this issue Sep 15, 2020 · 4 comments

Comments

@roryabraham
Copy link
Contributor

roryabraham commented Sep 15, 2020

cc @megankelso @michelle-thompson @tgolen

Problem

We don't currently have a way of displaying general-purpose temporary in-app notifications to users.

Potential Solutions

  1. Implement a reusable growl, snackbar, or banner notification in RNC, similar to the ones used in web and mobile currently.
  2. Use in-app messaging, and browser notifications on desktop/web. This is like push notifications in that they are typically persisted in the iOS/Android message centers, but typically show up as banner notifications in-app.
  3. Any other ideas welcome.
@roryabraham roryabraham changed the title Temporary User Notifications Temporary In-App User Notifications Sep 15, 2020
@mallenexpensify
Copy link
Contributor

@roryabraham Are you thinking more short term for the Proof of Concept or long term for public launch?

  1. For short term/PoC, they shouldn't be needed, right?
  2. For long term, would we be able to use snackbar notifications similar to how we do now?

My other thought is, I wonder how many of these types of messages we could send from Concierge. One potential benefit is we'd be encouraging people to interact with Concierge via Chat... maybe/hopefully

@AndrewGable
Copy link
Contributor

Agreed with @mallenexpensify that this seems like a long term discussion, for the POC can we just use the default OS notification?

@roryabraham
Copy link
Contributor Author

So after talking with @mallenexpensify some more, we really are thinking that 2. is probably the best option for a number of reasons. To name a few:

  1. It most closely mirrors how we're using browser notifications on desktop/web.
  2. It offers the look/feel and customization options of the native iOS/Android platforms.
  3. It doesn't require that we design or maintain our own in-app notification system.

@AndrewGable yes, I think that Airship's in-app messaging will provide an interface to utilize the default OS.

closing this issue out for now, can be revisited later if desired

@marcaaron
Copy link
Contributor

Missed this conversation, but I think we should start by doing nothing here for now.

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

No branches or pull requests

4 participants