It has been quite a while since I last posted in this community, so this time I’d like to share some of the progress I’ve recently made on Easing-Point.

I currently define Easing-Point as a handheld gaming device controlled entirely by a single switch. I’ve now completed a Version 1.0 demo video and redesigned its appearance and color scheme to make it look a little less ugly.

The original motivation behind Easing-Point was to explore more possibilities for game controls instead of limiting handheld games to the traditional D-pad layout.

The second reason was that I wanted Easing-Point to become a platform for showcasing games that are creative but mechanically simple—games that people can pick up and play almost anywhere, even when they only have a few minutes.

I’ve made several rough game demos, including a traditional space shooter and a simple text-based murder mystery. These demos helped demonstrate that it is possible to create playable games using only a single spring-loaded lever switch.

Of course, Version 1.0 has many limitations. Although using only one switch makes the device look extremely minimal, it also removes many possibilities for interaction.

That is one of the main problems we are trying to address with Version 2.0. We have added a button on the top of the device, as well as a millimeter-wave radar sensor to provide an additional layer of input. In other words, we are now experimenting with using the player’s heart rate and breathing as part of the game controls—and designing games specifically around those interactions.

While keeping the project experimental and creative, we have also tried to keep the PCB and mechanical structure relatively straightforward in preparation for eventual mass production.

We have been working on this project for so long that, honestly, we have almost stopped worrying about whether it solves a genuine need or is simply something we are making for ourselves.

Either way, I still wanted to share it with everyone. We are currently planning to launch Easing-Point on Kickstarter toward the end of this year.

If you’re interested, you can follow our progress on the official website, where we also post development logs and other updates:

https://georiginai.com/

Hey everyone — building a hardware product (a small secondary display bar for desks, think a compact monitor-adjacent gadget) and I'm at the "get real manufacturing costs" stage before I can price a Kickstarter campaign. I could use some outside perspective because I think I'm overthinking this.

Where I'm at: I have a working prototype built on a Raspberry Pi 5 and an off-the-shelf display, which proved out the concept. But what I'd actually ship to customers is different — a custom PCB (the Pi is too thick for the final form factor), edge-to-edge display, non-touch, anti-glare coating, and only one cable going into it total (power). Roughly the scale of Corsair's XENEON EDGE but smaller.

Here's the problem: almost none of that final product actually exists yet.

• The custom PCB has no design, not even a rough schematic — just the target specs above
• The mounting mechanism (how it physically attaches to a monitor or desk) is also unsolved — I have a rough idea (magnetic base plate + snap-on unit) but nothing finalized

My plan was to get a close-enough manufacturer quote now, based on the general spec, so I can set a realistic Kickstarter price — then use the money raised to actually hire a consultant/engineer to design the PCB and finalize the housing/mounting into something manufacture-ready.

My questions: Is it even realistic to get a usable cost estimate from a manufacturer with this little locked down? And if not — what's the minimum I'd need to bring them (a schematic? a comparable reference product? something else?) before they could give me even a rough range? First time doing hardware manufacturing, so genuinely feeling pretty in over my head on this part — appreciate any pointers.

Hi all,

My future product vaporises Vegetable Glycerin to test professional equipment. We're nearly done prototyping and thinking about implementing Elfbar-style disposable cartridges — no mic or battery needed, so a stripped-down disposable version.

Any ideas where to source such manufacturers? Alibaba seems to be banning vape-related search words. My thinking was towards exhibitions.

I have an idea for a future (hardware based) gaming product... Considering that there are a number of Shenzhen based companies who already work in the sector, and who have a long track record of producing something similar, is it better to work with them in terms of OEM / ODM manufacturing... Or is it better to hire freelancers (via Upwork etc) and work on birthing the project independently?

As someone who will be bootstrapping the entire operation... I want to be as cost effective as much as possible - whilst still being in a position to create a high quality product that's also markedly different from what's already out there.

My main concern when it comes to working with an established company is that I wouldn't be in a position to own any of the designs or CAD files, and I'd be worried that the company would quickly introduce a similar product to the market if they thought that my ideas were good.

I would be looking to create a fully working prototype (using off the shelf and readily available products), and would also want to create a pre-order campaign (lasting 6-9 months) that fully pays for manufacturing (at least 10k units) as well as certification / shipping / warranty / taxes etc.

What would you suggest?

I've been working on an open-source hardware project called Spaghetti LAB for quite a while, and I've reached a slightly weird problem:

I can build it, but I'm struggling to explain what it is in one sentence, basically, i'm thinking at the UVP taht describes better my project.

The project is now pretty far along. It has gone through several hardware revisions, a lot of them based on feedback I've received online. I recently got a spot at Maker Faire Rome and some support from JLCPCB, so I'm redesigning the landing page and trying to finally communicate what the project is actually useful for.

The original idea came from a problem I kept running into while prototyping.

You start building something reasonably complex, but instead of working on the thing you actually want to test, you end up spending days debugging all the little pieces around it: wiring, bad solder joints, poorly documented modules, ADC quirks, libraries, firmware, etc.

In one project we spent almost a month getting a PID-controlled heated wall with a display working properly, because we had some issues with MCU registers.

The funny part was that the heated plate wasn't even the prototype. It was just one small part of it.

That's basically why I started building Spaghetti LAB.

The idea is to make that supporting electronics something you can assemble, configure and change very quickly.

The hardware is made around two types of blocks:

Connector blocks connect to the real world: sensors, motors, switches, signals, etc.

Function blocks handle things like conditioning, acquisition, outputs, communication and other functions before connecting to the controller.

Everything snaps onto a backbone. Multiple backbones can be connected to create larger systems.

Each block is automatically identified through NFC, so when you physically build something, the software creates a digital representation of the hardware.

Then there's a visual programming environment. The easiest way I can describe it is something like n8n for embedded hardware: you connect actions and logic to schedule events, read inputs, control outputs, process data, etc., without rewriting firmware every time the prototype changes (i worked a lot on the OS built in zephyr, so basically no firmware needed, just dynamic driver load and you just deploy a config file).

There's also a configurable dashboard for quickly creating controls and visualizations for the prototype.

The goal isn't really "no-code electronics". It's to remove as much friction as possible between:

I have an idea → I build it → I test it → I change it → I test again.

For Maker Faire I'm actually thinking about turning this into a small physical challenge.

Instead of giving visitors a PC, they'd get NFC cards with actions such as READ, WAIT, SET, etc.

They might receive a challenge card:

"Blink an LED every second."

They place the action cards on the backbone, and the corresponding programming blocks appear on the screen. Then they physically attach the required hardware modules, which also appear automatically. Finally they tap an EXECUTE card.

If their physical hardware + logic solve the challenge, they win an entry for a kit giveaway.

Harder challenges could be things like:

"Measure temperature and display the updated value every second."

and would give more entries.

And this brings me to what I'd really like feedback on.

If you saw this project for the first time, how would you describe it?

I've been experimenting with things like:

"A programmable breadboard without the mess of wires."

or

"Build prototypes with the flexibility of a breadboard and the reliability of a PCB."

But I'm not convinced either really communicates the potential of the system.

I'll attach some photos of the actual PCBs, and a render of what the finished hardware should look like.

I'm particularly curious about three things:

1. What do you think this is after seeing it?
2. Would something like this actually be useful in your prototyping workflow? If so, for what?
3. What would you want to see on the landing page before thinking "OK, I get it"?

I'm probably too deep into the project at this point to see it with fresh eyes, so criticism is absolutely welcome.

T-H-A-N-K-S

Hey everyone,

I’m building an Autonomous Navigation as a Service (ANaaS) startup. The core premise is transitioning industrial automated vehicles (AGVs, tuggers, custom carts) away from rigid PLC ladder logic and floor tape, and retrofitting them with a dynamic ROS 2 / Nav2 stack.

We are offering this as a plug-and-play SaaS/RaaS model so clients can get adaptive, intelligent routing without needing in-house robotics R&D.

The tech is solid, but I’m hitting a wall on the Go-To-Market side in the industrial space.

For those of you who have sold robotics, heavy automation, or B2B hardware/software:

1. Who is the best early adopter for this? Should I be cold-calling Hardware OEMs to white-label my stack, or targeting System Integrators who are building custom setups for factories?
2. How did you land your first 3 pilot programs?
3. Industrial folks can be notoriously risk-averse. What was the "aha" moment that made your early clients trust a modern software stack over their legacy systems?

I'd love to hear from anyone who has navigated the sales cycle in the manufacturing, warehousing, or robotics space. Appreciate the advice!

Equipment Tracker Pro lets you document mechanical equipment, manage work orders, and generate 13 branded equipment and service PDF reports right from your phone instead of typing up notes from memory at the end of a shift.

I am a working HVAC technician and I built this for my own service calls and boiler room checkups. Offline records, work orders, parts inventory, and basic PM scheduling are free on mobile, permanently. No record cap, no expiry, not a trial.

Upgrading to Pro gives you cloud backup, the web dashboard, and exportable PDF reports with your own company logo.

Pro is a 7-day trial if you want the reports and the dashboard.

What projects or tools are you all building right now?

https://equipment-tracker.com/guides/reports

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).

We also experimented with the red-black-white version of this panel, but the refresh cycles were way too slow.

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. :)

Curious what other people's version of this is, something that seemed completely reasonable at the design stage and only became obvious once it hit an actual manufacturing process, whether that showed up as a weird quote or parts that just didn't work the way you pictured.

Doesn't have to be a big one, just want to hear what people actually ran into.

Hey everyone!

We’re the team behind PIIX. We’ve been building an AI workspace for creative work, and we’re at the point where we’d really like to get it in front of people outside our own team.

The idea behind PIIX is pretty simple: instead of jumping between different tools when you’re researching, collecting references, developing an idea, generating images, or exploring different directions, we wanted to bring that process together in one place.

That’s what our Flowboard is for. You can organize references, prompts, generated images, and different ideas in one workspace. You can also bring in things you’ve already made with tools like Midjourney or ChatGPT and keep developing them in PIIX.

We’re still early, though. So rather than telling you that PIIX is the future of creative work or something 😅, we’d honestly just like to know:

Does this actually make your process easier? What feels useful? What feels unnecessary? What would you change?

We’re looking for some early users who are interested in creative work and experimenting with AI. No particular type of work or background required.

As an early user, you can get one month of PIIX Pro completely free ($36 value) in exchange for trying it out and sharing your honest thoughts with us.

If you’re interested, check out PIIX here: https://piix.studio/ and send us a comment or DM. We’ll get in touch and set up your free Pro access.

And honestly, even if your feedback is “yeah, I don’t really see the point,” that’s useful for us too. We’re still figuring things out, and we’d rather hear what people actually think.

Thanks for reading!

What are smaller hardware businesses using to manage materials and avoid running out of parts before a production run?

I've been looking at MRPeasy, Katana, and Odoo, but it's difficult to tell how well they work once you're managing multiple BOMs and supplier lead times.

Has anyone used one of these, or found any other option that works well? I'd be interested to hear what you like about it and whether it actually helped you catch shortages earlier.

Long story short, several years ago my father invented a system to sanitize water and basically increase the capacity of water treatment plants with only a small modification. Currently, we are moving to commercialization. We have 2 units successfully in the field running for more than a year and have interest globally. For the first time in years we have tangible momentum

To get to this point we have exhausted all our own resources and that of the 100k equity investments we have had. To successfully get to the market we need roughly 300k over the next 3 years (Exchange rates are in our favor). We need capital now to keep moving and actually penetrate the market.

Unfortunately, in our country grants are not an option for us. We have participated in several incubator/ accelerator programs that are extremely time consuming, disappointing and offer prizes of free access to software or monetary rewards of just 2k. We have yet to present directly to an investor.

My question is then, what is the best way for a hardware manufacturer to reach audiences/ investors outside of their home country?
Is it worth putting our limited resources and effort into Social Media? If so, what sort of presence gains the best traction (especially with such a technical target market).

I’ve been building a small ESP32-S3 voice device for kids. The MVP is working now — actual hardware, custom firmware, WiFi, SIP/RTP and clear two way calls.

I’m also already working with a manufacturer in Shenzhen, so its beyond the dev board stage.

For hardware founders here, when would you start raising?

After a working MVP? After EVT/DVT? Or would you try crowdfunding/preorders first?

Trying to understand where bootstrapping normally stops making sense once tooling, certification and production costs start coming in.

I’m sharing this early because I need a reality check before I spend more time building it.

I’m working on a small side project and would love feedback on the problem it should solve first. What makes you personally decide a new tool is worth trying instead of sticking with your current workaround?

I’m especially interested in the point where an annoying task becomes annoying enough to look for a solution.

So i have been running my hardware startup for little over 10 years and now that it is more stable, I would like to explore a different avenue.

I was looking into becoming a Fractional CTO or technical advisor (haven't made up my mind yet).

But before I begin, i want to know if hardware startups do hire fractional CTOs or is Full time CTO a better option for them.

I want to know from founders and co-founders if they would hire someone like that, whether pro Bono or for a small equity or even better for a monthly retainer.

I have seen many software startups hiring fractional CTOs, so wanted to scope the hardware, core engineering market for the demand for this title.

I’m 27. I recently joined a product company as a PM after spending ~5 years in a small bootstrapped hardware startup, where I was one of the earliest employees and eventually grew into a director-level role.
My previous role was very hands-on across product development, hardware, bit of firmware, manufacturing, vendors, customers and execution. It was very startup/ad-hoc style, and I had a lot of ownership and freedom.
I joined this new company specifically to learn proper product/project management and understand the structured side of hardware + firmware + software products and also financial perspectives.
It has been just over a week and honestly, I feel completely out of my depth.
JIRA, documentation, certifications, firmware/software releases, structured processes, international clients, formal tracking, etc. are all new to me. I’ve been assigned a project already and I’m slowly figuring things out, but it has definitely shaken my confidence.

At the same time, I’ve received another offer from a company working on hardware manufacturing/prototyping solving pain-points for startups.
That role is much closer to my existing strengths, I'd have much more ownership: handling projects, customers, vendors, bringing in business and potentially helping scale the business but no firmware or software exposure.
So essentially:
Option A: Stay where I am, tolerate the uncomfortable learning curve and build the skills I’m missing.
Option B: Take the other role, leverage what I’m already good at, get much more autonomy/business exposure and potentially move faster towards entrepreneurship.

Long term, I don't see myself as a traditional PM. I want to build/run businesses and products around technology, but I don't have the exact path figured out yet.

Would you guys stay and push through the learning curve, or take the opportunity where you already have leverage and ownership?
Especially interested in perspectives from people who have made a similar transition.

Hi Everyone!

I'm new here, my name is Matt and I am the CEO of a company called "Circuit Center". I had heard from some of my colleagues that there were a litany of issues within the PCB industry, not the least of which being gatekeeping educational and useful tools behind a paywall, causing a difficult barrier to entry

I made my app because of this.. and because of spite towards some former business partners. Every tool & future-tool on the site is free (we have data science tools, API integrations, user-metrics, a free BOM tool, and a PCB creator // editor // 3D-viewer & more on the ay this week) so that people can learn & price their boards.

The only way the company makes money is through people advertising their products on the site, and I will eventually only ever feature products & links to sponsors on the site as the sponsors come in, but for now I have integrated every API I can to fill the website's data set :)

I would love any and all feedback (a few potential partners told me they would love a "mom-and-pop-shop locator tool" for me to integrated into the interactive map I made & I cannot help but love it!), so please do not hesitate to reach-out or comment with criticism and/or questions. I just want to help people that make things which are wonderful, and I am proud of my creation so far. Please check it out at circuitcenter.ai for more & view our signup page at our signup page for more!

I managed to make a prototype that gets my idea across, basically just a solid frame, and a lever attached to a tube. It's measured in inches not feet or centimeters, what's the best way I can get this thing streamlined so it's not so janky?

Hi,

I'm not building another AI CAD tool, but I'm building the missing layer: the workflow between "I have an idea" and "I have a product in hand."

Nirmana AI — an AI-powered platform that carries a physical product across the whole journey in one marketplace:

- Generate: describe what you want → iterate 2D/3D → export STL/OBJ/STEP

- Validate: publish to a gallery and see if anyone actually wants it before you spend on tooling

- Manufacture: route validated designs to real shops for quotes and commercialize.

My background is architecture, prototyping, design controls, and verification/validation. So this is built around making sure a design is manufacturable.

Would love your feedback:

1. If you're an indie designer, hardware founder, brand, or maker, where does idea → CAD → manufacturing hurt you most today?

2. For those who've made it to production: which step ate the most weeks?

3. What would make you trust an AI-generated design enough to manufacture it?

Opening 100 founding spots — 50 creators + 50 manufacturers to shape this (no card required): https://nirmanaai.com/

If you think the idea is wrong, please tell me why?

We're a small electronics manufacturer based in Germany (industrial communication, IO-Link hardware, smart industrial gateways). With the new EU Packaging Regulation (PPWR) in force, cross-border selling within the EU needs local registration and a representative in each country we ship to, which is impractical at small volume. However, we are registered for the German market with all necessary obligations (LUCID, system provider).

I am looking to connect with similarly-sized electronics manufacturers or vendors in other EU countries for a reciprocal distribution setup instead. The idea is: we sell your products here, you sell ours in your country. Each side stays locally registered and compliant in their own market, avoiding costs per country.

Ideally I'd be looking for companies with a comparable product portfolio and an existing customer base in industrial automation, embedded systems, or electronics in general.

If that sounds interesting, drop a comment or DM.

I’m preparing a hardware crowdfunding launch for Mimi Tape, an offline pocket music and video player that uses swappable cassette-style cards. The current prelaunch page is here: https://www.backerkit.com/c/projects/ajana/mimi-tape-the-pocket-mp4-player-with-digital-cassettes/pre-launch

I am the creator, and I want to validate more than the visual novelty. What would you test in the next week: landing-page conversion, willingness to pay, card usability, or something else? I would appreciate specific feedback on the page or the product pitch.

i keep catching myself doing this, and i see other people do it too. treating "this got hard" or "i thought of a reason it probably wouldnt work" like its the same as actually trying and failing. its not.

a prototype that never left your laptop isnt failure. an idea you talked yourself out of pitching isnt failure either. thats just avoidance dressed up as logic.

real failure only happens once you show the thing to someone else and get an actual answer back. an actual no. someone telling you it doesnt work. until that happens you dont have data, you just have a guess youre calling a conclusion.

its like a guy with a crush who never actually asks her out. hell come up with a hundred reasons it "probably wouldnt have worked anyway." none of that is real though. he doesnt actually know its a no, he never asked. hes just pre-rejecting himself so he never has to find out for real.

if the only proof your idea sucks is a story you told yourself before anyone else weighed in, thats not proof. go find out for real.

I'm building Wave Sonic under my studio, T.Tech — a pocket-sized music player that ditches touchscreens for a haptic rotary dial (we're calling it T-Dial) and comes with a bilingual AI assistant baked right in (Aries AI). Think tactile, retro-futuristic hardware meets modern AI, not another phone-shaped slab.

We've already got:

Two design directions (dark futuristic + retro reel-to-reel analog)

Detailed hardware specs and pricing tiers worked out

A full investor deck and product landing pages built

What I'm looking for now is people who want to actually build this with me — hardware/electronics folks, embedded/firmware devs, industrial designers, or anyone who's into audio gear and wants to get their hands dirty on a real product from prototype to launch.

If you're into hardware startups, love music tech, or just want to work on something that isn't another SaaS app — drop a comment or DM me. Happy to share more details, sketches, and the deck.

Let's build something people actually want to hold.