Outdoor-time schedule
A user enters an outdoor window and personal profile inputs. The core schedule engine produces a list of planned applications and allows completed or skipped records.
RE:APPLY
Keep a personal
routine in view.
An iOS prototype for recording sunscreen application and scheduling personal reapplication reminders around outdoor time and available UV information.
Core and simulator validation
A reminder, not a health judgment
Re:Apply is being built as a personal routine tool. It does not diagnose skin conditions or guarantee a safe exposure time.
Data-state visibility
The design distinguishes fresh, stale, estimated, and unavailable UV information so a reminder is not presented as more certain than its input.
One record path
In the planned app, notification actions, an app button, widgets, and a watch surface all feed one recording path. Widget and watch delivery still need real-device validation.
From an outdoor plan to a record
Users can see the data state and update their own routine as the day changes.
-
01
Set today’s routine
Choose an outdoor time and enter the inputs used by the personal schedule.
-
02
Check data state
View whether UV information is fresh, stale, estimated, or unavailable.
-
03
Record an application
Mark a planned application done or skipped, then update the remaining reminders.
Illustrative workflow
- A user enters an afternoon outdoor window.
- Re:Apply shows the available UV-data state and a personal reminder schedule.
- After applying sunscreen, the user records it and the remaining reminder list is updated.
Claude Code in the development loop
Claude Code is used to plan, implement, and test the product state; it does not make health decisions for a user.
Inputs: schedule states and failures
We give agents schedule rules, timezone changes, missing-UV cases, and the Swift modules that coordinate records and local notifications.
Work: scoped tests
Agents run core and simulator checks for time boundaries, missing or stale data, skipped records, and reminder rescheduling.
Value: dependable routine feedback
The development workflow makes the data state and recovery path explicit when a forecast is unavailable or an application record changes.
The current prototype does not call the Claude API; Claude Code is used in development.
Questions at this stage
Does Re:Apply give medical advice?
No. It is a personal reminder prototype and does not diagnose skin conditions, prevent burns, or guarantee safe sun exposure.
Is every UV input verified for release?
No. The calculation inputs and real WeatherKit/device behavior need additional validation before a release claim.
Are widgets and watch features available now?
They are follow-up delivery and physical-device validation work; the current evidence is core and simulator validation.
Product enquiries