01 · Senior project
Campus Pulse
A location-aware campus event discovery experience for CSULB students, designed to surface what is happening nearby without burying people in another noisy feed.
Selected outcomes
- Refactored API access into reusable service layers
- Built responsive Flutter interface patterns
- Integrated map-based campus discovery concepts
- Collaborated across authentication, security, and cloud workstreams
The problem
Campus activity is fragmented across flyers, social accounts, group chats, and word of mouth. Students can spend years at a university without discovering events or communities that match their interests.
Campus Pulse explores a simpler question: what if students could open one map and immediately understand what is happening around them?
My contribution
My work focuses on the application layer: interface structure, layout, refactoring, and the service architecture that connects Flutter screens to backend endpoints.
I consolidated repeated networking behavior into a shared API client and separated event, interest, and user operations into focused services. That makes the code easier to test, reason about, and extend as backend contracts evolve.
- Reusable authenticated API client
- Dedicated user, interest, and event services
- Interactive map and event-discovery interface
- Clearer separation between UI and networking concerns
What I am learning
The technically correct design is not always the design that survives a team project. Good architecture also needs understandable boundaries, useful documentation, and enough flexibility for several people to work without stepping on each other.
This case study is intentionally marked in development. I will continue replacing this template copy with screenshots, architecture decisions, measured outcomes, and lessons as the capstone progresses.