A useful mobile assistant should not assume you own a Mac.
The phone-only direction focuses on complete mobile tasks, with clear choices about what can run on the device or through cloud assistance.
Planned workflow · An illustrative direction, not available today.
The starting point
A self-employed professional wants to capture an idea, review selected information and leave with a practical next step while away from a computer. They may not have a desktop EVO installation at all; the phone needs to provide value on its own.
A miniature desktop interface is not a complete mobile experience. A short session may need a concise answer and one decision, while files, local models and desktop actions may not be available. Pretending the phone can perform every Mac task would create misleading expectations.
What you bring
- Planned: a spoken or written request and material the user deliberately selects.
- Planned: available mobile capabilities, connection status and the chosen processing mode.
- Planned: approved preferences relevant to the current task, without assuming access to every device or file.
What EVO needs to understand
The intended assistant would work backward from a useful mobile outcome. A request that fits the phone should finish there. A task requiring unavailable desktop tools should explain the missing capability and offer a useful preparation step, rather than claim it was executed elsewhere.
Working through it
Make a small session productive
The planned interface would prioritize the goal, the minimum relevant material and a clear deliverable. A clarification should appear only when its answer would materially change the result; independent preparation need not become an endless question sequence.
Choose a real execution path
Available device capability and the user's choice would determine the supported path. Local processing could be offered only where the actual device and installed model support it. Cloud assistance would require its own availability, limits and data agreement.
Leave a usable next step
The mobile experience should return the completed result or a specific stopping point with open questions. It should not label a draft as a submitted action, assume a Mac is online or turn an unsupported task into a hidden cloud request.
What you receive
- Intended: a result sized for a mobile task, not a desktop screen compressed onto a phone.
- Intended: saved progress and clearly identified remaining work.
- Intended: an honest explanation of the selected processing path and unsupported actions.
When you come back
Returning to the phone should recover the selected work without requiring a desktop handoff. Cross-device continuation, when available, would be an additional option rather than a prerequisite for every mobile task.
Your information and choices
- The design calls for explicit selection of attachments and cloud use.
- Notifications, location and voice access would require their own permission choices.
- Stopping a task should remain accessible in a compact mobile interface.
Current scope
Implemented foundation
- Current implementation evidence comes from the Mac product; mobile design can build on its work, consent and continuation foundations.
Next milestones
- The phone-only Alpha product and its model, voice, notification and device behavior still need implementation and real-device qualification.
- iOS and Android have no public installer or announced release date. Mac capabilities are not advertised here as completed phone features.
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.