A message survives beyond the push.
Keep useful messages available after delivery.
Where this work fits
Messages only help when they reach the right person at a useful time. A push can be missed, so customers also needed relevant email and a place to return to notifications.
I built persistent notification history and read-state behavior alongside delivery. The inbox gave customers a place to revisit information independently of whether they noticed a momentary push notification.
Schedule a tailored message across channels
Customer activity shapes the message and timing. Email or push delivers it, while the inbox keeps it available to revisit.
Match the message and timing to the customer.
Timing and audience mattered as much as the channel. I aligned sends with customer activity, filtered invalid device recipients, and kept a saved inbox so a missed push did not lose the message.
The skills behind the work
- SQL
- Query and update relational data, with clear rules about which records a result represents.
- Firebase Cloud Messaging
- Deliver device notifications separately from the application’s lasting message history.
- State management
- Represent what is happening now and define which changes are valid next.
Tailored, scheduled email and push notifications helped increase customer engagement by 30%.