Inspiration
Starting college can feel like being handed a map with no directions. Students may know what they hope to do—find an internship, join a research team, or explore a career—but not which campus opportunities might help them take a next step, or who they can reach out to for guidance.
Additionally, with the resources currently available, it is often difficult for the new guy to start getting involved and connected, and it can be just as hard for the alumni to stay in touch when they move on.
We built WarmPath for the undergraduate who is still figuring it out, and for those who wish to keep connectin. It brings campus resources and opportunities into one place and helps students explore possible routes toward their goals, while also providing a platform for discussion and connection. Rather than serving as a guarantee for success, WarmPath is designed to make the people and the options easier to discover and the next step easier to see.
What it does
WarmPath offers a platform that aims to connect users with what is happening on campus, especially in relation to the careers and goals they wish to fulfill. The services provide path and resource discovery, and a community experience.
Our goal was to make the project useful to someone who does not yet know what to search for or whom to ask, as well as those who may just feel a desire to keep a hold of some means of connection and helping those after them.
How we built it
Building WarmPath gave us hands-on experience across the full stack. We worked on user interfaces and visual design, connected frontend experiences to APIs, built backend services, and used PostgreSQL to persist application data. We also explored how web and mobile applications can work together, including using Expo Go to run and test our mobile prototype.
Our work involved coordinating across these pieces as a team. We used an agentic workflow to help with development tasks, while still needing to make shared decisions about product scope, technical boundaries, and how the different parts of the application should fit together. We also explored AWS as part of thinking through how a full-stack project could be deployed.
Challenges we ran into
One of our biggest challenges was keeping the web and mobile experiences coherent as the project evolved. We also had to make design and architecture decisions while multiple features and teammates were moving in parallel. Branches, merges, and differing assumptions sometimes created conflicts that required us to revisit how we coordinated work and how shared interfaces should behave.
We worked through these challenges as a group—clarifying responsibilities, aligning on shared contracts, and integrating changes across the project. That process taught us that teamwork is not separate from engineering: collaboration, coordination, and resolving tradeoffs are part of building the product.
Accomplishments that we're proud of
We are very happy to have accomplished what we have. The development of this website and app prototype involved a great deal of effort and sacrifice. Because of this, the simple fact that we managed to produce such a product is augmented by the fact that we managed to pull off, as a team, what we had set out to do.
What we learned
We learned that a working product is more than a collection of screens or endpoints. A successful full-stack application depends on clear API contracts, reliable data models, consistent design decisions, and communication between the people building each part. On top of all of this is the vast experience we were able to gain in the fields mentioned before.
What's next for SWARM
Moving forward, gaining access to and adding more relevant user, student, and resource data can allow the app to be more functional and up to date, providing the resources that students will really want and giving alumni a meaningful way to pass on some help. Working with existing databases as well as exploring opportunities to gain users organically and collect data can help to further this end.