01 / Cross-platform rewards
Referral + promotions engine
I designed the reward lifecycle in Django, then carried the same state through Angular and Flutter. One feature that had to agree with itself across three tiers, on a live product.
- Django
- Angular
- Flutter
- PostgreSQL
Redemption authority / ZEVA
Two clients can ask. One service decides.
Django issues rewards on a cycle and signs each one. The Angular console manages referrals and promotions; the Flutter app takes a deep-linked referral and presents the signed token at redemption.
Neither client settles anything. Django verifies the signature and the single-use state, then writes to the one PostgreSQL record both surfaces read.
A forged or replayed token fails at the signature
















