The architecture that turns a smart textile into a connected product system
Four ways into the architecture
A Textile Computing™ product is one coordinated system of seven architectural concerns. Inspect the layers, reconfigure them by implementation, assign responsibility, or apply the cross-stack requirements — the same model, seen from four perspectives.
Select a layer to read its role and connections.
Textile interface
- What it is
- The physical structure that meets the body — engineered around contact, fit, stretch, placement, comfort, movement, and care.
- Receives from
- The body and its physical context — movement, contact, and the surrounding environment.
- Passes forward
- A conformable surface, positioned for the product's intended function.
- Design questions
- Contact and placement · fit and stretch · comfort and movement · care and durability.
- Possible MyantX contribution
- MyantX typically develops the textile structure, materials, and interface geometry.
Evidence belongs to the configuration tested
Specific studies, products, and regulatory pathways demonstrate how the architecture has been implemented. Each result or status applies to the material, system, or product tested or commercialized.
The architecture in a current SKIIN™ cardiac-monitoring implementation
A SKIIN™ product — its form factor, function, active Platform layers, maturity, and availability. The exact product and its details are confirmed on the Products pages.
A 3D-knit dry-electrode ECG study
A 3D-knit dry-electrode ECG study evaluated identified textile-electrode constructions against clinical gel electrodes, including performance after repeated washing. The implementation exercised the textile-interface, sensing, interconnection, electronics, and integration concerns. Full methods, results, and limitations are provided on Research.
Review the researchA Health Canada–licensed Class II product
SKIIN™ Connected Garments hold Health Canada medical device licence #106352 (Class II), held by Myant Inc. The licence applies to that identified product and intended use — not the Platform. Full status is maintained on Quality & Standards.
Quality & standardsBuild on the layer your product needs
Most programs begin at one layer or one boundary. Select where you are, and see what to bring, what may result, and the recommended path.
What needs to move forward?
- What to bring
- The product concept, the function it must perform, the form factor, and the systems it must connect with.
- Potential program outputs
- A layer-by-layer architecture, an integration boundary, and a development plan.
Connected-product architecture programs are typically scoped through Textile Computing™, with Analytical Testing and Scale-Up & Manufacturing supporting where required.
What needs to move forward?
- What to bring
- The product concept, the function it must perform, the form factor, and the systems it must connect with.
- Potential program outputs
- A layer-by-layer architecture, an integration boundary, and a development plan.
Connected-product architecture programs are typically scoped through Textile Computing™, with Analytical Testing and Scale-Up & Manufacturing supporting where required.
External integrators are part of the architecture
The layer boundaries above are designed to be built against. Partner organizations can create products on the platform — bringing their own electronics, software, or service layer to a defined interface, with development kits and integration scoping provided as part of a program engagement. Within Myant Health, the data-and-software layer operates under the HumanOS name; for partner programs, the equivalent responsibilities are defined per engagement.
Define the architecture behind the connected product
Bring MyantX the interface, function, form factor, and systems the product must connect with.