Unicore Social is earlier work and no longer in active development. This page describes what we built and what I learned from it.
Context and problem
Campus life runs on scattered channels. Club announcements live in one group chat, event invites in another, internship opportunities on a notice board nobody passes twice. Students miss things that were meant for them, and clubs spend their energy on distribution instead of on what they are organizing.
What the product was
Unicore Social was a social platform for university life: one network connecting students, clubs, events and opportunities. A student saw the campus as a connected space rather than a pile of channels. A club reached the people its event was made for. An opportunity found the students it fit.
My role
Co-founder. I worked on the product and the community side: how the network should feel to a student, and how clubs and communities would actually use it.
System architecture
- One connected network
- Shared campus identity
- Students
- Clubs
- Events
- Opportunities
- Events reach the right people
- Opportunities find their students
- Clubs focus on organizing
The core idea was the graph in the middle: every student, club, event and opportunity a node, with relevance travelling along the connections instead of being broadcast to everyone.
Product decisions
Community first, features second
A campus product lives or dies on whether communities adopt it. Unicore Social was shaped around club and community workflows from the start, not around a feature list.
The campus as the unit
We treated a single campus as one connected space rather than trying to be a generic social network. Density inside one campus mattered more than reach across many.
What I took from it
Unicore Social was where I started building companies. It taught me that adoption is a product problem, not a marketing one.