Some of the best context is already on the device. Calendar events, health activity, and system signals can explain what a note means without forcing you to repeat details by hand.
ISEA's native sensing direction is about respecting those sources and using them carefully. The landing card shows calendar and health records moving into the same context layer as your own notes.
What native context unlocks
When a user says, "the design review went well, remind me to polish the prototype tomorrow," the calendar can help identify the meeting. When a user logs a run, health data can provide distance and timing. The app can enrich the record without asking the user to re-enter what the phone already knows.
That creates better records:
- meeting notes linked to the right event
- movement logs aligned with health data
- follow-ups that keep their original context
- reviews that reflect the day as it actually happened
The boundary
Native sensing should feel useful, not invasive. ISEA's approach is to keep the user in control of what connects, what syncs, and what stays local.
The goal is simple: make the device's existing context work for the user, while keeping the user's boundaries intact.