01 / PRODUCTS & DIGITAL CONNECTIONS

Products & digital connections

Each touchpoint has its own job. Connection should still make it clear where you are and what you can do.

01

Ami robotics

Embodied connection

Explore ways of relating beyond the screen through sound, movement and shared space.

Development result · See official capability informationExplore
02

WeChat mini program

A lightweight touchpoint

Discover Ami on a familiar platform; consult the mini program for its actual pages and services.

Official QR availableExplore
03

Ami app

Connection on the move

Explore mobile interaction and product connection with understandable preferences, status and controls.

In development · Features and download unannouncedExplore
04

Brand & content channels

Understanding & expression

Use brand stories, articles and film to explain ideas while distinguishing official information from concepts.

Content channels / Brand website URL unconfirmedExplore
05

Product store & support

From discovery to use

A future connection between product information, purchasing guidance and support; transaction and after-sales terms require separate publication.

Development direction · No transactions on this siteExplore
A POSSIBLE CONTINUITY

A connection with a beginning—and an exit

Experience principles for the future, not a working feature flow.

  1. 01

    Choose

    Let the person choose where to begin.

  2. 02

    Explain

    Explain purpose and scope before linking information.

  3. 03

    Make visible

    Make connection status understandable.

  4. 04

    End

    Make room to pause, disconnect or ask for help.

Connection is not automatic sharing.

Website enquiries, mini-program accounts and future device services are distinct contexts. This page does not claim that unified accounts, cross-device memory or automatic synchronisation exist; each product needs its own explanation.

Support should grow with the product.

Future support could include onboarding, feedback, maintenance guidance and content updates. Responsible entities, scope and processes must be defined before those services open.