Home  /  OEM/ODM
OEM/ODM Delivery

Smart-glasses OEM/ODM from concept to MP, with clear gates and accountable owners.

SmartXY reduces AI/AR smart-eyewear development risk through requirement freeze, platform selection, optical co-design, DFM, validation and mass-production governance.

Models
OEM · ODM · JDMBuild-to-print → platform customization → custom engineering
Governance
IPD + AgileEVT · DVT · PVT · MP gates
OEM timeline
1–3 monthsBuild-with-logo
ODM timeline
6–9 monthsCustomization
Engagement Model

Choose the right path: OEM, ODM or JDM.

The fastest route is not always the safest. The right model depends on how much of the product definition, platform architecture, optics, software and IP you already own.

OEM

Build-with-logo

You bring the custom logo, package design, and APP animation; SmartXY delivers DFM, sourcing, manufacturing, QC and shipment.

  • Best for: SmartXY production-ready models
  • Focus: Fast local market pilot test, cost, yield, and delivery reliability
  • IP: design owned by SmartXY
  • MOQ: 500-1K units
ODM

Catalog Customization

Start from a pre-validated SmartXY series, then customize POC, PRD, ID/CMF, CNC Function Prototype, UI, firmware protocol/app, regional certification, and packaging.

  • Best for: the best fit to the local market
  • Focus: platform reuse with light customization
  • IP: SmartXY platform + your brand layer
  • Commercial: NRE + Tooling Mold + Production
JDM

Custom Engineering

Co-engineer a differentiated product on a SmartXY base platform — hardware options, chips, optics, firmware/app scope and regional compliance defined per project.

  • Best for: differentiated, category-defining launches
  • Focus: deep, controlled customization
  • IP: jointly defined, with clear boundaries
Capability Ladder

A seven-step smart-eyewear delivery system, from definition to MP.

01

Requirement freeze

Market scope, specs, ID/CMF, certification, budget and launch schedule.

02

Architecture

Chipset, OS, power, camera/audio, optics, SDK/API and OTA plan.

03

ID / MD / HW / SW

ID, mechanics, electronics, firmware, app and algorithm interfaces.

04

Prototype

CNC, 3D print, PCB/FPC samples, dev boards and interaction validation.

05

EVT / DVT

Functional, DFM, optical, electronic, acoustic, thermal and reliability validation.

06

PVT

Trial build, process validation, yield metrics, reliability reports and certification.

07

MP release

Yield ramp, ERP/MES traceability, QC plan, packaging, logistics and lifecycle.

IPD + Agile

Stage-gate rigor with fast weekly execution.

SmartXY uses an IPD-inspired lifecycle adapted for lightweight, high-speed smart-eyewear projects. Each phase has entry/exit criteria — when criteria are not met, the project does not move forward blindly.

Project initiationFeasibility studyPlanningDevelopmentVerificationLifecycle management

Phase gates that protect time, cost and quality.

01

Concept & planning

Cross-domain co-initiation across acoustics, optics, electronics, software, hardware, structure and supply chain.

02

Development

High-frequency prototype iteration with DFM embedded before design lock.

03

Verification

EVT, DVT and PVT gates establish KCP controls to pre-identify and mitigate risks.

04

Mass production

Trial-production review, yield ramp-up, test-tooling finalization and MP execution.

Customer Co-Development

Not only a supplier — a technology partner with transparent decision-making.

For strategic programs, the most important deliverable is a traceable decision system that lets both teams see risks early and close issues fast.

End-to-end process sync

Requirement intake, solution design, key-device selection, development and testing validation are fully visible.

Joint solution review

Customer participation in architecture, interface definition, BOM decisions and optical/HW/SW routing.

System alignment

Drawings, documentation templates, code specs, material control, version management and test standards.

Dedicated interface owners

A dedicated PM and technical lead per project to reduce cross-department communication overhead.

Delivery objectives

Progress visibility, risk controllability, clear accountability and traceable milestones.

One traceable system

Decisions, risks and versions visible end-to-end — the core of low-risk co-development.

Communication Cadence

High-frequency, transparent and closed-loop control.

Hybrid development model combining IPD rigor with Agile responsiveness.
Weekly synchronization on progress, risks, shared understanding and action plans.
Cross-functional reviews across mechanical, hardware, software, optics and supply chain.
Transparent reports: progress, risk register, version history, issue and prototype status.
Dedicated program taskforce with centralized allocation of high-priority resources.
Same-day response for critical issues and closed-loop resolution ownership.
Software Co-Development

Progress, bug and version control aligned with customer systems.

Daily development plans, weekly project sync, technical review, monthly retrospective, code review, release review and version change logs with impact scope, timing and rollback strategy.

Requirements reviewDesign reviewCode walkthroughTest reportsRelease reviewAPI co-creationComponent library managementVersion naming conventions
IP & Data Protection

Clear IP boundaries, code isolation, delivery encryption and privacy-by-design.

01Standardized R&D process

Requirements → proposal → design → test → MP review with full-process documentation and version control.

02Legal safeguards

NDA, software copyright and IP-ownership agreements define cooperation boundaries before deep development.

03Access control

Role-based access control, permission hierarchy and immediate revocation upon personnel departure.

04Code isolation

Dedicated code repository per client project with strict isolation from other projects.

05Environment isolation

Independent development, testing and delivery/release environments.

06Delivery protection

SDK and core algorithms protected via obfuscation, encryption and anti-reverse-engineering.

07Audit & traceability

Logging of code access, download, commit and artifact transfer for a complete audit trail.

08Privacy architecture

Data minimization, least-privilege access and on-device processing for sensitive data.

ERP + MES

Manufacturing transparency from supply chain to delivery.

Supply chain mgmt

Cost analysis, order approval, procurement, inventory and quality control.

Production mgmt

BOM, materials, orders, inspection, warehousing, replenishment and reports.

Digital production

Full traceability, error-proofing and key-parameter logging via one-item-one-code.

ERP + MES sync

Procurement, production, quality, warehousing and delivery transparency.

Typical Timeline

OEM 1–3 months · ODM 6–9 months · JDM scope-dependent

Timeline depends on optical complexity, certification scope, tooling, firmware/app/cloud integration and requirement-change discipline. The earlier requirements are frozen, the lower the downstream cost and schedule risk.

StageKey output
ID designConcept, 3D, CMF and wearing experience
Mechanical structureStack-up, hinge, IP-rating strategy and ergonomics
HW + SW developmentSchematic, drivers, app, SDK/API and OTA
Prototype & validationCNC, 3D print, tooling validation and reliability tests
Manufacturing releaseSMT, assembly, QC, PVT, yield ramp-up and MP release
FAQ

OEM/ODM questions before starting a program

What is the difference between SmartXY OEM and ODM?+
OEM is build-to-print production based on your design and specification; ODM uses SmartXY's validated platform library with customization across branding, CMF, firmware, app, packaging and regional certification.
What is the typical smart-glasses ODM development timeline?+
A typical ODM project may take around 6–9 months depending on optics, tooling, firmware, certification, app/cloud scope and requirement changes.
Which project gates does SmartXY use?+
An IPD + Agile mechanism with concept & planning, development, verification, trial production and mass production stages, including EVT, DVT, PVT and MP-readiness gates.
What should a customer prepare before starting?+
Target market, product definition, expected volume, launch timing, ID/CMF direction, optical route, chipset preference, app/cloud scope, certification markets, privacy requirements and commercial constraints.

Ready to convert your smart-eyewear concept into an executable launch plan?

Prepare your product definition, target market, expected volume, launch timing, target BOM and certification markets — we'll help choose the right OEM or ODM route.

Request launch plan →