The reason why AR glasses are not a thing yes is because there isn't a big enough battery to allow them to function for more than a few minutes.
Glasses form factor have space for about .9watt hours now, and ~2 in 4 years time (assuming current trends) Assuming a 14 hour day, that means that your have 140mwhr to spend every hour. A not very bright light on your glasses is about 30mw, a decently bright one is 90mw. Processing imagery on that kind of budget requires custom silicon, and a huge bunch of optimisations.
I had Claude design an entire 4 layer rp2040 based PCB from scratch and PCBWay build it. It worked on the first go, other than some silkscreen overlapped, which doesn't hurt anything. That was before Fable.
Then I had it design a case for the new pcb to 3d print. Also worked the first go, but with minor cosmetic issues.
People have yet to even BEGIN to appreciate what these things can do with the right harness.
For the most people, the risks outweigh the desire for tinkering. Personalization will grow right at the vendor offering, not in the hands of customer. People don't even have the time to cook their own recipes. People have their own chores to worry about. I'm talking about bulk of the customer base, not the geeks.
There's a whole continuum from "Buy an off the shelf unit" to "here's a barebones case you can slide ready made switches and caps into" to "mix and match custom PCBs and cases" to designing your own PCBs and/or cases. There are pretty clear pipelines and even some levels of tooling for "draw up the layout you want and get a bunch of files you can send to production houses"
Takeaway 1: A lot of this is grounded in economic realities. I did the full bespoke route (custom PCB, custom 3-D printed case) and figured it probably cost me about $500 all inclusive to get what I wanted, and that's honestly a lot of money for a keyboard.
AI won't solve any of the economic problems. They can't fix "the minimum PCB order is N units, so now you have a drawer full of spares you paid for". They can't make the expensive part you needed cheaper, especially if you're an individual buying quantity of 1/5/10 instead of an OEM buying reels and containers-full. They can't change the fact that a case for a large widget will be expensive to mill/3-D print/mould/etc.
Takeaway 2: Customers may have surprisingly limited imagination for bespoke gear. There are galleries (and even coffee-table books) full of exotic keyboards. But Micro Center is full of $50 interchangeable "tenkeyless with RGB lighting" boards; throwing on a random set of "custom" keycaps, and that's enough for a large part of the audience.
Will these customers want or benefit from more tools, or will it just give them rope to hang themselves on and give them an excuse to bail out of the purchase entirely? Even if you can provide them a gallery of vetted turnkey choices, there might be more choice paralysis than actual benefit.
Takeaway 3: Hardware is forever (relative to software). You have a lot of small firms and group-buy products that disappeared and now the owners can't get an exact replacement or repairs. Conversely, Unicomp can gut and rebuild a 1986 Model M with new innards in large part because they've been selling the same basic design since a 386DX/16 cost as much as a Toyota Tercel.
If your AI spawns a galaxy of 1-of-1 bespoke products, who services and supports them? That seems like it's only going to appeal to the enthusiast-hacker type who can keep them alive themselves, who is least likely to need AI help designing them. Design for disposability isn't a great look for anything but incredibly low-cost, limited-usecase items.
If you are keeping inside the LEGO level of complexity, almost. But just as with code, if the project is complex you need a real engineer herding the cats. That said, it certainly can extend the reach of an effort, and is a huge help doing board reviews and data sheet analysis, etc. but the real engineering decisions are very very hit and miss, just like with code.
I had an esp32-box-3 lying around from a lapsed "voice agent" project from a year or two ago. Had a baby. Baby moved to another room, sleep trained. Baby either: 1. wakes up a few times a night, babbles for a bit, goes back to sleep OR 2. baby wakes up and fusses for N (=10) minutes, at which point parents need to go in and settle (that's the sleep training routine we use).
In either case, we do NOT want to wake up every time the baby does. Baby can go back to sleep easily, we adults have a harder time. A few rounds with Claude and the esp32 is now our new baby monitor. It tracks cry/fuss duration and publishes an audio stream (via a web UI or direct with, say, VLC). The audio only comes through AFTER N minutes of fussing have elapsed. It also posts notifications (to ntfy) after 30s and N minutes. My log says baby often wakes up 1-2 times a night and resettles almost immediately. We only wake up if the audio comes through, after N (10) minutes.
Also during the day it's really handy to be notified when baby has woken up from her nap. Let's us be out of the house, or in a distant room, and still keep track of what's going on.
It's fun to keep improving and adding features to this. Never would have had the time/energy to get this done without a coding agent. I ordered a set of 10 more of the esp32-box-3s to give them out to my friends (well, some are for other projects... so much potential).
(EDIT: Yes, I know this isn't AI designing hardware, but even writing code for embedded off the shelf stuff feels like a huge new potential.)
So they put a web browser in the device?
With hardware you get extra safety risks of fires and shocks, so let's see
Producing PCBs (say, 5 or 10 units) is pretty expensive, and components are also costly on such a small scale. Combining these two requires additional money or time. Beyond that, you need to consider that you probably won't get it right the first time, and every attempt multiplies the cost.
It'll be a deal-breaker for many people — the risk is just too high.
You're lucky if you're in a region where these open-hardware companies sell their wares, even though many of them will go under in the current market.
All the people that I know in tech and not in tech, don't do that, even if presented with the option they're too busy to also get into this endeavour that still requires a lot of expertise. I stopped reading there
It's not that I don't like your point of view. It's that I can't stand AI slop.
By the way, this is not new either. In the 1990s Microsoft tried to convince people how great it is if their fridge gives data to MS so MS can order needed food etc..
Fast forward some decades - many don't want to yield any more data to private entities, no matter which alleged "benefit" this would bring.
I tried building a health device few years ago and got completely lost in how to setup camera and touch display with a raspberry PI. Would imagine, with AI running in a command line, it would be much easier.