SendLove: a Supabase-backed gift experience with separate sender and recipient journeys #52652
Replies: 1 comment
|
Nice split. On mobile I'd put the two journeys as two short lines right under the headline: "You: make the gift (free account, about a minute)" and "Them: tap the link. No app, no sign-up." Add one phone-sized preview of what the recipient sees and both questions are answered before anyone scrolls. Since recipients open gifts without an account, one thing worth testing on the data side: the gift link should use a long random ID, and your Supabase policies should let a logged-out visitor read one gift by that exact ID but never list the gifts table. Open a gift link in a private window, then try a request for the table with no filter; it should come back empty. I ran our free outside check on sendlove.io: no secret keys in the public code, /login and /signup load, and sign-in links point at your live domain. The only small item was a missing Content-Security-Policy header. What outside checks can and can't see: https://appfirstaid.com/guides/what-built-in-security-scans-miss I work on AppFirstAid; the free check is at https://appfirstaid.com |
Uh oh!
There was an error while loading. Please reload this page.
We're the team building SendLove, a browser-based digital gift project for everyday love and keeping in touch across distance. Sharing a small product-design example from an app using Supabase.
Two journeys, one gift
The sender personalizes a gift and needs an account to send it. The recipient opens the shared link in their browser without creating an account or installing an app. That distinction is part of the product: receiving a personal message shouldn't require joining another service first.
Our frontend uses React/Vite and the Supabase JavaScript client, including Supabase Auth. A Node.js/Express backend runs on Railway, with Supabase for data and Stripe for paid gifts.
What we'd like feedback on
For a shared experience like this, the homepage has to explain both who needs an account and what the recipient will actually see. We're interested in how other builders explain those two journeys clearly on mobile without turning the introduction into a technical diagram.
For context, our Love Letter is free to create and send, with a sender account required; other catalog gifts are paid. We're sharing the existing product, not claiming measured conversion or performance improvements.
Disclosure: SendLove is our own product. This introduction was prepared with AI assistance.
All reactions