Inspiration
Students with back-to-back schedules told us the same thing: their phone is always charged, but their AirPods, iPad or Apple Watch die mid-lecture. Apple's low-battery alerts fire at 20% and 10%, which is too late to find an outlet, and checking each device by hand adds up when you own four or five.
What it does
Charge Ahead extends the Apple battery widget so one device shows the level, charge status and estimated time remaining of every device on your Apple ID. It reads your calendar on the device and sends one alert before an event when a device won't last, for example "Charge your Watch and AirPods before your 2 PM lecture - about 30 min needed." If there's no time to charge, it suggests how to save battery. After a couple of weeks of history, it also learns your charging habits and predicts when a device will run low, even on days with no calendar events. Alerts are capped at 1 to 2 per day, and all calendar and usage data stays on the device.
How we built it
We started with a kickoff and scoping session on the Apple ecosystem, then surveyed students, built two personas (an on-campus power user with 4 to 5 devices and a commuter with 2 to 3) and mapped their journey. We turned those findings into an MVP prioritization matrix and a full PRD with prioritized features, user flows and 15 testable requirements. Then we built the Apple Battery Widget prototype in Figma Make.
Challenges we ran into
- Notification fatigue: respondents wanted help but set a firm limit of 1 to 2 alerts a day, so we designed around an alert cap and combined alerts.
- Privacy: calendar access only works if users trust it, so on-device processing became a core requirement, not a feature.
- Scope: we cut charger-location alerts and non-Apple devices so the MVP stayed focused on the validated problem.
- Prediction needs history: new users have none, so calendar alerts work from day one and predictive alerts turn on later.
Accomplishments that we're proud of
- Every survey respondent was comfortable letting the feature read their calendar as long as the data stays on the device.
- A complete PRD with success metrics, acceptance criteria and open questions, built from real user research.
- A clear split between what is validated (calendar-based reminders) and what still needs testing (history-based prediction).
What we learned
- The devices people forget are the accessories, not the phone.
- Time remaining ("about 2 hours left") is more useful than a percentage.
- With notifications, fewer and better timed alerts matter more than extra features.
- Prioritizing hard, and writing down what we are not building, made the product stronger.
What's next for Charge Ahead
- Test with real users: run a prototype test with students like our two personas to check that the alerts feel well timed and that people keep calendar access on.
- Add battery-saving tips and a morning summary: suggest steps like Low Power Mode when there's no time to charge, and offer an optional daily snapshot of every device's battery.
- Check technical feasibility: confirm that iOS can report battery for AirPods, Apple Pencil and Apple Watch, and that background checks don't drain the main device.
- Measure what matters: track how many alerts lead to charging within 30 minutes, how many get ignored, and how many users keep calendar access on after 30 and 90 days.
Built With
- claude
- figma
- figma-make
- google-docs
- google-form