All work

032024 — 2025

UW-Social

A student-centered event discovery and community platform.

Visit project
Role
Founder & Project Lead — 9-person team
Stack
FirebaseFirestoreGoogle CloudGeminiReact
Product architecture and user flow diagram for UW-Social
Fig. 05 — Platform architecture and community loop
01

Problem

Campus event information is scattered across email, Discord, social media, and org websites. Students burn time searching and still miss things worth attending.

02

System

A Firebase-backed platform centralizing discovery, community interaction, and personalized recommendations, fed by a newsletter ingestion path that turns unstructured email into structured events.

  • Ingestion — subscribed newsletter accounts parsed into structured event records
  • Data — Firestore collections for events, notes, and user profiles
  • Intelligence — Gemini for summarization and recommendation
  • Community — Discord and WeChat loops feeding content back in
03

My contribution

  1. 01Founded and led a 9-member cross-functional team across engineering, design, and marketing.
  2. 02Defined the product vision and development roadmap.
  3. 03Ran user interviews and two rounds of validation, then drove iteration from that feedback.
04

Engineering decisions

01

Solving the cold-start problem

Problem

Without enough event supply, students see no value — and without users, organizations do not post.

Decision

Narrowed to engineering and business events instead of chasing full campus coverage, and built direct relationships with student organizations.

Tradeoff

Lower initial coverage.

Outcome

Higher information quality and a defensible first audience.

02

Scalable event collection

Problem

Most event sites restrict large-scale scraping, so automated aggregation was unreliable.

Decision

Collected newsletters via subscribed email accounts and converted them into structured event data.

Tradeoff

Extra preprocessing per source.

Outcome

Stable long-term collection that does not break when a site changes.

Technical architecture diagram of the UW-Social web platform
Fig. 06 — Frontend / Firebase / integrations
05

Results

Growth metrics

300+
Curated events
100+
Active users
60+
Discord members
150+
WeChat community

Lessons learned

  • Products come from continuous user feedback, not feature accumulation.
  • Solving the right problem is usually worth more than building more functionality.

Next project