# How do you make a product feel coherent across phones and wearables?

By Sean Everett · October 8, 2026

Give each device a clear role while preserving the task across transitions. Define shared state, synchronization and notifications around what the person is trying to do.

Topics: Cross-device products · Mobile apps · Wearables

## Choose the job for each surface

A small wearable display, a phone screen and a widget offer different opportunities for interaction. Decide what a person should be able to notice, start or complete on each. Keep complex setup where there is enough room to make the choices understandable.

Begin with a few task transitions. Someone might start a focus session on a phone, check its status on a watch and later review the result on the phone. Define what should appear at each step and how the person continues.

Evergences’ mobile and wearable assistant beta combined native applications, widgets, notifications, watch complications, synchronization and integrations. Those surfaces share a product experience while serving different moments of use.

## Define the state that travels with the task

Identify which information is shared across devices and which belongs to a particular surface. Give shared records stable identities and clear update rules. Decide what happens when two devices change the same item before either sees the other’s update.

Make freshness visible when it matters. A device may be offline, an integration may be delayed or background activity may be limited. Show enough state for the person to understand whether they are seeing current information and whether an action has been saved.

Choose the supported behavior for each operation while disconnected. Android’s offline-first guidance distinguishes reading local data, writing only when connected and storing a local change for later synchronization. An offline label therefore leaves important differences in what a person can finish.

Test a complete disconnected task with the reference information it needs already available. Show whether a change is stored on this device, awaiting synchronization or confirmed elsewhere. Define when cached information becomes unsuitable to use, and test conflicting edits and repeated attempts after reconnection. Keep operations that require a current shared decision unavailable until that decision can be obtained.

Design interrupted transitions deliberately. If a person starts a task on one device and finishes elsewhere, preserve the meaningful progress. If an operation cannot continue, explain what remains and provide a supported next step.

## Coordinate attention across the devices

Treat notifications as part of the same conversation with the user. Define which device should alert, how duplicate alerts are handled and what acknowledging an alert means elsewhere. Avoid making the person dismiss the same event repeatedly.

Test the experience with one device unavailable, permissions changed and an underlying integration disconnected. Include repeated taps and delayed updates. These conditions reveal whether the product’s state is understandable beyond the ideal path.

Use a limited beta to observe the transitions that matter most. Improve continuity and recovery before adding more surfaces. Measure the success of the complete task, alongside the behavior of each individual app.

## Related reading

- [Productizing a mobile and wearable assistant](https://evergences.com/case-studies/mobile-wearable-assistant-beta/)
- [Building durable context for AI workflows](https://evergences.com/case-studies/durable-ai-context-beta/)
- [Android Developers: Designing an offline-first application](https://developer.android.com/topic/architecture/data-layer/offline-first)
- [Related owned product: Jetpack Ultra — cross-device dashboard (TestFlight beta)](https://www.jetpackultra.com/)

Source: https://evergences.com/insights/cross-device-product-continuity/