-
-
Failed log in attempt
-
Creating and activity as a staff
-
Activity page as a caregiver
-
-
-
-
-
Inspiration
Many activity sign-up systems are designed for individuals, but in caregiving contexts, sign-ups are often done repeatedly by caregivers on behalf of multiple dependents. This creates friction for caregivers and leads to heavy manual coordination for staff. We were inspired to build a solution that reflects how caregiving actually works.
What it does
WibesCoders is a caregiver-first activity registration system. A single caregiver account can manage multiple dependent profiles and bulk sign them up for activities with clear status visibility. On the operations side, the system enforces activity capacity in real time, reducing overbooking and eliminating manual consolidation for staff.
How we built it
We built a full-stack web application using a React frontend and a Node.js/Express backend with a relational database. Authentication is handled with JWTs, caregiver–dependent relationships are stored in the database, and bulk sign-ups are processed through structured APIs. Capacity and signup status are computed dynamically to support real-time visibility for both caregivers and staff.
Challenges we ran into
One challenge was balancing scope with impact within limited time. We had to prioritise features that meaningfully reduced real operational pain rather than adding complexity. Another challenge was designing flows that worked for both caregivers and staff without shifting work from one group to another.
Accomplishments that we're proud of
We’re proud that we designed around real caregiving workflows instead of form-based assumptions. Our solution supports bulk sign-ups, persistent profiles, and enforced capacity, all of which directly reduce cognitive load for caregivers and manual work for staff. We’re especially proud of delivering a working end-to-end system under tight time constraints.
What we learned
We learned that social impact products are often about reducing invisible burdens rather than adding new features. Designing for operations, clarity, and trust can be more impactful than designing for speed alone. We also learned the importance of scoping intentionally and building for real users, not idealised ones.
What's next for WibesCoders
Next, we’d like to expand caregiver profile management, introduce clearer eligibility indicators per activity, and enhance staff reporting tools. With more time, we would also explore waitlists, attendance tracking, and analytics to further support long-term programme planning and community impact.
Log in or sign up for Devpost to join the conversation.