The problem
You meet someone useful at a career fair, save their contact, and a month later can't remember where you met or why it mattered. ConnectiveNet is a digital rolodex for people who network in person. You scan someone's QR code, note why you met, and the context stays with them, so following up is easy.
The outcome
- Live on web and iOS. The web app runs at connectivenet.com, and the iOS app is built in React Native with Expo.
- One backend for both. The web and iOS apps use the same API, so the iOS app didn't need a second server or a rewrite of the business logic.
- Shipped on a capstone timeline by a three-person team working in Scrum sprints.
Decisions that shaped it
Agree on the API before the screens. We pinned down the API contract early. After that, web and mobile could be built in parallel against the same contract, and neither had to wait for the other.
Split the backend by domain. Each part of the product got its own Django app with clear ownership. Three people could work at once without stepping on each other.
Core loop first. AI follow-up suggestions, location features and real-time messaging were all on the table. We shipped the loop people use at every event first: meet someone, save them with context, find them later. The rest waited until that loop worked.
Expo for iOS. Building the iOS app in React Native with Expo let the team carry its React skills from the web app straight into mobile.
My role
I was a Software Engineering Capstone Developer, focused on backend design and application architecture. I set up much of the structure that let the web and iOS apps share one backend. I also helped turn a large product idea into epics small enough to finish each sprint.
The main lesson: on a team, the hardest calls are what to build first and who owns what. Getting those right early mattered more than any single feature.
Tech stack
- Backend: Django, Django REST Framework, PostgreSQL
- Web: Next.js, React, Tailwind CSS
- iOS: React Native, Expo
- Workflow: GitHub, Jira, Scrum







