r/hwstartups • • Apr 06 '26

I make headphones, and many people want to buy them. But mass producing them doesn’t seem possible.

Thumbnail
gallery
2.3k Upvotes

r/hwstartups • • Sep 17 '26

I let a crane robot clean my room now

1.8k Upvotes

I'm the creator of Stringman and I've spent the past few months refining a room scale CDPR for picking up laundry and toys. The allure of putting a crane on the ceiling is that there's nothing up there to get in the way (and the floor might be too messy for wheels) but also that it keeps costs down since you can use fewer and smaller actuators to get the same work done.

The aim is just to save some time in homes with kids since we spend so much time cleaning up the floor. I leave these on in four rooms in my house, and I'd guess it saves me about 30 minutes per day.

Of course, it's not complete, and the video above only shows one run, which didn't flawlessly clean the room, but the hardware is fairly stable. I think robotics demos should be honest and show progress exactly as it happens. I'm sure I can make it work better than this, especially with more diverse data.

I'm always looking for people interested in testing this out in their own room, so if that interests you, please let me know.

thanks reddit.


r/hwstartups • • Jul 23 '26 Bravo

After shipping 30+ hardware products, these are the lessons I wish someone had taught me earlier

Post image
583 Upvotes

Over the past six years, I've had the opportunity to help ship more than 30 embedded hardware products to customers across 10 countries.

Looking back, these are the lessons I wish someone had taught me before I started. If you're building a hardware startup looking to scale, I genuinely hope they save you some time, money, and headaches.

Most books and tutorials teach you how to make a prototype work.

Very few teach you how to make it survive manufacturing, deployment, maintenance, and scaling.

Here are the 10 lessons I'd urge you to remember before you start scaling:

  1. A working lab prototype means nothing:

A device that works perfectly on your bench can still fail the moment it reaches a customer's environment. Field conditions expose problems you never see during development. Never scale before field testing.

2. Procurement can kill a product faster than bad engineering:

I've seen projects delayed more by component shortages, long lead times, and sourcing issues than by firmware bugs. Keep track of inventory and end of life of chips before you fulfill that bulk order.

3. Design for manufacturing from Day 1:

If your product isn't easy to assemble, test, and calibrate repeatedly, scaling production becomes painful. Invest in testing jigs, quality control and plan your setup in advance.

4. Design for maintenance, not just deployment:

Think about how someone will replace a battery, recalibrate a sensor, or swap a failed module two years from now. Be transparent about what is replaceable and what will be not.

5. Your support team shouldn't need an embedded engineer for every issue:

Build diagnostics, logs, and simple troubleshooting tools so technicians can solve most problems themselves. If you keep sending your engineers to field for petty issues, you'll run out of cash.

6. Calculate the lifetime cost, not just the BOM:

Maintenance visits, recalibration, batteries, SIM/data charges, cloud services, subscriptions, and support often cost more than people expect. Make sure you educate your customers about those beforehand.

7. Add safety features even if no one asks for them:

Thermal protection, watchdogs, reverse polarity protection, proper fusing etc should be in your design. The customers may have not asked for them, but they'll definitely hold you accountable when things go wrong.

8. Always buy more components than you think you'll need:

Some parts arrive faulty. Some get damaged during assembly. Others fail for reasons nobody can explain. That's just hardware. Maintain your local inventory, don't be dependent fully on vendors.

9. Remote teams are fine, but hardware needs regular face-to-face collaboration:

Hardware and firmware engineers should meet in person regularly. A single misunderstanding between the two can easily cost weeks or months. So even when you hire remote teams, make sure they are not distributed.

10. Leave plenty of margin in your BOM:

Component prices, freight, customs, and geopolitical events can change overnight. If your pricing has no buffer, your profit disappears first. Make sure you add a certain miscellaneous cost.

That just barely scratches the surface. Every project teaches you something new and the list could go on.

I'd genuinely like to hear from others building hardware products.

What's one lesson you learned the hard way that you'd want every first-time hardware founder to know?


r/hwstartups • • Aug 20 '26

Doing things that don't scale

444 Upvotes

I'll file this one under doing things that don't scale.

I'm doing small batches of my product myself. And each step adds time. I keep telling myself this is temporary until I automate this.

This is the smallest USB-C device ever made btw (yes smaller than Yubikey Nano 5c)


r/hwstartups • • Sep 17 '26

A hardware startup for hardware startups: we built the PCB Prototyping Machine we wanted for ourselves

Thumbnail
gallery
424 Upvotes

Hey r/hwstartups,

I’m one of the founders of PewCB. This isn’t my first hardware company: I’ve spent about 16 years leading hardware development, and rapid prototyping has always been a big part of the job.

We originally built PewCB One based on our own needs. Once we started using it, it genuinely changed the way I prototype electronics.

The closest comparison I can make is getting your first 3D printer. You have an idea in the morning, design the board, make it, assemble it, and test it. By the end of the day, you know whether the idea works.

That’s why we decided to turn it into a product.

So, what is PewCB One?

It’s a desktop machine for rapid electronics prototyping. It uses a laser to selectively remove copper and solder mask from special ceramic PCB blanks. A typical board takes about 10 minutes to process.

Fabricating the PCB was only half the problem we wanted to solve. Assembly had to be fast too, so we developed a somewhat unusual stencil process.

Once the PCB is finished, you wrap a thin tin stencil sheet around it and put it back into the machine. The laser cuts the solder-paste apertures directly over the finished PCB. There’s no separate alignment step because the stencil is made in place, on the board it belongs to.

As the apertures are cut, some tin transfers onto the exposed copper pads, effectively tinning them at the same time.

From there, the workflow is:

apply paste → peel off the stencil → place components → reflow on a small USB hot plate

For the boards I make at work, fabrication takes roughly 10 minutes. Assembly and reflow take another 20 or so, depending on the component count.

A few other details that mattered to us:

Fine-pitch components are practical.

The machine is precise enough for modern components, not just large DIPs and SOICs. We use down to 0201 passives, fine-pitch QFNs, etc.

The trace width/clearances are 75um (3 mil) - and it is a reliable and repeatable capability with a good margin (actual technical limit is 25 um, or 1 mil). The important part for me is that I don’t have to redesign a circuit around “prototype-friendly” components just because I want the PCB today.

The blanks come with solder mask pre-applied.

The laser selectively removes the solder mask to form the pads, so the traces remain protected and solder flow stays controlled. You’re not working with a completely bare copper board.

We can make double-sided boards with vias.

In addition to the standard prototyping technique of using small rivets, we offer a different approach: prefabricated vias. Our blanks come with a grid of plated vias made at the factory, making the process much faster than adding vias manually. It’s the preferred method we use for prototypes in-house.

We also publish project templates for these blanks on our GitHub, which makes it easy to get started.

The laser can cut the ceramic substrate too.

Holes don’t have to be round or mechanically drilled; you can create arbitrary cutouts and board outlines.

I especially like V-scoring the board instead of cutting it through completely. The blank keeps the standard shape, that makes it easier to apply paste and place components. After reflow, you simply snap the board along the scored lines.

And yes, it really is a desktop machine.

We have PewCB machines living right on our developers' desks. They don’t require external ventilation, compressed air, vacuum, or any other supporting infrastructure.

The machine is enclosed and uses closed-loop internal filtration for fumes and particulates. No copper dust, no odors in the room.

One important caveat: our product isn’t meant to replace a PCB factory.

For production boards, of-course we use PCB factories. We’re not trying to compete with JLCPCB or PCBWay on price per board; they’re extremely good at what they do.

PewCB One solves a different problem.

During R&D, what matters isn't the PCB price, it’s the cost of interruption:

  • I want to test a power stage or a new sensor.

  • I need an adapter for an FPC display connector.

  • I want to try new tiny SMD LEDs in my prototype.

  • I need a one-off test jig.

  • When an idea strikes me while I'm sipping my morning coffee, I want to be able to test it immediately, while the inspiration is still fresh.

That’s who we built PewCB for: hardware startups and engineering teams doing real electronics R&D, where iteration speed really matters.

We’ve started sharing examples from our day-to-day engineering work, along with some less practical experiments, in our Reddit community and on Discord.

If you work in electronics, feel free to ask me anything about the process: limitations, blanks, vias, accuracy, assembly workflow, or anything else.

I’m happy to answer the uncomfortable questions too :)


r/hwstartups • • Sep 15 '25

I invented a timelapse camera for houseplants and brought it to market

407 Upvotes

This is my biggest project so far. Today is September 15, 2025, and I first started tinkering with the idea back in November 2024. I got serious about it around February 2025.

I’m incredibly proud of what I’ve built. It’s a complex piece of work, and it took countless late nights. I had to bring together so many different technologies and skills I’ve taught myself over the years. I’m 28 now, and when I was 18, I made the decision that I didn’t want to wake up at 30 full of regret. The pain of discipline or the pain of regret. Consume less, produce more.

The idea came after I started my first job as a software engineer and moved into my first apartment with big, bright windows. For the first time, I could actually have houseplants, something I’d wanted for years. Around the same time, I picked up two new hobbies: 3D printing and electronics. Those, combined with my software background, made this project possible.

I made everything myself except the electronic module (ESP32-CAM, which I buy). Everything else, I built from scratch in just a few months:

  • Designed and 3D printed the case

  • Built the app

  • Set up the backend server with user management, authentication, image processing, video generation, AI models for enhancement & interpolation, order management, password resets, device management

  • Programmed the ESP32 logic

  • Built the shop website (no Shopify)

  • Created and managed social media accounts to find customers

My product has been live for about 4 months now, and I’ve made double-digit sales. Not a lot yet, but I’m confident I can grow this with better marketing. I’m more of a maker than a marketer, so this part is challenging for me. You can check out my videos on Instagram @ plantcam.io

Starting today, I’m committing to posting one video every single day. The product is stable and delivers great results my main issue is that I’ll run out of money soon if sales don’t pick up. But honestly, I’m happy and proud of what I’ve built.

I’d love to hear feedback. Please keep it constructive. I’ve had plenty of positive reactions, but there are always a few people who just throw negativity around. Otherwise, I’m happy to answer questions.


r/hwstartups • • Oct 23 '25

I developed a dual-screen, ESP32-powered ereader

Thumbnail
gallery
383 Upvotes

Some time ago, my old Kobo ereader broke, which led me to look for a new one. I’ve become increasingly interested in open and repairable hardware, such as the Framework laptop and Fairphone, but have been disappointed by the lack of an ereader equivalent. Additionally, I wasn't satisfied with the design of most ereaders: they typically have a single screen and require some form of case to protect them from damage (Something I didn't have for my Kobo, which explains why it broke ;) ).

I just finished my engineering studies last summer, so I decided to take the leap and see if I could create something that solves these two problems. And now, after a few months of development, I’m excited to announce that the Diptyx E-reader is entering its pre-campaign stage on Crowd Supply!

To summarize the product: The Diptyx ereader is a dual-screen ereader that runs on an ESP32 and will be made open-source when the crowdfunding campaign has finished. It runs custom software capable of displaying EPUB files and uses two e-ink screens for a book-like reading experience. Through the built-in UI, you can scroll through chapters, add bookmarks, change the font type and size, and much more.

When traveling, you can simply fold it closed, protecting the screens and making the device highly portable. But most importantly, the Diptyx uses no DRM and requires no accounts or cloud services, meaning you fully own the device and everything on it!

I designed the hardware all myself, including the electronics and plastic case. The drawings on the outer panels are old ex-libris artworks (a sort of ownership-stamp in books). The software is partially based on prior open-source work, but mostly custom.

For future versions, I'm excited to try different types of artworks on the pcbs (using different silkscreen colors, plating types, etc), and to try different color schemes overall

I'd love to hear your feedback or questions, and if you're interested you can read more about it on the crowdsupply page: https://www.crowdsupply.com/diptyx/diptyx-e-reader


r/hwstartups • • Apr 03 '26

Advice making a hwstartup ( eink watch)

Thumbnail
gallery
318 Upvotes

Hi, i posted my Diy eink watch on r/watches And was blown away by the enthusiasm. I have just been making this as a hobby but it seems there is real appetite to turn this into a product.

So far ive spent about $1500 dollars of my own money developing this including custom pcbs and parts for about 5 watches. I think there are still a few ruggedness issues I want to sort out and can imagine spending approx $800 -1200 on new board rounds and other development to get to the next stage. Ive opensourced this version but the next planned version fixes lots and leaves it in the dust.

Questions:

-how do hw startups usually fund their initial prototypes?

-do you think this is a viable product?

-are incubators worth it?

-any other advice?

Im based in Tasmania, Australia if that is needed for context.

https://www.reddit.com/r/Watches/comments/1saalnq/diy_watch_i_made_an_opensource_eink_smartwatch/

Want to know more? Read the instuctables article

https://www.instructables.com/Building-a-Lightweight-Curved-EInk-Smartwatch/


r/hwstartups • • 12d ago

My animal deterrent turret! Iron dome for your backyard

289 Upvotes

Wip, still developing it. Yesterday I posted about a pcb I made - it’s inside of this bad boy!!! Quit my job to make it a reality. Can’t wait for users to try it out once the beta uint survive more than a week outside I will be confident to start giving to people :)


r/hwstartups • • May 20 '26

I made a device that automatically mutes TV ads. Would love some feedback.

257 Upvotes

Hey everyone, over the past few months I've been working on a device that will automatically detect and mute TV commercials.

I started this project after growing frustrated with the sheer number and repetition of TV commercials particularly on streaming services. I started manually muting commercials when they came on, but for those of you who also do that know, it can get annoying to keep on top of. I realize I could pay for "ad-free" streaming tiers but with a lot of the services you still get served ads and the costs of those tiers are getting pretty pricey nowadays (especially if you have multiple streaming services). Plus ads on cable or other non-streaming platforms still exist, so it doesn't totally solve the problem. So I set out to build something that would silence commercials regardless of the platform without having to manually mute.

The device I've built analyzes real-time outbound audio data from TVs to detect ads, and then modulates the downstream audio depending on the detection state. This modulation could be muting, turning down the volume, or perhaps splicing in your own audio content. For now, it just mutes, but those other options would be pretty trivial to put together. The hardware involved in this project is pretty straightforward and currently uses off-the-shelf components since I'm still in the testing/demonstration phase. Right now it can accept audio from an aux, RCA, or optical source and the outbound audio is played through an aux. The bulk of the technical complexity and challenge is on the software side. So far I'm able to pretty reliably detect ads, but it's still fairly buggy and a little ways off from being ready to fully share with the public.

One thing to note, however, this project/architecture requires the use of external speakers. Since the audio analysis and modulation has to happen after exiting the TV (due to the HDCP encryption used to protect content and DMCA 1201) this project isn't able to mute commercials on the TV speakers themselves.

Before I spend even more time and effort to get this project to the point of a product, I thought I should reach out to relevant communities and get thoughts/feedback from folks to see if other people care about this problem or if this is something that just uniquely bothers me.

So I would love to hear what people's thoughts are on the project. Really what I'm trying to figure out is:

  • Are you bothered by TV ads enough to want to use/pay for a device like this?

  • Would you prefer a soundbar/speaker system with this tech built in, or an inline device that would allow any speakers to be used?

If you'd like to answer these questions in a survey format so I can analyze the responses a bit easier, here's a link: https://forms.gle/Mzr9YPAfu3rkNnw96. It's just the same questions as above so shouldn't take more than a minute.

Please let me know what questions, concerns, feedback, or input you might have. Thanks!


r/hwstartups • • Oct 08 '26

How we prototyped our prototyping machine with help of the prototype of that prototyping machine.

212 Upvotes

Hi everyone! We're developing PewCB, a PCB prototyping machine. The project grew out of our own need to prototype electronics quickly. As soon as we had an early prototype that could make PCBs, we started using it to develop the machine itself.

Here is a story on how we developed one interesting function of PewCB. The machine has a sliding tray on the front, which is used to load PCB blanks. It is actuated by a stepper motor and a lead screw. When the tray is fully closed, we need to apply a specific force to lock it against its stops. We use a spring-loaded nut for this. Once the tray reaches the fully closed position, the motor makes a few extra revolutions, compressing the springs and providing the force needed to hold it against the stops.

To measure deflection, we devised a position sensor made up of a digital magnetometer and three magnets with alternating polarity. When we move the sensor along the magnets, the magnetic vector rotates almost proportionally to the displacement. The sensor picks up even small changes in position with very low latency, so the system can respond quickly to changes in force.

This force sensor also has another use: detecting obstructions. If something gets in the way as the tray is opening or closing, the controller detects it immediately and stops the tray or reverses the movement. Also the entire tray acts as one big button. Instead of aiming at the eject icon on the screen, you can simply push the tray to close it.

By the time we had started developing this subsystem, the key parts of the machine were already working, and we could make boards with it. We prototyped the assembly using 3D printing for the mechanical parts and PewCB for the electronics. We needed to check whether we'd chosen the correct magnetometer sensitivity and magnet size, what signal-to-noise ratio we'd get from the sensor, and whether external interference would have a noticeable effect on the measurements.

The whole process took a few days, but it allowed us to build a production version of the assembly, with an aluminum tray frame and a brass nut, in a single iteration. We got to experience the pure joy of engineering and we wish you feel the same way about your own prototyping endeavors!

For more info about the machine join our Discord or visit our website pewcb.com


r/hwstartups • • 14d ago

I’m open-sourcing my modular macropad

204 Upvotes

So after 1 year working on this modular macropad part-time, I decided to change direction and make it open source. A lot of people told me it’s not that valuable unless it’s completely editable, and honestly I get it.

So I rebuilt it to be easy to assemble with just screws, and the modules can be redesigned in KiCad or Altium, so anyone can have their own layout.

Now that a lot of people are using Claude Code and Codex, macropads kind of found a new use, so I’m really curious what layouts people will make. I’d rather do this and have people really own their hardware.

Would you actually build one yourself or would you rather get one ready made?

More info: keemate.com


r/hwstartups • • Sep 03 '26 Helpful Bravo

Why we abandoned E Ink for a segmented LCD after designing our product around it

165 Upvotes

Disclaimer: I'm one of the people behind Airgeek, a soon-to-be-open-source air quality monitor. We are currently launching it on Kickstarter. I'm posting here because I thought the display-development story might be interesting to the community here. Ask me anything :)

Introduction

Hi Reddit,

In 2023 we started work on what would become a serious open-source air quality monitor (currently on Kickstarter). I am responsible for the hardware design, including the display panel.

We started with an E Ink panel but eventually moved to a "legacy" segmented LCD. I think it might be interesting for the community to hear why we switched (it's the question we get the most often) and where the advantages and disadvantages of E Ink are, compared to a custom segmented LCD. I also wanted to document the path in case anybody else wants to follow (and avoid the many, many potholes).

First prototype (E Ink, 2023)

So this was the very first prototype of what would later become Airgeek. We used a 1.54" E Ink panel made by Waveshare. We got a pretty decent volume price on that panel. We were driving it (in the hardware sense) with our own custom driver based on the reference schematics from the manufacturer of the on-board IC. For code, we were using a clean rewrite of the Waveshare driver (in the software sense).

I really liked the look and feel of the panel, but it had a few problems. Some of those were obvious from the beginning, some surprised us:

  • First of all, the panel was tiny (duh). It's not a problem when you place the device up close. But for our project specifically, we realized you don't want to place the device up close, because that affects the readings. Or to put it another way: the size of the display shouldn't severely limit your placement options, which the E Ink did. But I could probably live with that; there are many commercial devices which suffer from this exact issue.

  • The second problem was, perhaps surprisingly, power consumption. Refreshing the E Ink is not actually that cheap: at 3.3V, we're talking milliamps over seconds (IIRC, it's been a while). Normally the cost of redraw amortizes pretty well since the content stays on for a long time, but we're making updates every 5 minutes (and we might want to go as low as 30 seconds in some cases). And that's just the panel: you still need to optimize the driver circuit (which uses a charge pump to increase the voltage), and unfortunately my analog skills back in the day weren't up to the challenge. (And I would probably still struggle a bit today.)

  • But the real deal-breaker was the full refresh cycles. Every now and then, we would need to do a full refresh cycle (a transition to all black, followed by a transition to all white) to keep the display healthy. Each time that happened, if I had it in the line of sight, the device would interrupt my train of thought - basically it was an unintentional pomodoro timer :). I know there are big differences between the manufacturers and some panels would probably tolerate less frequent full refresh cycles and they would be faster. That would only partly solve the problem though.

And a complicating issue was the integration of BMV080. This is a laser-based particulate matter (PM) sensor that measures particulates in the freely flowing air, i.e. it doesn't have a fan. You need a clean optical interface between the sensor and the environment, and normally that is very thin glass. The datasheet constrains the thickness of the glass and its various optical properties, severely limiting your choice. Gorilla Glass was a readily-available product that ticked all the boxes, so we wanted to go with that.

Ynvisible side quest (2024/2025)

It was around this time that I found Ynvisible. If you don't know them, they make extremely cool thin film displays. We still weren't sure what the enclosure was going to look like, and so we liked the (literal) flexibility. We entered into talks with them, and realized this isn't going to fly.

Ynvisible requires a fair gap between segments. That's perfectly viable for loads of applications, but it wasn't compatible with what we needed. We did one design iteration with them and abandoned it.

But I still think what they do is massively cool.

The E Ink had a massive advantage: it's a matrix display, and you can craft beautiful, crisp fonts and pictures with it. If we were to give that up and go with a segmented display, I wanted it to at least be sleek. I saw a watch LCD made by em microelectronic at embedded world, and I wanted that level of ridiculous segment spacing. You can barely tell this is an LCD because the telltale gaps between segments aren't there.

The first generation LCD (2024)

After that didn't work, I started hunting for a manufacturer willing to build a display panel with such an unusually low segment spacing.

I approached em microelectronic (who make the watch display) several times, but their sales representative ghosted us. They would promise to get back and they never would, and when I reminded them they wouldn't bother to reply at all. That was seriously uncool.

Unfortunately, Europe and the USA basically gave up on (segmented) LCD manufacturing. We invented the technology, perfected it and then decided it was too low-tech to bother, and outsourced all manufacturing to Asia. As a result, the vast majority of manufacturers are based in China, and we couldn't find a European partner. Don't be fooled, there are many American companies which "pose" as LCD manufacturers, but only provide consulting on top of overseas manufacturing.

Eventually we found a company that would meet the challenge, Royal Display. It was my first-ever experience dealing with a Chinese ODM. The experience was basically the opposite of em microelectronic. They work fast and they actually care.

That being said, we were in the early days and things were still just taking shape. So we designed this very conventional LCD with them (the graphic design is mine, the engineering is theirs):

The contrast on that panel is pretty epic. You can confidently read this in any light, from virtually any angle, and at distance. Technically, the panel is backlit, but we ditched the backlight eventually. The power consumption of the LEDs is too high, even if you just turn it on briefly. Perhaps we can fix this in Airgeek A2 :)

Here are some pictures of the panels taken at a larger distance, and at angles:

Side quest: Gorilla Glass (early 2025)

So this was a fun one... Remember the BMV080 and its optical interface? Gorilla Glass was a natural choice, and so we wanted to use that and cover the entire front of the device (the panel, and the sensor) with a single piece of glass to get a nice, clean look. But we made the mistake of sourcing the glass and the display separately, leading to lots and lots of pain down the line.

We had an electronics fair coming up soon (embedded world 25) and so we were in a hurry to finish the next-gen enclosure. But Gorilla Glass processing is done in China, too, and we couldn't find a company, local or not, that would guarantee delivery of the glass in time. So we decided to cut it ourselves - what a brilliant idea that was. We bought some Gorilla Glass iPad display protectors and asked a local water jet cutting company to carry out the actual cutting. I bought four types of protectors, brought them over, and collected the shattered glass the next day...

Turns out they had never worked with glass this thin and "had no idea what was wrong." I bought some more and asked them to allow me to witness the machine in operation. After a few more destructive passes, it was obvious that the jet would vibrate the thin glass sheets so violently they would shatter against the steel bed of the machine. So I bought _even more_ protectors and glued them to some scrap glass with a heavy-duty double-sided tape, and voila, that worked! - somewhat, anyway:

The abrasive they were using clearly was too large, resulting in fuzzy edges and extremely shatter-prone cut-outs, since there were about a bazillion sites where cracks could form around the perimeter.

We then tried applying lacquer to the glass anyway, in a last-ditch effort to salvage what we could. Unfortunately, the glass is treated with hydrophobic coating which we were unable to remove. Certainly not mechanically, since the panel would just crack; I tried applying all the solvents I could (legally) use, but to no avail.

All in all, this was a desperate attempt at having a backup plan in place and I'm not particularly proud of this!

In the end, a Chinese supplier did ship the panels two hours before we left for the fair, and we were incredibly relieved:

A misunderstanding, and the second generation LCD (mid 2025)

The feedback from embedded world was encouraging and people did like the overall design. But it was clear the device didn't have the "premium" look and feel we were after. Somebody told me (jokingly) that the device looked like a miniature television from the 1980s, and I just couldn't unsee it. It was clear we needed to do better.

It was around this time that I started thinking about inverting the LCD: making the front side normally black, with the active segments white - that would give us a clean, uniform look. But it turns out that's not as easy as "flipping the colors."

To see what the device would look like, I peeled off the front polarizer from the original LCD and turned it 90 degrees:

Our ODM offered to build an inverted panel at no additional cost. They shipped it in a few weeks and it was absolutely stunning:

There's one minor issue, mind you: this isn't a reflective panel. This is a VA panel, and it _must_ be backlit from behind. And sure enough, the contrast is just epic, but it's not exactly compatible with our incredibly constrained power budget.

Now I have to admit, I didn't know immediately what the problem was. You can actually see the segments without backlight, but they are incredibly faint - so I thought I must be driving the display wrong, because it was using a different waveform. It took a while to clear up the confusion - the engineers kept telling me I should enable the backlight; I tried to explain I want to run the panel without backlight. Eventually we realized a mistake was made, and this panel could never have worked to begin with. Too bad, because it looked amazing. We took some great pictures of the device with the VA panel (with backlight on) and built the first website around them, but otherwise it was a complete flop. And we made it our goal to approach the looks of the VA panel, but in a reflective configuration.

We decided to build an inverted STN panel instead, and - crucially - to have it optically bonded to the Gorilla Glass by our ODM. This is one of the game-changers: they use a glue which has similar optical properties to the cover glass and the display components, so you get very few internal reflections which reduce the (perceived) contrast - the result is a "brighter" display.

Third generation LCD (early 2026)

But I still wasn't happy with the result. Compared to the E Ink or the first LCD, the contrast of this panel and the viewing angles were quite poor - after all, it was an STN panel.

This was when I realized that the various Western companies offering to do the R&D for you do actually add value: they know the technology and the manufacturers and their capabilities, so they can help you get there quickly - but at several times the cost, and we couldn't afford that. I sort of felt I owed them an apology for writing them off as useless middlemen though.

I decided to get to the bottom of the problem. I felt that my goodwill with the ODM was running out - after all, I've been constantly changing what we were trying to build - and we only had one more shot at doing this right. I came up with a load of proposals - stuff we could try to make it better - and I just sent that over.

A hard-earned lesson: a picture is worth a thousand words. Before, I tried to explain what I was trying to do in English; around this time, I started sending pictures. The language barrier is real; the salespeople speak English really well, but the engineers designing the panels often don't. I guess a lot is lost in translation to Chinese, but the pictures often make it to the engineers unmodified.

In the end, our ODM designed an LCD with optically-bonded Gorilla Glass, with an anti-glare foil on top. And if I understand correctly, this foil also plays the role of the external polarizer for the display, increasing the amount of light that makes it through the display stack. So you remove the vast majority of reflections, and you make the display brighter - and that is enough to kick this into high gear! (I will certainly try peeling the foil off, but I don't have enough panels to spare at the moment.)

Closing thoughts

Switching to LCD fixed all of the original problems:

  • The panel is really quite large: the digits are 45 mm tall. You can read this from across a small room just fine.

  • The power consumption, including the extremely low power driver in our microcontroller, is on the order of microamps (at 3.3 V drive).

  • The display doesn't suffer from periodic attention-grabbing full-refresh cycles.

LCDs come with some advantages:

  • The power consumption is constant and doesn't depend on how often you change the displayed values (but you need the MCU to run to drive the change, so there is some indirect power consumption).

  • Refreshes are much faster and feel smoother.

And obviously, they have some disadvantages:

  • The layout of a segmented LCD is fixed, whereas an E Ink display is completely software-defined. But in our particular case, LCD was the right choice, and I'm glad we went that route.

If you're curious what the finished device looks like after all of this, check out our Kickstarter page.

And if you're designing a custom LCD, feel free to ask me anything here. I've probably made the mistake already. :)


r/hwstartups • • Jul 12 '26

How to spend $140k on tooling and still have no product

Post image
162 Upvotes

The SF hardware founder pipeline, basically:

  • Have an idea

  • Duct-tape together a demo

  • Fly to Huaqiangbei to find a supplier

  • Meet a guy who says, “Yeah, we can make this”

  • Start working with him while still jet-lagged and running on blind optimism

  • Find out three months later that he does not actually own a factory

  • Your specs get passed around a bunch of WeChat groups, with every agency adding their cut

  • Somehow, an earphone factory ends up taking your smart ring or smart glasses project

  • They’ve never built a ring or a pair of smart glasses. They tell you custom molds are required.

  • Cool, there goes $140k

  • In the end, the factory you actually needed was probably in Dongguan, Foshan, or an industrial town you had never even heard of.

  • The earphone factory screws it up

  • You realize compliance, customs, duties, and shipping were never included

  • You cannot ship the product

The annoying part is that there is no clean database for any of this.Hardware pricing moves constantly. A tiny plastic part gets more expensive, capacity gets tight, or a bigger customer jumps ahead of you.

Suddenly the whole quote changes.

So yeah, my advice is pretty boring:

Treat sourcing like networking in SF.

Cold email everyone. Talk to ten suppliers, not one. Ask what they actually make in-house. Ask who owns the machines. Ask who made the sample.

“We can make it” is not useful information.

And do not underestimate the language barrier.Honestly, one good person inside the supply chain is probably worth more than another $100k thrown at the problem.


r/hwstartups • • Apr 22 '26

We made a modular gaming mouse! Just finished shipping all pre-orders

Thumbnail
gallery
156 Upvotes

We just finished shipping all our pre-orders and wanted to share our project. It started off as a hobby where I built custom gaming mouse and posted on my socials. It eventually ended up becoming a product because I wanted a modular mouse with Arduino attachments for extra inputs/outputs, while still keeping the same specs of a gaming mouse.

Some key points:

  • Shipped just over 220 units

  • Around 5 months of development for core features (mostly part-time)

  • Built on top of a ZephyrOS based framework we’ve used in medical/IoT projects

  • I handled hardware (PCB + 3D), parts of the firmware, and most of the web app

  • Firmware development was split with a coworker but he eventually took over most of it (thanks Josh!)

  • Designed with mass production in mind early (secure bootloader, test points, tester jig, and lot-based test tracking)

One thing I really underestimated was how hard it is to ship even 50 units, especially with multiple SKUs. For my full-time work, I’m usually focused on design and setting up systems for mass manufacturing, but I hadn’t gone through the full process end-to-end myself. I handled designing, building, testing, customer support, marketing, and fulfillment, and it ended up being significantly more work than expected, pushing the timeline back by almost 2 months...

Anyways, thanks for reading and I'd be happy to answer any questions you have! Just very very happy that we finished shipping all our pre-orders :)


r/hwstartups • • 28d ago

Making a Digital Gauge for Cars

Thumbnail
gallery
147 Upvotes

Hey guys. I have been designing and developing a digital gauge for cars for over a year now and i finally trust it enough to present it here and ask for feedback.

Its a 52mm gauge so it can fit universal into any standard aftermarket Analog gauge pod. I spend alot of time to support anything you throw at it given my capabilitys in electrical engineering and software development.

My biggest issue is that i have cars to test it on besides my own BMW E46. The E46 is great for testing CAN sniffing but it doesnt support any OBDII requests nor does it have any custom ECU like MaxxECU, Haltech or similar.

One of the key development thoughts was that i need to support any ECU or CAN network. Thats why the Gauge comes with preset profiles for aftermaket ECUs plus the possibility to make your very own profiles from scratch or via the dbc parser which is build in.

If you dont have a CAN bus thats also no issue at all. the Gauge has 8 Analog inputs supporting 0-5V sensors and NTC or PTC sensors up to 60k Ohms.

Now why am i writting here exactly? Honestly i find myself kind of lost in what to do at this point. I opened my shop start of october because i thought i would get some people to buy it and get me feedback (I even setup a 20% discount for early supporters). But its been 19 days now and hundrets of messages later i only found 2 buyers which feels kind of demotivating for me. I am ofcourse glad i got someone to support this project but it is not how i thought it would start out. The most difficult fact for me right now is that after i started i saw so many other people starting to build the same format Gauges which just makes my content go unseen due to my lack of video editing skills.

I am hoping that some people here would have some tips on what to do next or what to do better...


r/hwstartups • • Sep 29 '26

I regretted closing my old business in 2024 so I started a new one.

Thumbnail
gallery
141 Upvotes

I’ve been in and out of running a hardware business and previously ran a small hardware startup called Oak Development Technologies in a similar market to Adafruit and Sparkfun. I took an unexpected break in 2024 right as one of my boards was taking off and the regret of walking away really haunted me for a while because it didn’t need to happen.

So today I decided to formalize my company again, this time under a new name, Kavrous Technologies, as I wanted a fresh start. I’m not totally abandoning my past company though as I still have stuff I can build and sell for one segment while I work on what I really am pushing for.

One product I’m putting a bunch of time into right now is KeyBoy. KeyBoy started out as a toy for my kids because they were small and I thought it would be a fun gift. Today I’m turning it into a full fledged product while also maintaining my roots in the open hardware community. There is still a ton of work to do but it feels good to be back in the groove.


r/hwstartups • • May 03 '26

FCC votes to ban all Chinese labs from certifying electronics sold in the US due to national security concerns — ruling would affect 75 percent of US-bound devices

Thumbnail
tomshardware.com
141 Upvotes

r/hwstartups • • 14h ago

Building the programmable power supply I wish existed

Post image
140 Upvotes

Hey all, been a long-time lurker here, finally posting. I got so tired of the pile of wall warts and power strips for my music gear, I'm building a programmable power supply: 7 isolated DC channels with barrel jacks: configurable voltage, polarity, and max current settings. Also a four port USB hub, and a 100W USB-C charge port for a laptop or tablet. With all of it powered by a single USB-C power brick like you use for your laptop today.

I have a music solo act where I play live, and had some close calls with unplugged power bricks during soundchecks. I finally had it and started asking around on popular forums on how the heck other people solved this.

Most the answers I got was the same approach I already took, or a me-too-wish-this-existed response. So started designing it.

It's still in the early stages (thus the renders), but the first pass of the enclosure is designed. Have the main layout done. Now getting the first critical path board fabbed and shipped here in the next week.

Also trying something a little different with this product by designing it in the open, with weekly videos tracking how the product development is going, both the wins and the setbacks. It's kinda scary to develop like this as it's very vulnerable, but it's also awesome to share with others how our tiny team goes about building new products.

I'll aim to post here regularly with updates if there's interest. Otherwise we'll be posting updates on the blog at https://tonicaudio.com/blog and via YouTube: https://youtu.be/9xP5pFiPCFk

(Mods: if these links are against the rules, please let me know and I'll remove them. Def not trying to be spammy!)


r/hwstartups • • Sep 10 '26

My HW startup launched (and got funded) after working on it for 2 years!

139 Upvotes

EDIT: comparing the device to Pihole is simply not fair and an oversimplification of PuriFi. PuriFi is a whole-home security / privacy appliance that ideally goes inline with your network. DNS resolution is only a subsystem of our ecosystem and even that our device does much better than a device running Pihole as your DNS server which CANNOT intercept devices that have their own DNS or use DoH bypass. There is also nothing wrong with using a RPI board. Many successful companies started that way before moving on to their integrated devices.

We sent out units for review and this one is from Archin3t. I'd like to note that we do NOT use Pihole, we built our own DNS resolver.

Features that make it unique from a DIY device:

  • Relay assisted P2P private VPN

  • IP masking via egress

  • IP Firewall

  • Fleet Intelligence (Opt-In, anonymous data)

  • Mobile App

  • Live network monitor

  • Plug and play, no config

  • Auto updating blocklists

  • DoH Bypass prevention

  • One tap allowlisting from share screen

  • Text and email notifications

  • Commercial level customer support

Features that make it unique from existing vendors:

  • Price

  • The exact package we provide

  • Works with existing networking equipment

  • Recursive DNS

  • We don't need your data to protect you. We don't collect or process your activity. Everything runs on the device itself. Stats are ephemerally streamed to the app on demand

The device has plenty of other features such as:

  • Per device profiles

  • Content controls

  • Advanced security features

  • Automatic updates

  • Household sharing

To name a few. You can check out the full list of features on our Kickstarter Page

We are shipping two different batches. First batch is based on the RPI5 board so that we can get them to customers as cheap and fast as possible (by December, boards already stocked). Second batch will be our fully integrated device shipping by May.

I'm just really happy to have made it this far and even happier about the feedback we have been getting from our users. Everyone so far seems to love it, as well as their family.

Thank you for reading. I wish everyone else working on their projects good luck.


r/hwstartups • • 13d ago

My first-ever custom PCB. Designed from scratch. And somehow... everything works. First try. 🤯

133 Upvotes

I have to admit, I was pretty skeptical when I placed my first order with PCBWay.

There's something surreal about spending hours designing something in KiCad, rotating it around in a 3D viewer, and then holding the actual hardware in your hands.

But the real excitement came when I powered it up. Flashed my firmware. Established communication. Ran the entire test suite. Everything passed.

While building Sentry, my AI-powered animal deterrent system, I reached a point where my prototype had become a jungle of controllers, drivers, voltage converters, and wires.

Every new feature meant another component, another connection, another potential point of failure.

I always told myself that once the cost and complexity crossed a certain threshold, I'd design a custom board.

Well, I finally crossed it.

But I didn't just consolidate the electronics. I took the opportunity to add capabilities I had wanted for a while:

• Integrated power management and control circuitry.

• An IMU with a compass to help compensate for positioning drift.

• A dedicated MCU supervising the Raspberry Pi, including a watchdog that can automatically reboot the system if the Pi stops responding.

That last feature was especially important. When you're building autonomous hardware, the system needs to know how to recover when something goes wrong.

And here's the fun part.

I'm not an electrical engineer.

My academic background is in Information Systems and Business Analytics. I've just always been fascinated by engineering and understanding how things work.

With the help of Claude and Astra, I went from figuring out schematics and PCB layouts to designing, ordering, programming, and testing my own hardware.

And somehow, on my first attempt, the entire system works. Okay, technically there's still one button I haven't tested because it hasn't arrived yet. But at this point, I'll happily take the win. 😂

There's something incredibly rewarding about turning an idea into a physical, working system. One more discipline explored. One more engineering challenge tackled. One step closer to getting Sentry into the real world.

Back to building. 🔧

#HardwareEngineering #PCBDesign #Robotics #KiCad #GarageRobotics


r/hwstartups • • Aug 24 '26

We built a Lamp companion. The hardest part was teaching it when to shut up.

131 Upvotes

We make a desk robot called the Autonomous Lamp. 5 bus servos for the neck, a camera in the head, a mic array and an LED ring, all hanging off one small single-board computer. It's always on, always listening, meant to feel like a companion sitting next to you, not a device you operate.

But there was a problem. When it's always on, every sound in the room is a possible interaction. A coworker stops by your desk to talk and it joins in. I type on my blue switches and it joins in too. So instead of a companion you get something that talks over you all day.

Here is what we tried, what went wrong, and what we learned. Hope some of it is useful

Prototype 1. It answered everything

First prototype, I walked into the office, sat down at my desk, and before I opened my laptop, it spoke first.

Then all day. I talked to myself while reading code, it answered. I picked up my keys to leave, and it called after me into an empty room. A coworker a few meters away was talking about a project on the phone, it heard that and joined in too

It wasn't broken. It did exactly what we told it to do. What we told it to do was the wrong thing.

Living with someone doesn't mean talking the whole time

Prototype 2. "Hey Lamp"

So we did what everyone does. Say the name first, then talk.

"Hey Lamp, turn it down." "Hey Lamp, what time is it." "Hey Lamp, never mind."

Worked right away. No name, nothing wakes up. You can even put the name at the end, like "come on dance a bit, Lamp", and it still understands and still does it. That really works btw, not making it up. Our Repo is public, it's in the commit history if you want to check.

We thought we were done. Then a few days of living with it and something felt off.

You don't say "Hey Mom" every time you talk to her at dinner. This lamp is 40cm from my elbow and I was saying its name 30 times a day.

Hey Siri makes sense. The phone is in your pocket, the speaker is across the room, and neither has eyes. They really have no other way to know you are talking to them.

The Lamp has a camera and sits right beside me. We were copying a limit we don't have.

It worked. But once it worked, it was back to being a thing you operate, and it stopped feeling like the companion we set out to build.

Prototype 3. Turning toward it, which is where we are now

We argued about this for a while and kept coming back to one thing.

People don't have a button on their body. So the Lamp shouldn't either, not if it's meant to be a real companion.

For months we had been asking how to make it quieter. Every answer to that question made it feel less alive. Quieter and more alive were pulling against each other, and we kept trading one for the other.

The right question turned out to be a different one. How does a person know you are talking to them?

The answer is stupidly simple tbh. You look them in the eye and speak.

So that is what we built. If you want it to feel like a companion, you turn toward it and talk. Camera and mic together, the way two people actually do it. This is the part where having a body pays off. A smart speaker cannot do this. A thing with a camera in its head and servos in its neck can.

Two things make or break this:

  • People turn before they speak, never after. Checking the camera when the mic hears something is too late, the moment already passed. So the camera measures all the time into a 3 second buffer, and when you speak the system reads back through it. That buffer holds 4 numbers per sample, not video. A timestamp, the head angle, the face size, and how far off centre it was.

  • Presence is not the signal. Someone sits beside this thing all day, so seeing a person tells you nothing, and a face pointed at a monitor is still a face. What we measure is which way the head is pointed.

Then we fixed it too well.

Someone sat in front of it, looked right at it, asked it something. Nothing. Asked again. Nothing. He was sitting so close the camera cut off the top of his head, so the detector guessed where his eyes were and put them above the frame. That works out to 90 degrees. The log had him in profile 4 times in a row. Not the LinkedIn kind

The rule that fixed it: a measurement that cannot be made must not vote either way. Not measurable had been quietly counting as looking away. And there was a hardware half to the fix too. The same face box now feeds a small vertical re-aim of the neck servos, so when it frames you badly it corrects its own aim instead of blaming you for sitting wrong.

Chin resting on your hand needed its own work too. If you ever sit in front of one, try it

If you're building an always-on device and found another way to tell when someone is talking to it, I'd like to hear it. Happy to answer anything about the build. And if you read this far, ty


r/hwstartups • • Oct 06 '26 Bravo

[AMA] Ask Me Anything: 16 years of building smart hardware from concept to mass production in Shenzhen

127 Upvotes

Hey everyone, I’m Matt. I’m Taiwanese, I speak Mandarin natively, and I’ve been based in Shenzhen for many years.

I’ve spent the past 16 years working on consumer electronics and smart hardware products, from low-power wearable device and modules to smartwatches, smart rings, and other IoT devices.

My experience is mainly around taking a product from 0 to 1, not just working on one specific technology, but helping connect the whole process from concept and POC, to prototypes, supply chain, and eventually mass production.

Some of the areas I’ve worked on include:

* Hardware / PCBA architecture

* Embedded systems and MCU firmware

* Sensor integration and applications

* Wearable algorithms

* Bluetooth / Wi-Fi communication

* iOS / Android app integration

* AI model and cloud API integration

* EVT / DVT / PVT and mass production

* Manufacturing, supply chain, yield improvement and troubleshooting

Since I’ve been working in Shenzhen for a long time, I’ve also built up relationships with local suppliers and manufacturers , including ID / MD, mold makers, PCBA / SMT, assembly and testing companies.

I’m also familiar with different MCU, SoC and sensor vendors and their distributor networks. When choosing components, I usually look beyond just the specs and consider cost, availability, supply chain risk, and whether the part actually makes sense for mass production.

A few projects I’ve personally designed and worked on:

  1. Motion-sensing module that could fit inside a phone SIM card slot

Built around an STM32 MCU + 6DoF IMU for motion and posture analysis, including hardware, firmware and algorithm integration.

2. Smart fresh-air mask with PM2.5 monitoring

I worked on the sensor, MCU, fan control, Bluetooth and mobile app, allowing users to control the airflow and monitor PM2.5 levels from their phone.

3. Contactless elevator button

Used an IR LED + photodiode array to detect finger position and reduce false detections, creating a contactless interaction system.

4. VR Lighthouse tracking receiver

Worked on the receiver module used with a VR Lighthouse tracking system for spatial positioning, involving optical sensing and signal processing to determine the device’s position in 3D space.

Over the years, I’ve learned that getting a hardware product to work in a prototype is only part of the job.

The harder part is often figuring out what the product actually needs, what can be simplified, how the hardware and software should work together, and how to eventually manufacture it reliably and at a reasonable cost.

One principle I’ve learned is: don’t make a product more complicated just because you can. Figure out the core user needs first, then decide what features are actually worth building and what should be removed.

Right now, I’m working independently in Shenzhen and exploring what I want to build or work on next.

So if you’re working on:

* Smart hardware / IoT

* Wearables / smart rings / smart glasses

* Sensors / algorithms accuracy

* Hardware startups

* Shenzhen manufacturing and supply chains

* Taking a prototype to mass production

or if you’re simply curious about how a hardware product actually goes from an idea to something you can manufacture, feel free to ask.

And if you’re building something yourself, feel free to share what you’re working on or what problems you’re running into. Happy to exchange ideas and experiences.

I know one of the biggest challenges for many hardware startups is figuring out how to turn an idea or prototype into a real, reliable hardware product and especially how to find the right people, suppliers, and manufacturing partners you can actually trust.

That happens to be one of the areas I have a lot of hands-on experience with.

So if you’re struggling with turning an idea into hardware, finding the right suppliers in Shenzhen, or simply figuring out where to start, feel free to ask or reach out. I’d be happy to chat and share what I’ve learned.


r/hwstartups • • Sep 27 '26

Update to "sat on a hardware idea for a year," I flew to Shenzhen and held my first prototype

122 Upvotes

Since I last posted (original post here), a lot has happened.

First, I got more serious about IP (at the recommendation of my design partners in Shenzhen), which honestly deserves its own post. Short version, I talked to a few IP lawyer friends who gave me the rundown on what to expect (including the inevitable costs 😅). Then instead of going through firms, I messaged the specific patent attorneys I wanted to work with directly on LinkedIn. Every one of them thought that was wild, but it got me calls right away, mostly because they wanted to know who this woman was sliding into their DMs with an idea 😂 I've done a few now to learn the process before picking one for the non-provisional.

Ok, enough about that. What I really came here to talk about is Shenzhen.

I flew out solo to meet my design partner, and I was blown away. The city is beautiful, everyone was so welcoming, it was easy to get around, and the food was so amazing. But this is a hardware sub, so let's talk hardware.

Walking into their office felt like walking into a San Francisco startup. Super vibey, engineers all on an open floor, and an office dog that followed me around which was lovely.

They took me upstairs for our structural design review, and we spent over two hours going through the whole thing. They had a 3D printed prototype ready and walked me through each component one by one, then we went through the full design document together and settled on a few more material choices. I'd brought some reference materials from the US to leave with them, which they really appreciated. Having something physical to point at instead of describing it over a call made those decisions so much easier.

And holding it... going from an idea, to a 10+ page spec, to something I was actually holding in my hand, was an unreal feeling and yes I wanted to cry (didn't but I wanted to, just a few happy tears).

Two weeks after my visit, the team had a fully functional prototype ready. It's waiting to ship, but if you know anything about China holidays, it's Mid-Autumn Festival right now, followed by Golden Week, so I'm waiting until everyone's back. Honestly I'm envious the US doesn't have long holidays like this, but I am happy to wait. They sent me videos and it's exactly what I envisioned. Every little detail I mentioned, even the ones I felt like I said in passing, they got right and built into the design.

A few things I'd pass along from this stage:

  1. If you can go in person, go. We covered more in two hours in that room than in weeks of calls.

  2. Bring physical references. Materials, samples, anything you can hand them. It ends the "what do you mean by that" back and forth.

  3. Mention the small details, even in passing. My team caught things I barely said out loud, but only because I said them.

I have no doubt there are endless change orders ahead of me. But I'm still celebrating the small win. Going to Shenzhen, holding the device, meeting the team, deepening the relationship, and now patiently waiting for my first working prototype to show up at my door.

I'm now convinced mechanical design engineers have all the fun! After years in software, building this seemingly simple (yet somehow pretty complex) device has been the most fun I've had.

For those of you who've been past this stage, what caught you off guard between early prototype and production?