A workout application developed with friends during a hackathon, where a limited build window forced the team to choose a focused user flow and execute quickly.
PROJECT AT A GLANCE
A short build window forces the team to identify one useful workout flow, divide it into compatible pieces, and reserve enough time to combine and demonstrate them.
01 / Context
Kasli explored how a digital product could support workout planning or tracking. The hackathon format made scope the central design constraint: the team needed a concept that could be demonstrated coherently within a short period.
The project combined product decisions and implementation under time pressure. Every feature competed for the same limited attention, so the team had to distinguish the core experience from attractive extras.
02 / Approach
The work began by establishing the shortest end-to-end path a user should be able to complete. Tasks could then be split between teammates while maintaining shared assumptions about data, navigation, and the demo.
Rapid prototyping favors simple components and known patterns. The goal was not to design an entire fitness platform, but to create enough of the intended workflow to test the idea and communicate it.
03 / Result
Kasli remained a team prototype rather than a maintained public product. The surviving portfolio record is limited, so specific features and outcomes are not overstated here.
As an experience, it demonstrated how quickly team communication, scope control, and integration become the determining factors in a short build.
04 / Reflection
Hackathons reward a thin complete path more than many disconnected screens. A demonstration also needs time for integration and recovery from failures, not just feature construction.
A future version would start with user interviews, choose one measurable workout problem, define a minimal data model, and validate that core loop before expanding.