BU Spark! Project
[1] Problem
[2] Discovery Phase
We identified two main audiences: New incoming Freshmen and Transfer students. Both audiences require support in settling the community as they are new to the campus.




[3] Research and Insights
We conducted structured user interviews using a script, observing participants while they interacted with the app. Two rounds of interviews were tied to our two MVP milestones.


[4] Process & Design Development
Our goal is to help students on campus get familiar with campus community by providing nearby ongoing activities that can be filtered based on interests and popularities for students to be proactive.


Nearygle - Mascot and logo inspired by golden eagle as we want our app to be easy and recognizable. Eagles are known to be very aware of their surroundings


[5] Scope and structure
[6] Final Solution










Allowing user to user interaction of friends you see on the map while having the ability to host your public or private event.
At the end of the Spark! Innovation Program, our team presented Sanvia on Demo Day to the Boston University Faculty for Computing & Data Sciences with a presentation and on-display Eposters.


E-Poster
[7] Outcomes & Reflections
What worked well was the feedback loop between interviews and iteration. Each round of user testing gave us a clear, actionable signal — and because we responded to it directly in the next build, users could see their feedback reflected. That builds trust in the process.
What didn't work as smoothly was the early team disruption. Losing half the team created a rough start and forced scope decisions we hadn't planned for. In hindsight, earlier alignment on a leaner MVP would have cushioned that more.
The most durable lesson was about the value of design-first development. Having a visual reference before writing any code kept the product consistent and gave everyone a shared target. Without that, especially on a reduced team, it's easy for features to drift in style and feel. Design is not a nice-to-have at the start — it's the mechanism by which a team maintains coherence when bandwidth is tight.








