Project preparation guide · Electronic product

From an electronics product idea to a prototype: where should you start?

You do not need a completed circuit schematic to start developing an electronic product idea. Technical work can be planned once the problem, target user and main functions are defined. Selecting the right prototype objective ensures that electronics, software and mechanical work address the same question.

Product development guide · · Publication:

Describe your project Read the guide
Transformation of electronic product idea into requirements, technical verification, integrated prototype and testing steps
Conceptual technical demonstration · Project preparation guide · Electronic product
Initial outputFunction and usage description
FocusPrototype testing the right question
ContinueTesting and production preparation

VOMRO engineering approach

Clearly define what the first release will prove.

A product idea may contain many features; the first development phase need not complete them all at once. Initial questions may be whether a critical sensor works under the required conditions, whether users can hold the device comfortably or whether a particular connection can be established. The prototype reduces that uncertainty through observable results.

It is productive to start a project discussion with a problem definition, sample usage flow, and basic functions. Targeted size, energy source, production quantity and budget approach also affect the options. Writing uncertainties as unknowns prevents assumptions from being treated as design decisions. The roadmap below shows how the idea can be turned into a measurable development scope.

01

1. Turn the feature list into a use case

Divide “it will be smart and wireless” into the tasks the user will do. The user can turn on the product, make settings, see some data and, if necessary, transfer the result to another system. At each step, it should be written what the device will do, what information it will use, and how it will give feedback to the user. Initial installation and daily use can be treated as separate scenarios.

Record requirements in verifiable statements. The measurement range, recording frequency, connection format and environmental conditions should be as clear as possible. Organize priorities into core functionality and later versions. When a feature changes, it can be examined through this list whether it affects energy, size or server needs. The output of this phase is a concise product description that has the same meaning for both the customer and the development team.

  • Target user and concrete problem solved
  • Initial installation, daily use and service flow
  • Measurable core functions and priorities
02

2. Verify the most uncertain technical function early

If a sensor, communication link or mechanism is critical to product operation, its limitations are assessed first. A development board and temporary test setup may be enough to answer the question. This sample's appearance or assembly need not represent the final product; its purpose is to check whether the chosen approach works under the required conditions.

Off-the-shelf modules, custom electronics and combinations of the two are compared against cost, size, energy and production requirements. For wireless connectivity, choosing a protocol name is not enough. For example, Bluetooth SIG defines different BLE connection topologies; the appropriate structure depends on how the device will be used. Critical trial results are recorded through measurements, observations and outstanding questions. This provides technical evidence, rather than only a positive impression, for moving to the next stage.

  • Technical uncertainty determines the success of the product
  • Function verification with small setup
  • Comparison of ready-made module and custom design options
03

3. Develop electronics, software and housing in the same layout

While preparing the electronic schematic, board dimensions, battery, antenna, screen, buttons and connectors are considered in the same layout. The data flow and states of the embedded software are defined. While mechanical design solves assembly and service access, industrial design shapes usage and appearance decisions. Changes made in one part should be transferred to other disciplines regularly.

Power, reset, clock and programming connections are assessed together with the processor's hardware requirements. ST's hardware application note is an example reference covering these topics together; the documentation for the selected component governs the actual board. For devices that need to save energy, sleep and wake-up behaviour are included in the software architecture. If a server is required, device identity, transmitted data and command results are planned alongside the board firmware.

  • Board, battery, antenna and user interface placement
  • Embedded software and device states
  • Mechanical assembly, production and service access
04

4. Evaluate the prototype against initial acceptance criteria

An appearance model, functional sample and integrated prototype answer different questions. A housing model can assess grip and dimensions, an electronics setup the core function, and an integrated prototype how the parts work together. Stating the prototype type prevents an unverified feature from being considered complete.

Testing should cover more than normal use. Add relevant scenarios such as power loss, weak connections, invalid input, low battery and restarting. Link measurements and findings to hardware and software versions. Check access, connection orientations and assembly sequence on the physical sample. When a problem is found, record the affected requirement and how the fix will be retested to complete the revision.

  • Type of prototype and the function it will verify
  • Normal usage and outage scenarios
  • Record of findings, revisions and revalidations
05

5. Plan production preparation and project files from the beginning

In the transition from working prototype to production, bill of materials, procurement, assembly, programming and function tests are arranged. The fact that the part will be produced with a mold may change the design details. External tests necessary for the target use and market are also planned. The impact of changing parts between the production sample and the prototype should be reviewed; Production preparation is not just about ordering more pieces of the same file.

In VOMRO, the source code, electronic and mechanical design files and technical documents of the project are delivered at the end of the project. The initially specified list clearly includes build information, software version, interface definitions and relevant production outputs; third party licenses are noted separately. Sample PCB and electronic component assembly support is only offered to customer projects we develop. For an initial evaluation, you can gather the product's core functions, target user, and existing work.

  • Material, production, programming and test files
  • Revisions matching source code and designs
  • Validation plan for target use and market
Choose the prototype type based on the question to be answered
Prototype typeQuestion answeredBasic assessmentNext decision
Functional validation setupDoes the critical technical approach work?Testing a sensor, connection or mechanismChoosing or changing architecture
Appearance and ergonomics modelHow is the product handled and used?Volume, reach, grip and part placementImproving form and mechanical fit
Integrated prototypeDo the parts work together as expected?Hardware, software, body and usage testsPlanning revision and production preparation

How it works

Turn decisions into a project plan.

Not every project looks the same; however, the measurable requirement, controlled revision, and field verification steps remain unchanged.

  1. 01

    Describe the problem

    Write down the user, the basic need, and the job the product will do.

  2. 02

    Choose uncertainty

    Determine what technical or usage question the first prototype will answer.

  3. 03

    Develop together

    Advance electronics, software and mechanics with the same requirements.

  4. 04

    Decide with the result

    Plan revision and transition to production steps with test findings.

Frequently asked questions

Before starting the project

The technical scope, deliverables and test plan are clarified together according to the requirements of your project.

Can a project be started with a product idea alone?

Yes. The problem the idea solves, the target user and basic functions are enough to get started. A concrete work plan is created by evaluating technical feasibility and prototype scope.

Why might the first prototype not look like the final product?

The first sample is sometimes prepared only to verify a critical function. Appearance, ergonomics or integrated operation can be evaluated in different examples. The purpose of each prototype and the features to be tested are written at the beginning.

Is only a working sample delivered at the end of the project?

In VOMRO projects, source code, design files and technical documents are also delivered at the end of the project. The list of file formats, compilation information, and relevant outputs are clarified at the outset; third party licenses are disclosed.

Related content

From idea to a product under your brand

Consumer electronics and end-user product development

 From idea to working product

End-to-end product development

 Physically test the model

3D prototyping and product validation

 Design that makes the function visible

Industrial design for electronic products

All product development services

Your project, your product

Developed confidentially and delivered with source files.

We may work with a confidentiality agreement (NDA) before sharing technical details. At the end of the project, we deliver the source codes, design files and technical documents we have developed to you.

  • NDA before sharing technical information
  • Clear deliverables agreed at the outset
  • Source and technical files at the end of the project
Our confidentiality and delivery process
Let's start with your idea

Let's talk about the product you dream of and the need you want to solve.

Submit a project request +90 534 487 98 02