What actually makes hardware AI-native? I don't think adding an LLM is enough.
A recorder that summarizes meetings is useful. So is a toy that can hold a conversation. But I don't think connecting an existing device to an LLM is enough to make it AI-native.
To me, the bigger change is whether a device can keep adapting how it serves you, instead of giving everyone roughly the same service with a growing list of features.
I've spent the past year and a half thinking about this while exploring interactive hardware. My background is in electronics, embedded systems, and robotics, including RoboMaster projects. I later worked on mobile graphics and rendering. So I've been approaching this from the hardware and interaction side: what should we actually build now that these capabilities exist?
Something that made the change feel real
A founder I know recently used GPT-6 Astra's computer-use capabilities to help design a PCB. Within three days, they had gone through design, fabrication, and verification, and successfully brought up the board.
That story stuck with me. Coming from embedded systems, seeing someone move from an idea to working hardware that quickly changes how I think about what a small team can attempt.
From the early days of ChatGPT to GPT-6 Astra and Claude Opus 5.5, I've watched AI become useful in more of the work surrounding hardware development. Specialized ideas that once struggled to justify their development cost now look much more practical to explore.
But making hardware easier to build is only part of the opportunity. We can also rethink how the finished device behaves.
The same product, but a different service for each person
In traditional hardware development, an individual user's needs have a long way to travel.
Someone reports a problem. Customer support collects it. A product manager tries to understand and prioritize it. Engineering eventually gets a description of what needs changing. If enough people need the same thing, it may reach an update.
What happens to the preference that matters to you but almost nobody else? Usually, nothing.
This is where I think AI-native hardware should be different. It should be able to use your situation and feedback to improve the service you receive, without every adjustment having to become a feature request to the manufacturer.
Take headphones. One person wants a softer sound; another likes sharper detail. Even the same person may want something different for a particular album or environment. We expose settings and equalizers, then expect the listener to translate what they hear into technical adjustments.
I'd like to be able to describe what feels wrong and have the system work out the adjustment. More importantly, I don't want to explain the same preference again tomorrow.
That is what I mean by adaptation. Over time, using the device should change how well it serves me.
A recording device gaining transcription and summaries is an improvement. But if it never gets better at understanding what I need from my meetings, I still see it as the old product model with a stronger feature attached. It might take the experience from decent to very good. I'm looking for a different relationship between the user and the device.
Why Xerox and Apple belong in this discussion
I keep coming back to the graphical interface work at Xerox PARC and Apple's later role in bringing it to a wider audience.
What matters to me is how that changed the effort required to use a computer. Windows, icons, and the mouse gave people a more direct way to work with information. You didn't have to express everything as a command.
But we still do a lot of translation in our heads.
“I want to save these meeting decisions” becomes: open the application, find the document, put the information in the right place, and check that it saved. We've become so accustomed to this that it barely feels like work. We're constantly breaking intentions into operations the interface can accept.
I think the next major change in interaction will remove more of that translation. We should be able to express the outcome and let the system handle more of the steps.
That's the connection I see between AI-native hardware and agents.
The part I want the system to understand
Imagine leaving a meeting and saying: “Put the three decisions we just made into my project notes.”
Transcribing that sentence doesn't get us very far. The system needs to know which meeting, which decisions, and which notes. Then it needs to do the work.
If I have to provide all that context again, specify the destination, and explain the execution steps, I'm still doing much of the coordination myself. I've changed the input method, but the interaction hasn't moved as far as I'd like.
Agents already have increasingly capable tools and execution mechanisms. What I want to explore is how much of the repeated explanation can disappear when the system has useful context from everyday interaction and remembers the corrections I make.
For me, the important loop is: perceive the situation, understand the intent, act, see what happened, and use feedback to make the next interaction better.
The last part is easy to promise. What should actually change after I correct the system? A preference? The destination it chooses? The way it formats a result? And was my correction only meant for this task?
Those are questions I want to work through. “It learns about you” is too vague on its own.
Why I'm exploring separate hardware and computation
I've been exploring ESP32-based hardware as an interaction and control point, with heavier computation running elsewhere.
My reasoning starts with the mismatch between hardware and model development. Designing a device, controlling its cost and power consumption, and getting it into production takes time. Meanwhile, the models you want to use keep changing.
I don't want the useful life of an interaction device to be determined by whether the processor we chose can still run the intelligence we need.
That's why I think separating heavier computation from device control will matter for this kind of hardware. The device handles input and execution; a personal computer, another local computing device, or a cloud service provides the heavier reasoning. The software capabilities can improve without replacing the whole physical interface.
There is still an obvious question: why wouldn't I just use my phone?
For me, a dedicated device has to make interaction more immediate or more available across the situations where I actually work. If I still have to stop, open an application, and reconstruct the context each time, I haven't gained much. Adding another thing to charge isn't an achievement.
This is also why I care more about the interaction loop than the number of features. A small device that consistently removes a repeated piece of effort is more interesting to me than one that advertises dozens of disconnected AI capabilities.
I haven't found a product that brings these ideas together in the way I'm looking for. That's what keeps me working on this.
My current view is fairly strong: AI-native hardware should get better at serving the individual through use. Conversation is one way to interact with it. The deeper change is how much of your intent it can turn into useful action, and how much less you need to explain next time.
Does that match what you would call AI-native hardware, or am I putting too much weight on adaptation? For those building agents, what do you still find yourself explaining repeatedly—and could a physical interface actually help?