The most important use case for mobile is having push notifications. So while the mobile app is in development its time to make sure our backend is ready for notifications.
I'm looking at using the mailboxer gem for the actual notification part and we can continue using the public_activity gem to create that "firehose" of activity data that we want to track. We'll be able to pick and choose what data out of that we actually want to "notify" a user about - which we'll do through mailboxer. This will also allow us to generate notifications for things that aren't "activity" based, like reminders ("You have an event upcoming", etc). Mailboxer also allows users to send messages to each other which is something that'll be useful even if its super simple.
The most important use case for mobile is having push notifications. So while the mobile app is in development its time to make sure our backend is ready for notifications.
I'm looking at using the mailboxer gem for the actual notification part and we can continue using the public_activity gem to create that "firehose" of activity data that we want to track. We'll be able to pick and choose what data out of that we actually want to "notify" a user about - which we'll do through mailboxer. This will also allow us to generate notifications for things that aren't "activity" based, like reminders ("You have an event upcoming", etc). Mailboxer also allows users to send messages to each other which is something that'll be useful even if its super simple.
337 #427