Summary

Users want to have notifications when certain events happen on the Pair App.

Proposals

Gem Solution?

✅ Proposal 1: Noticed Gem

Use the noticed gem

Pros

1. Seems very robust and should be able to elegantly handle expanding usecases
2. Avoids needing to jump through the hoops on rolling our own

Cons

1. It’s a new dependency

Notification Delivery Methods

These proposals aren’t mutually exclusive and multiple ones can be chosen and implemented. These are related to the methods we’ll use to deliver the notifications to a user.

❌ Proposal 1: In-App UI

Notifications are persisted to the database in a new model(s) and there are views on the app for displaying them. To start, I was thinking this could be kept super simple to an index view for seeing notifications and a new link in the header to visit that page. The link can have some way of signaling to the user that there are unread notifications. This will require wireframes to more precisely outline how this feature would look.

Pros

1. User can view and interact with this information while using the app. This may allow them to navigate more quickly to items that need their attention.

Cons

1. Potential for lots of database reads/writes centered around notifications. Difficult to scale properly.
2. Probably reduced utility compared to emails or other off-app deliveries?