I’m a software developer with no hardware background, planning a small handheld device: camera capture, text processing on the device, audio through a headphone jack, and a few physical buttons. It needs to work offline and run a single app.

I’m choosing between two options:

• A) A generic rugged Android handheld from Shenzhen (5", 13 MP autofocus camera, 3.5 mm jack, physical buttons), locked to my own app.
• B) A custom build: Raspberry Pi 5, camera module, 5" touchscreen, audio board, battery board and a 3D-printed case.

Questions:

1. For a first batch of 10–30 units, which would you choose, and why?
2. If I go with A, how risky is relying on a generic Chinese handheld (silent hardware changes, discontinued models, firmware I don’t control)?
3. Do these manufacturers offer custom cases or button layouts at small quantities? At what volume does that make sense?

Thanks!

current prototype uses existing hub with small modification. totally fine for 20 units. if this becomes 5000, obviously not fine. ive been looking at standard parts and injection molding suppliers on alibaba and custom tooling isnt as impossible as i expected, but still feels early while design could change. anyone been through this? what volume made custom mold worth it for you? probably nylon or ABS depending final load. i dont need super tight aerospace tolerance, just consistent press fit. also how much variation should i expect between cavities on cheaper mold? manually touching up every few parts sounds harmless until youre doing thousands. trying to time custom tooling without doing it way too early.

on paper, software could have handled a lot of what we put on a small device. but making an action immediately available changes how often you actually use it.

that has stayed with me as we work on what comes next.

has building something physical ever changed your mind about an interaction you first imagined as an app?

Hi everyone,

I'm building Migoo, an AI tool for turning source materials into editable presentations.

One question I keep coming back to is trust.

A presentation can look polished and still be wrong in subtle ways. A key qualification might disappear from a summary, two separate findings might get combined, or a number might lose the context that makes it meaningful.

For a casual presentation, these issues might be manageable. For a client meeting, research review, or business decision, they matter much more.

I'd appreciate perspectives from people who use AI for professional work:

• Do you check every slide against the original source, or only the important claims?
• Would links back to the source passages make you more comfortable using AI-generated slides?
• What would make you reject a generated deck even if the design looked excellent?

I'm trying to understand what level of accuracy and traceability people actually expect before trusting this kind of tool with important work.

Critical feedback is welcome. I'd rather identify the trust problems early than build around assumptions.

i'm with rove, we make portable triple-monitor setups for laptops. these are just example setups to show the idea, not my own trips or places. the point is more screen space, less tab chaos and faster work wherever you open your laptop.

it's one usb-c cable for video plus its own power adapter.

what do you think?

Pm me direct on TDLOGY website

I’ve been thinking about sample fees in international sourcing.
Imagine a buyer contacts five manufacturers about a new product.
All five appear capable of producing it.
The buyer requests samples to evaluate quality before placing a production order.
Two suppliers offer free samples.
Two charge a small sample fee.
One requests a much larger payment because the sample requires custom engineering work.
Would the sample fees affect your supplier evaluation?
I can understand the manufacturer’s perspective.
Preparing samples isn’t always as simple as taking something from existing inventory.
Custom samples may require engineering time, special materials, machine setup or additional inspection.
If a manufacturer receives many inquiries that never become orders, providing everything for free could become expensive.
But buyers also have legitimate concerns.
They need to evaluate suppliers before committing to production.
Paying significant sample fees to several manufacturers could make initial sourcing expensive.
And paying for a sample doesn’t guarantee that the manufacturer will meet the required quality standard.
Maybe the distinction should be between standard samples and custom-developed samples.
For standard products, a free or low-cost sample might be reasonable.
For customized products requiring genuine development work, charging a fee seems easier to justify.
Another possibility is making the sample fee refundable or creditable against a future production order.
But that arrangement also needs clear conditions.
There’s one more complication.
If the buyer pays for custom sample development, does that payment include any design rights, technical documentation or future production obligations?
Or is it simply a service fee?
Those questions could matter when selecting a long-term manufacturer.
For buyers: Are paid samples a normal part of your sourcing process, or do you prefer suppliers that provide them free?
For manufacturers: How do you decide when to charge for samples, and do you credit those fees against future orders?
I’m particularly interested in the differences between standard catalog products and customized industrial components.

Hi everyone,

I'm a CSE student in Bengaluru, India, building Sygnetta, a physical IoT device paired with a web platform that lets students check faculty availability before walking across campus.

The problem is simple: students often walk to faculty cabins for project reviews or assignments only to find the faculty member unavailable.

I've had the PCB fabricated and am working on assembling the device and integrating it with the software. My college principal has also agreed to a pilot.

I'm now looking for a small amount of capital for R&D, specifically to simplify the hardware, optimize the PCB and components, and bring down the cost per device so it can be deployed affordably across campuses.

I'm particularly interested in non-dilutive grants, hardware incubators, prototype-development programs, or crowdfunding options that accept student founders before company incorporation.

For founders who've built physical products in India:

• How did you fund your first few prototypes?
• Are there grants or incubators you'd recommend for an IoT product at this stage?
• Are there any legitimate communities or platforms where people support early hardware projects?

I'd appreciate specific recommendations or experiences. Thanks!

Looking for someone around to Philly, NJ or Delmarva area be able to meet up to help with development of a flight simulator controllers meant for space simulation.

\- Uber prefer US based but willing to hear all taker.

\- can do attitude, hobbist or tinker, likes bending wrench, electronic / software background are some of the quality I'm looking for.

\-passion about flight sims especially space sims are a plus Star citizen no Man's sky elite dangerous

\-if you like to know more hit me up DM's I have a small little model going.

Hey m23 here, I am a Mechanical Engineer, I am thinking of design and develop a solution using the resources in my hand i.e CAD, FEA , CFD , machine and sheet metal shop , 3D printing setup , National Labs for testing . I am From Ludhiana which is hub for manufacturing, I want to develop something of my own that I can directly sell to customers . I want to use my engineering knowledge to build something meaningful. Any ideas are Welcome .

​

I’m not an engineer by degree, but I’m deeply interested in technology, electronics, hardware and product development.

I believe capability comes from learning, building and actually solving problems.

So I’m putting myself out there: give me a real engineering problem that you’re struggling with. I’ll research it, learn what’s needed and try to build a practical solution.

I’m not saying I can solve everything. I just want one real problem and one chance to prove myself.

If you’re a founder, engineer or builder with a challenging problem, DM me.

I'm Harsh, based in Bengaluru. Under the name Shim Works I design small hardware products that fix everyday annoyances. Two concepts so far, both at the renders stage:

• Sideport: a phone case that moves the USB-C port to the side, so the phone sits low and straight on a MagSafe stand, car mount or tripod while it charges.

Processing img it0tnysbckxh1...

• Overpass: a magnetic card wallet that passes wireless charging through to the phone, so you can charge on a MagSafe charger without taking the wallet off.

Processing img 49vgmqkbckxh1...

Both are here, with drawings and design targets: https://claude.ai/artifact/UBDU4kdAx3f6niShrLA9jM

What I bring: the ideas. I spot an everyday problem, come up with a product that fixes it, and turn it into a concept with renders and a concept page, like the two above.

What I'm looking for: someone for everything after the concept: engineering, working prototypes, certification, manufacturing and logistics. Ideally you already have contacts with prototype shops and factories in India or China.

I'm open to:

1. A co-founder who wants to build a hardware brand together
2. A partner who handles prototyping and manufacturing for a share
3. An accessory brand that wants to co-develop or license ideas like these. I have more coming.

If that's you, comment or DM me. I'd also like blunt feedback on the two concepts. Would you use them, and what would kill them?

We're a 6 person hardware team and our enclosure plus 4 internal brackets just passed drop and thermal testing on printed and machined prototypes. Next is a 500 unit pilot, then a few thousand a year if the pilot goes well.

Our options for the prototype to production manufacturer include Quickparts, Jiga and the local shop that machined the first brackets, and I'd rather not requalify someone new at 5,000 units. Everyone keeps telling me the first real manufacturability review is where the surprises show up. For those who've been through it, what changed in your design once a manufacturer reviewed it?

I'm a semiconductor engineer with around 1.5 years of experience, exploring the idea of building my own AI hardware startup alongside my full-time job.

I'm working on developing a specialized AI inference accelerator, with the goal of improving computational efficiency and reducing power consumption compared with conventional approaches.

I'm still in the early stages and trying to understand how to validate the technology and build a credible prototype without significant funding.

I'd love to hear from founders who have built semiconductor, chip-design, or hardware startups:

- How did you validate your idea before investing heavily in hardware?

- How did you access EDA tools and licenses without a large budget?

- Did you start with open-source tools, FPGA prototyping, university labs, or incubators?

- How did you fund your initial development and gain access to experienced engineers?

- How did you balance startup development with a full-time job?

- What milestones helped you decide when to seek funding or go full-time?

- If you were starting today with limited capital and experience, what would you do differently?

I'd appreciate practical advice from people who've actually gone through this journey, especially those who started without significant funding or institutional support.

Thanks!

I see a lot of the same questions popping up here, adding my thoughts as someone that has worked in R&D and product development.

Intellectual Property

If you want to develop a product, and want to keep your options open to patenting it, you will need to have a basic understanding of intellectual property, even if your product isn't a success, this will stand to you for future products. University of Pennsylvania have an excellent introductory course for it on edx.org, you can audit it for free.

Market Research

Most products fail because the market doesn't really care about them, if you haven't already, I suggest you start with market research. Secondary research is good for getting an idea of the size of your target market. Customer interviews are gold, try to learn as much about them as possible, you will use what you learn throughout the product development process, including how to market to your ideal customers. Use customer interviews to build a persona of your ideal customer. Be careful with market research, people like to tell you what you want to hear, ask open questions, like "What are your problems with sleep?", rather than "Would you buy this sleep mask?". If you do want to ask a leading question, leave it to the very end of your survey/interview. At this stage you may be able to identify some of your ideal customers and possibly recruit them for future market research as your product is developed.

Minimum Viable Product

This is part of market research. Start with a theory you have for a feature your product should have. Make the quickest, cheapest version of your product, it should be embarrassingly bad, but communicate the feature effectively. Show this to some of your ideal customers and ask them for feedback. Try to be neutral to them when presenting it, "say one of the team made this" or something similar, so they aren't trying to protect your feelings. After you've validated/invalidated the feature, move on to the next theory you have and create another MVP to validate that, and so on.

Design Concepts

You can skip this step if you are confident in what you have learned from talking to perspective customers & got enough feedback from them about your MVPs. Alternatively, you could try to build on that knowledge and challenge yourself / your product developer to improve on them. Generally, aim for 3 design concepts & pick the one you think is best. You could choose to present them to your ideal customers for feedback before choosing.

Prototype Development

Develop your chosen concept / MVP into a manufacturable design, have it manufactured and assemble it yourself, if that is feasible. Document any issues in assembly and any areas that could be improved. You could choose to present it to your ideal customers for feedback.

I see a problem that seems to come up, where people struggle moving from design concept to prototype design, here is my rough approach:

1. Develop at least 3 design concepts & pick the one you think is best
2. Find your design constraints (size, weight, IP rating, relevant engineering standards, etc)
3. Develop your prototype

a) Start with what you know

▪ design constraints

▪ if your product has a mechanism that moves something from point A to point B, model up in CAD the part that is moved, then position it at point A & point B

b) Fill in the blanks.

▪ Think of ways to fill in the blanks you don't know

▪ Think of it like a puzzle, model a solution in CAD

▪ Don't overthink it, try to solve each requirement bit by bit

c) Evaluate

▪ You can evaluate in CAD, look at your design with a fresh pair of eyes

▪ Very few designs are good on first attempt, look at what you can simplify

▪ Simple isn't easy, most designs are overcomplicated

▪ What components can be modified to solve multiple purposes?

▪ What components can be eliminated or simplified?

d) Iterate

▪ Keep redesigning your product

▪ With each redesign, you should learn more and get ideas on how you could improve your product

That's all I can think of off the top of my head, hopefully someone finds it useful.

Hey fellow hwstartups / solo devs

I wanted to share a quick reality check on what early-stage hardware prototyping looks like in Europe right now, specifically regarding component sourcing for small-batch iteration loops.

With recent changes to EU cross-border e-commerce policy (the removal of the sub-€150 tax exemption, the transition flat tariff of €3 per commodity category/HS code, and logistics providers tacking on clearance fees like €2 per HS code), small component orders from suppliers like LCSC have become financially brutal.

Here is a real example from a recent checkout cart for a simple prototype build:

• 33 Component Items (Parts Total): €27.78
• Shipping Fee: €13.28
• Fixed Tariffs (HS categories): €27.00
• (Plus upcoming line-item/HS handling fees adds another wave of per-category fixed charges)
• Total: €67.84 (for €28 worth of basic passives, ICs, and sensors).

When you add local VAT on top, a simple €28 basket of components easily balloons past €70–€100+ before you even factor in PCB fabrication, stencil costs, or local assembly.

Alternatively, if you pivot to western distributors like Mouser or DigiKey, you hit the €75 tax-exclusive free shipping threshold, which means every quick "I just need a couple of test ICs" order lands around €95–€100+ after VAT, or carries a heavy €20–€25 base shipping penalty.

While the macro-goal of building European supply chain resilience makes sense on paper, the practical reality on the workbench is that the barrier to entry for early-stage hardware innovation and rapid iteration in the EU is getting exceptionally high. It forces independent devs and small bootstrapped startups to either hoard inventory or freeze experimental builds altogether.

How are other EU-based founders and hardware engineers adapting to this right now? Are you batching orders, shifting to local stock, or just absorbing the hit as a cost of doing business? Would love to hear how you're navigating this bottleneck.

For hardware founders who have visited factories in Shenzhen or Dongguan: what do you wish you had prepared before the trip?

One thing I’ve noticed is that factory visits become much more useful when the supplier screening is mostly done before arriving.

Instead of trying to visit as many factories as possible, it seems better to shortlist a few and use the visit to verify things that are difficult to see remotely:

- whether key processes are really in-house

- who actually handles engineering and quality

- how testing and traceability work

- what is subcontracted

- whether the factory can realistically support the expected volume

- whether they could work as a second source, not just the cheapest quote

For teams coming to Shenzhen for the first time, I’m curious:

What turned out to be most useful during your factory visits?

And what ended up being a waste of time?

i work on hardware with a small team. the idea came from a simple frustration, i kept repeating small actions that should've been faster than finding the right menu.

it made me curious how much of our day goes to reaching for controls instead of just using them.

so yeah, what tiny interaction in your workday would you redesign first?

working on it left me with a bigger question. if the useful action changes with your context, why do so many interfaces make you go looking for it?

honestly it's the thing i keep coming back to. i'm curious how other hardware builders think about this.

where have you found that a small dedicated interface beats a flexible app?