AI first should not mean AI everywhere
A phone still needs to be an excellent phone. Calls, camera, messaging, battery, accessibility, security and apps do not become less important because a model can summarize something.
ePhone is eFind’s AI-native phone product in active development—designed around eOS, eIntelligence, eLine, eGlass and the North Star interaction.

ePhone is a real eFind product in active development. No availability or launch date has been announced, and engineering targets can change while the hardware and software are validated.
The idea is an AI-first mobile experience built around the same North Star interaction language as eFind: ask, understand and act. Rather than making intelligence a feature hidden inside individual apps, the device could treat intelligence as a layer across communication, files, maps, camera, travel and everyday tasks.
The device also forces harder questions about local intelligence, privacy, security, battery life, connectivity and what must continue working when the network disappears. Those constraints are not footnotes. They are the product.
Imagine broadly. Promise carefully.
The interesting test is not whether a prototype can make a room applaud. It is whether the device can help with a missed flight, a weak signal, a dying battery, a family group chat, a boarding pass and a work problem—without making any of them harder.
A person should be able to start with the objective—“get me home,” “find the document,” “reply to this,” “what changed?”—and let the system coordinate the relevant capability. Apps may still exist. The point is to reduce the choreography required to use them.
The device cannot become helpless every time the network hiccups. We would need a deliberate split between on-device intelligence and network intelligence, with essential functions, privacy-sensitive tasks and safety-related behavior designed around what must continue locally.
eFind ONE could provide the identity and permission layer, but the interface has to make boundaries obvious. A phone knows an extraordinary amount about a person. “Technically permitted” is not the same thing as “reasonable to do.”
Battery life, radios, thermals, repairability, camera systems, displays, materials and durability matter more than a beautiful render. If the hardware is not pleasant to carry and dependable to use, the intelligence has nowhere useful to live.
ePhone is BUILDING. The product site documents the current family, design direction and engineering targets while we work through hardware validation, eOS, connectivity, privacy, battery life and the parts that become much less glamorous once a prototype has to survive an ordinary Tuesday.
The goal is simple to say and considerably harder to build: a phone that knows when to help—and when to disappear.
ePhone is in active development—not a shipping device or announced launch date. The product asks what a mobile experience looks like when eFind ONE, eIntelligence, eDrive and the North Star interaction are designed together from the beginning.
A phone still needs to be an excellent phone. Calls, camera, messaging, battery, accessibility, security and apps do not become less important because a model can summarize something.
Some intelligence belongs on the device for latency, resilience and privacy; other tasks may need cloud compute or current web information. The interesting design problem is choosing the boundary well.
Cellular, Wi-Fi and future satellite options can eventually become one connectivity problem from the user’s perspective. That does not mean eFind needs to own every network underneath it.
The design test: can the phone make the ecosystem feel simpler rather than merely putting more eFind icons on a home screen?
Models, engineering targets, eOS, eLine, camera direction, accessibility, connectivity and development status are documented on the dedicated ePhone site.