RichlyMe

A young, affluent audience wants to share experiences, but not in a public feed. The product had to be a closed stage: everything shown inside had to be real and provable, and nothing could leak out. There were two traps. If points can be bought, status loses its value. Real-time, exact location sharing is a safety risk for this audience.

Proof comes only from the in-app camera. When the camera opens, the server issues a single-use code valid for 120 seconds; the code appears in the frame and is bound to the proof on submission. The scoring formula lives in a SQL function (score_proof), is callable only by the service role and does not grow linearly with money spent.

Publishing is delayed: a proof appears at least 24 hours later, and only at city level. The backend is 49 migrations and 17 Edge Functions on Supabase, with row-level security checked by 401 tests across 38 SQL test files. Membership is sold only through Apple in-app purchase, managed with RevenueCat. The interface is built with Expo and React Native; the door opening, medallions and member card are drawn with Skia.

The app is being prepared in 12 languages, including right-to-left Arabic. The visual language is bespoke: no stock icon set; the badges, the seal and the “door ajar” light motif were designed for it. Privacy controls (delay length, app lock, screen-capture guard) stay with the member. The app is in development and not yet on the App Store.