# Starting from a wearable platform: what carries over? — SyntaForge

Canonical: https://syntaforge.com/en/blog/choosing-a-wearable-platform/
Language: en

> This is a text rendering of the same public webpage. Use the canonical URL for citation. Private inquiry records and administrator data are never included.

[← All articles](https://syntaforge.com/en/blog/) Hardware platforms 2026-11-04 SyntaForge editorial

# Starting from a wearable platform: what carries over?

An existing platform brings real hardware into the discussion earlier. Turning that reference into your own product still requires a clear account of what needs to change.

In this article

[Separate the platform from the finished product](https://syntaforge.com/en/blog/choosing-a-wearable-platform/#journal-section-0) [Wearing position changes the design problem](https://syntaforge.com/en/blog/choosing-a-wearable-platform/#journal-section-1) [A working interface is not the entire task](https://syntaforge.com/en/blog/choosing-a-wearable-platform/#journal-section-2) [Use a gap list to decide what happens next](https://syntaforge.com/en/blog/choosing-a-wearable-platform/#journal-section-3)
Starting from a wearable platform: what carries over?
Illustrative development scene

## Separate the platform from the finished product

A platform offers a foundation to assess, such as a display format, existing structure or development interfaces. A finished product makes choices around its users, tasks and environment. A reference device working in one situation does not establish suitability everywhere.

Put the current capability beside the project requirement. Mark what can carry over, what needs to change and what still needs testing. This usually produces a more useful discussion than a specification table alone.

## Wearing position changes the design problem

A wrist, chest or other mounting position changes viewing angle, button use, stability and daily removal. Different wearing arrangements need separate assessment even when they share an electronic foundation.

For field use, explain the working environment and boundaries early. Suitability cannot be established from appearance or photographs; the relevant requirements need project-specific assessment and validation.

## A working interface is not the entire task

A connection needs to support a business action. Where the data comes from, who confirms it, what happens when the connection drops and how the next connection recovers are all product decisions.

Walk one complete task through the platform: an input, feedback on the device, a user action and a record in the phone or business system. This exposes software and interface changes that a component list can miss.

## Use a gap list to decide what happens next

A useful review leaves four columns: the existing foundation, project differences, unanswered questions and the next deliverable. Not every question needs an immediate answer, but each should have a clear next step.

The right platform can reduce repeated work. Its value comes from how well it fits the project, while product definition, trial use and validation still do their own jobs.

For your next discussion

Make a gap list before deciding whether a platform is right for the product.First published 2026-11-04 [Discuss a product](https://syntaforge.com/en/contact/)

## Keep reading.

[All articles](https://syntaforge.com/en/blog/)

[What should you define before building your first wearable?](https://syntaforge.com/en/blog/defining-first-wearable/) Product definition 2026-11-04

## [What should you define before building your first wearable?](https://syntaforge.com/en/blog/defining-first-wearable/)

Agree on the user, the moment of use and one essential task before choosing screens, sensors and first-version features.

[Read article](https://syntaforge.com/en/blog/defining-first-wearable/)

[Why run a pilot batch after the prototype works?](https://syntaforge.com/en/blog/prototype-to-pilot/) Prototypes & production 2026-11-04

## [Why run a pilot batch after the prototype works?](https://syntaforge.com/en/blog/prototype-to-pilot/)

Separate “this unit works” from “the next batch can be built consistently”, and use a pilot build to check assembly, inspection and actual use.

[Read article](https://syntaforge.com/en/blog/prototype-to-pilot/)