An idea on the move. A clear handoff at your desk.
The planned cross-device experience would carry the request, current progress and permission choices together from iPhone to Mac.
Planned workflow · An illustrative direction, not available today.
The starting point
A founder notices an issue on the product website while away from their desk. They want to capture the request on their phone, then continue with the right project and files when the Mac is available, without sending themselves a collection of disconnected notes.
Copying a conversation between devices can transfer words while losing the working context: which project was meant, what was already checked, which files exist only on the Mac and what permission the phone was actually given. A handoff needs more than synchronized chat bubbles.
What you bring
- Planned: a request captured on iPhone and an explicitly selected Work.
- Planned: the identity of a paired Mac and the material chosen for handoff.
- Planned: the original request time and the later continuation time, with each device's time zone preserved.
What EVO needs to understand
The intended experience would distinguish work a phone can finish from work that needs the Mac. It would carry the goal and relevant state, while requiring desktop availability and appropriate permission before a desktop action. Pairing would not mean permission to do everything.
Working through it
Capture the intended outcome
The phone would record the issue and desired result against the chosen work. If the user merely asks for a review, that request would not become permission to modify or publish the website on another device.
Resume where the material exists
On the Mac, the planned review would identify the incoming request and check the current project. Changed source files or unavailable permissions would need attention before execution rather than being hidden by the apparent continuity of the conversation.
Bring back a meaningful result
The mobile result should distinguish a prepared suggestion, an applied change and verified completion. An offline Mac would produce a waiting state, not a fictional success. Unknown external outcomes would need checking before another attempt.
What you receive
- Intended: one connected request and continuation record across devices.
- Intended: a clear next action when the destination device becomes available.
- Intended: an outcome view that says what ran, where it ran and what remains unresolved.
When you come back
The product direction is to resume the same Work, not create a second unconnected conversation. Reconnecting a device must not quietly replay an operation or reuse an expired approval.
Your information and choices
- Planned controls include device pairing and revocation.
- The user would choose the material and permissions carried to the other device.
- Location, routine history and all local files would not become automatic handoff content.
Current scope
Implemented foundation
- The Mac has persistent Work and reviewed local continuation foundations. Cross-device behavior is a separate development track.
Next milestones
- iPhone pairing, remote execution, synchronization and return-to-phone results are not released or verified as a complete customer workflow.
- There is no public iPhone installer or promised date. This page describes a planned journey, not a currently usable mobile feature.
These are development capabilities, not a public release. See platform availability before requesting a trial.
Platforms and availabilityBring a task you want to move forward.
Explore the Mac release, or tell us which workflow you would like to evaluate. An application does not guarantee an invitation.