The Signal
What becomes useful
Helping local discovery feel less like a noisy list and more like a trusted path to relevant businesses.
TEAM PROJECTFull-stack contributor
Trust-first local discovery
Vantage
Helping local discovery feel less like a noisy list and more like a trusted path to relevant businesses.
The Noise
What makes it difficult
Local-business data changes constantly: categories, photos, trust signals, saved places, owner flows, and deployment realities all compete for attention.
The System
A path through the search space.
The team product combines a React discovery interface with business data, place enrichment, saved-business actions, owner workflows, and backend services. Affan's public pull requests span both sides of that path: from early models and routes to discovery UI, image enrichment, preference onboarding, and later Supabase compatibility work.
- 01Business records
- 02Place enrichment
- 03Discovery interface
- 04Saved / owner flows
My Contribution
- Contributed early backend and frontend systems across auth, business/deal/review/user models, routes, API work, and UI surfaces.
- Improved discovery, image enrichment, Google Places integration, and explore UI components through merged PR #26.
- Added demo mode, owner events, saved-business flows, discovery updates, metadata/photo proxy services, preference onboarding, and account/business UI through merged PR #30.
- Contributed Supabase compatibility and explore-discovery regression test work in PR #160, with attribution caution because the PR also includes another contributor's security-fix commit.
Important Decisions
Decisions that shaped the system.
- 01Enrich before presenting
Discovery work joined local business records with images and Google Places data so the interface could surface more than a bare database row.
- 02Make trust actionable
Saved businesses, preferences, owner events, and account surfaces turned discovery into a sequence of actions rather than a static directory.
- 03Protect discovery during change
Supabase compatibility and explore regression tests helped preserve behavior while the wider team architecture evolved.
Product In Motion
The system, made visible.
Verified Outcome
What the evidence supports
The public record contains merged full-stack pull requests and a current live deployment linked from the repository. No user, revenue, adoption, or business-impact metrics are claimed.
What Changed In My Thinking
The principle carried forward
Discovery quality is not only a ranking problem. Provenance, imagery, preferences, and the next useful action all shape whether a result feels trustworthy.
Team And Credits
This work is presented as a team project, never as a solo build. The public GitHub contributor list below credits visible repository contributors without assigning private team roles.