WorkPulse

Inspiration

I built WorkPulse primarily for myself. When I spend hours in front of a screen, I forget to take breaks and move. I wanted a simple way to make movement part of my working day.

What it does

WorkPulse uses Google Calendar availability to suggest suitable windows for movement breaks. It offers short exercises with visual instructions, recognizes movements through the camera, and saves completed sessions in a shared history.

How I built it

I used TypeScript, Next.js, React, MediaPipe for movement recognition, and the Google Calendar API for calendar availability.

Challenges

Connecting calendar availability, exercise tracking, and saved history into one consistent experience was a major challenge. Camera-based movement recognition also needs further testing in real conditions.

What I learned

My biggest learning was working with camera-based movement recognition: understanding how body movements can become input for an application. I also gained experience integrating Google Calendar availability into a working prototype.

What's next

I want to improve recognition reliability and make the movement-controlled game clearer and more responsive. The current demo video uses a demonstration calendar and simulated pose input to show the workflow; it is not a live-camera accuracy test.## Inspiration

What it does

How we built it

Challenges we ran into

Accomplishments that we're proud of

What we learned

What's next for WorkPulse

Built With

• docker
• google-calendar-api
• mediapipe
• next.js
• react
• typescript
• vitest