Speak2 Family
Senior living, one message across four surfaces
- Web, mobile, Alexa and facility TVs, off one API contract
- 4 surfaces
- Signage feed and email bounces, both silent failures
- Monitored
- Beneathatree's platform, built by me
- Client owned
A message to a resident has to arrive on whichever surface that resident actually uses: the app, the website, the Alexa unit in the room, or the TV in the lobby. Four clients is where this shape of product usually comes apart, because each one grows its own endpoint and then they quietly disagree about what a message is. These run off one set of APIs, so a change lands on all four or on none. The piece with no user to complain about it is the signage feed to the TVs, which fails silently by nature, and that is exactly why it got monitoring before the surfaces people can see. Transactional email got the same treatment, bounces watched and retries handled, because a notification nobody trusts is a notification nobody reads.
Next.js and Express in front, Lambda, SES and a VPC behind. Built for Beneathatree, running in senior living facilities, where a missed message is not a defect in a dashboard.