Cross-platform feature design
One feature designed to behave identically on web and mobile.
Cross-platform · flagship
ZEVA referral & promotions engine
Full-stack developer
I built one referral system that lives in three places at once — the Django backend that issues rewards, the Angular web flow that manages them, and the Flutter app that redeems them. It is the cleanest proof of range I have: a single feature that had to be right across the whole stack.
DjangoAngularFlutterPostgreSQLDeep linksSigned redemption
- Platforms
- Web + mobile
- Backend
- Django + PostgreSQL
- Web
- Angular
- Mobile
- Flutter
The problem
A referral and promotions program only works if every tier agrees. Rewards have to be issued on a cycle, acquisition has to survive an app install, and redemption has to be tamper-proof — across web and mobile at the same time.
What I owned
Designed and shipped the feature end to end: cycle-based reward issuance in Django, referral and promotion management in Angular, and deep-link acquisition plus in-app redemption in Flutter, all over one shared PostgreSQL model.
The hard parts
- Keeping reward state consistent across backend, web, and mobile without drift.
- Making acquisition survive the gap between a shared link and a fresh app install, using deep links.
- Signing promo redemption so it can't be replayed or forged.
The result
Shipped a referral & promotions engine that behaves identically across web and mobile, issuing and redeeming rewards on a live product.
How it fits together
- 01
Django backend
Issues cycle-based rewards and validates signed redemptions.
- 02
PostgreSQL
Single source of truth for referral and reward state.
- 03
Angular web
Referral dashboard and promotion management flows.
- 04
Flutter mobile
Deep-link acquisition and in-app redemption.
Skills it proves
API + data modeling
Modeled the reward lifecycle so every tier reads the same truth.
Secure redemption
Signed promo redemption to prevent replay and forgery.
Want the rest of the story?