Optional evaluation questions — answer what you know Leave any answer blank or write “Unknown”. For an answer you provide, include the responsible role, available evidence and open issue where useful. Requested quantity and timing do not confirm our MOQ, availability or delivery commitment. Editorial guidance only. No author-run device test or product performance result is reported. Review what to agree before a pilot .
Who pays and who approves?
Input sources and processing dependenciesWhat will supply the live input, and where will each processing step run? Identify prepared samples versus live input, the input device, local or remote processing and required or prohibited phone, network or cloud services.
Users, task and runtime conditionsWho will use the product, for which task and in which environment? Name a primary user, concrete task, setting and acceptance owner. Include workload, required runtime and charging opportunities.
Offline operation and recoveryWhat must happen when a request fails, is cancelled or arrives twice? Describe the expected response, repeat handling and observable outcome. What must remain usable after disconnection, reconnection or power loss? Specify recovery, retained state and power-loss behavior separately. A reconnection check does not establish permanent storage or long-term reliability.
Configuration to evaluateWhich hardware, operating systems and software versions must work together? Identify hardware, phone OS, application, SDK and firmware versions; leave unconfirmed combinations unknown.
Acceptance evidenceWhat observable result and measurable limits will define success? Name the observable task outcome, correct-output criteria, completion-time or recovery limits, test method and responsible owner.
What pilot quantity and timing are you considering? Pilot quantity Pilot quantity natureNot yet defined Evaluation request Quotation quantity tier; not an order Existing order reported by customer; confirmation pending Planning estimate Non-binding forecast Customer-approved plan; not a supplier order Timeline (optional)
For optional data-handling, support, budget and stop conditions, open “Optional platform, application and commercial details” below and use Requirements / evaluation workflow.
Optional platform, application and commercial details Product (optional)
Select a platform K900 AI camera glasses AR99 display glasses C100 EVT3 camera + display prototype AR99 MY AR99 Pro — EVT3 prototype Audio 01 — ODM project Other platform / help me choose
Purpose (optional)
Choose your next step Standard SDK access Paid sample evaluation Standard-platform branding / purchasing Custom development / integration Still exploring / need engineering assessment
Application task (optional)Not yet defined Own-App visual AI terminal Camera-free lightweight HUD First-person data capture system Retail product for your brand Industrial task and field operations Audio-only eyewear
Identify the hardware / firmware version if you have a unit, your phone OS, and the workflow you want to verify. Package availability, version, licence and supported interfaces are confirmed for that configuration; SDK access does not include firmware changes, app development or source-code rights.
Request the free standard C100 Android SDK / Demo by email . No paid brief is needed. There is no C100 iOS SDK or Demo. Opening this link creates a draft, not a delivery confirmation.
Describe the task, requested sample quantity and delivery country. Hardware sample cost, shipping, taxes and any agreed support are confirmed separately. C100 is an EVT3 prototype; access and timing require project review.
An initial brief can have an undecided platform, budget, quantity or date. We first review fit and missing engineering inputs. This is not confirmation of sample availability or project acceptance.
Tell us the quantity, market and branding changes (logo, colour or packaging). Standard-platform purchasing can be coordinated by your business owner. Software, certification and engineering changes are scoped separately.
Custom development scope
Custom work requires a development budget and a technical counterpart, either your team or a nominated partner, before work can start. You may leave these undecided for an initial brief. Feasibility, NRE, tooling, certification, licensing and delivery are confirmed by written scope; submitting a brief does not approve a project.
Engagement modelODM customization Joint development / JDM Technology transfer Enterprise integration
Development budget / range and currency (if known)
Technical counterpart / nominated partner (if known)
Application owner (optional)
Cloud or AI service owner (optional)
Connection path to evaluateNot yet defined Phone App as gateway Direct device network connection Compare both paths Offline task / local transfer
Target operating system / business system (optional)
Interfaces needed (optional)
Channel or deployment capability
Camera policy (optional)Not yet defined Camera is required Camera is optional Camera is not needed Camera is prohibited Not yet sure Display requirement (optional)Not yet defined Display is required Display is optional No display required Short text or captions Text and graphics Not yet sure
Task requirements for engineering review
These are your requested conditions, not confirmed product capabilities. Answer what you know; unresolved details can be reviewed later.
Actual workload / shift conditions
Software integration responsibility Software teamNot yet defined In-house development team Nominated integration partner Software support needs scoping No software team currently Complete App and service needed App / server and service responsibility
Specify prohibited data paths in the acceptance details or request notes. Interface availability, commercial rights and maintenance ownership require separate agreement.
Camera-free display workflow
HUD taskNot yet defined Pure display / prompts from own App Audio-to-caption workflow Both workflows need review
Captioning also needs an agreed audio source, recognition / translation service and phone or host integration. A display alone does not establish that workflow.
Visual input
Capture patternNot yet defined Event-triggered photos / clips Continuous stream Offline recorded video Both modes need review
Capture workload
Data and acceptance requirements
Task / data / latency / synchronization criteria
Data rights and handling
Optional quantities by stage — customer requirements, not an order
Record sample, pilot and production quantities separately; do not add them together. Quantities and dates do not confirm inventory, MOQ, capacity or a delivery commitment.
Sample quantity Sample quantity natureNot yet defined Evaluation request Quotation quantity tier; not an order Existing order reported by customer; confirmation pending Planning estimate Non-binding forecast Customer-approved plan; not a supplier order
Production quantity Production quantity natureNot yet defined Evaluation request Quotation quantity tier; not an order Existing order reported by customer; confirmation pending Planning estimate Non-binding forecast Customer-approved plan; not a supplier order
Budget status (optional)Not yet decided Awaiting approval Budget allocated Need a scoped estimate
Country / region
WhatsApp / WeChat (optional)
Overall quantity / existing estimate (optional)
Project type
General platform inquiry Embodied AI / robotics data capture platform C100 EVT3 prototype / SDK evaluation New accessibility ODM project (Confidant reference) New field-operation ODM project (007 Pro reference)
Confidant and Falcon 007 Pro are historical project references, not overseas-ready products. Original systems are not available for sample dispatch or testing. Similar applications require a new ODM project with NRE (non-recurring engineering), development time and project budget; scope, fees and schedule are agreed per project.
C100 is at EVT3. The unchanged standard Android SDK and Demo are free for evaluation and self-development. SDK modifications, feature changes and special requirements require NRE development fees starting at USD 3,000, paid before modification work; final fees depend on agreed scope. No iOS SDK or Demo is provided. This is a development-service fee, not a hardware price.
Capture project requirements Capture modality Downstream use
Requirements / evaluation workflowWhat data, access permissions and handling rules will the pilot require? Describe data sources, permissions, processing and storage locations, access, retention and deletion requirements. No sensitive records or credentials. What budget, support commitments and stop conditions apply? State the budget decision owner, external services and recurring charges, support owner, test budget and conditions for pausing the pilot. These are requirements for review, not agreed commercial terms.
A received request is pending review; it is not a quotation, project approval or delivery commitment.