Hoagie is the Princeton application platform.

Hoagie is more than just a couple of different campus applications; it is an integrated system. Every application is built with others in mind, filling different gaps in your campus experience. Hoagie Apps allow you to use the same profile across the entire system, meaning you can do things like save your favorite courses in one application and then see them pop up on a different one instantly.

If you're interested in being part of the team creating this platform—the Hoagie Club—click the button below to apply to Hoagie!

How does this work?
The applications are all built from scratch, using shared UI elements, frameworks, and APIs. We also aim to have a defined tech stack, development practices, and guides, simulating the work style of real tech companies. Hoagie's applications being built for one another has its benefits: all apps can get the latest updates at the same time, show things like your set course schedule across different applications, and just generally provide a better user experience.
Why Hoagie?
In a world of Tiger[name], there was a need for something fresh. Hoagies represent many things—they represent how some in New Jersey call sandwiches. They also represent a certain iconic sandwich shop that has satisfied many Princetonian's late-night cravings. In short, many things connect Tigers to Hoagies, and Hoagie is embracing that to the fullest as we attempt to add a new word to Princeton's club names.
What is the goal of Hoagie?
Hoagie's goal is to make our campus applications better by reducing redundancies and isolation between their codebases and design. Through doing so, we hope to create a better developer and software engineering culture on campus—one that goes beyond a semester of COS 333. That's why we do our best to create design and development guidelines for the work we do.
Are Hoagie Apps the same as COS 333 projects?

For the most part, no! Beyond everything mentioned above, Hoagie also avoids many constraints of a COS 333 project—we get to work on larger (and smaller) projects, create and use project templates and a lot of ready-made corporate tools and APIs—all of which might not be "optimal" for a good grade in a class like COS 333. Finally, unlike class projects, we get to piggyback off one another's work to the fullest, which allows us to develop and deploy applications much quicker than someone starting from scratch.

Also, our projects aren't only for COS majors :)

I wanna learn more!
More information will become available quite soon but if you'd like to connect now, feel free to email hoagie@princeton.