Campus

01 / Problem

Make connection specific to a university community.

Create a dating product for college communities that reduces low-intent swiping, verifies university identity, and makes it easier to move from discovery to real plans.

02 / Context

College life changes the product context.

A student-only network changes the product context. University verification, community trust, and safety need to feel native to the experience rather than layered on afterward.

03 / Constraints

The standard is coherence.

• 01Use .edu verification and layered checks without making sign-up feel clinical.
• 02Connect richer profiles, intent-aware discovery, chat, and planning across mobile and backend systems.
• 03Build clear reporting and blocking into the experience without overstating an early-stage product.

04 / Approach

One connected product practice.

Shape the product around a verified network: richer profiles, intent-aware recommendations, and a direct path from conversation to in-person plans, with product strategy, interaction design, mobile work, and backend systems developed as one discipline.

05 / Outcome

Founder-led product work, end to end.

Campus brings product strategy, backend architecture, native mobile development, and trust-focused interaction design together under founder-level ownership.

06 / Lessons

What the work keeps clarifying.

1. 01

   Verification and safety are interaction-design concerns as much as systems concerns.

2. 02

   Consumer product quality depends on consistency across strategy, interface, mobile, and infrastructure.