Inspiration
We were inspired by a simple observation: most calendar tools optimize logistics, not human performance.
What it does
Pebble analyzes your weekly schedule and scores it across five pillars: Sleep Recovery (meals, breaks, rhythm) Cognitive Performance Fitness Social Time
Instead of generating a single “optimal” schedule, Pebble creates three tradeoff-based alternatives:Sleep Optimized, Study Optimized, and Fitness Optimized
Each option includes: A total performance score Pillar breakdown Clear pros and cons Tradeoff explanations
How we built it
Pebble is a full-stack web application built using:
next + react + react-dom @google/generative-ai for Gemini calls Tailwind CSS
Challenges we ran into
Avoiding oversimplified scoring Tradeoff modeling Performance explanation
Accomplishments that we're proud of
Designing a structured, explainable performance scoring engine Modeling cross-pillar biological effects Generating tradeoff-based schedule alternatives instead of a single solution Maintaining clarity and simplicity in UI despite complex underlying logic
What we learned
Scheduling is not just a logistical problem — it’s a systems problem. Human performance has tradeoffs; there is no universally optimal week.
What's next for Pebble
Adaptive learning from user behavior Longitudinal performance tracking
Built With
- chatgpt
- claude
- gemini
- gemini-api
- next
- reach-dom
- react
- tailwind
- typescript
Log in or sign up for Devpost to join the conversation.