App, Cloud & AI

The wearable continues
in software.

Hulin develops the software around a connected wearable: iOS and Android apps, device communication, backend services and project-specific AI integration.

Start a Project
Two views of a rectangular wearable with a black woven wrist strap and no visible screen.
On the bodyWearable hardware reference
Original Chinese wearable app overview showing device status, daily goals and health-information tiles.
In the appDevice status and everyday information
Original Chinese sleep-detail screen with a stage timeline, period controls, duration breakdown and data settings.
Across timeSleep detail and period-based reviewView complete source screen ↗

Supplied wearable and app references; compatibility is defined per product. Original Chinese interfaces are preserved. On-screen values are examples, not performance claims.

Wearable software experience

DeepFit.
DeepFit Pro.

Real app experience informs the everyday details: connecting a device, presenting information and helping people return to the product.

For a new program, the app, backend responsibilities and integration scope are defined around your wearable.

From an overview to the detail.

The supplied overview brings device status, daily goals and health records into one place. A dedicated sleep view provides a timeline, summaries and daily, weekly or monthly review.

Make the connection understandable.

Binding, synchronization, settings and firmware updates need clear behavior in the app. Interrupted transfers and unavailable devices are part of the design brief.

The supplied health interfaces are software references. Supported measurements and intended use require product-specific validation.

Original Chinese activity app screen showing activity selection, a map, a start control and dated session history.
Original activity interface / supplied example data.
The map does not establish wearable GPS capability.

A session becomes a record

Useful now.
Findable later.

The activity interface connects a starting point with a history of sessions. Its information stays organized around the activity and the time it happened.

Choose the activity
Activity types and a visible start control establish the task.
Keep the context
Dated records retain session type, duration and associated activity information.
Return to the record
History gives the user a way back to earlier sessions, beyond the live device experience.
Health Wearables

One product / coordinated responsibilities

What makes the experience work.

The interface is visible. Device behavior, services and data decisions keep it connected to the product.

01On the device

Capture and retain the right data. Make connection state, local storage and firmware behavior part of the product definition.

Firmware · BLE · local state
02In the app

Guide setup, device binding and everyday use. Handle interrupted connections, synchronization and updates with clear user feedback.

iOS · Android · device experience
03Across the backend

Coordinate accounts, device records, storage and APIs. Define access, data lifecycle and operational responsibility early.

Services · APIs · data management
04With intelligence

Connect selected AI services to a useful product workflow, with explicit data boundaries, user control and a way to review the result.

Model integration · retrieval · agents

Architecture, data retention, service access and operational responsibilities are agreed per project.

AI-generated metallic pendant appearance concept, suspended from a necklace against a black background.
AI-generated appearance concept; not verified hardware.

AI with a defined role

From captured material
to a useful result.

Recording workflows may include transcription, summaries and structured output. Retrieval, RAG and agent workflows can be evaluated when the product needs to work with a wider body of knowledge.

Define the input, data permissions and intended result first, including where the user reviews or corrects the output. Then select the integration.

Depending on the project, integrations may involve OpenAI, Claude, DeepSeek, Qwen or Kimi. Service availability and behavior depend on the selected architecture.

Let’s build what comes next

Your next wearable. Together.

Tell us what you’re developing and where you need engineering support.

Prepare a short project brief, then open it in your email app to send to Hulin.

Prefer to email directly?
Your project brief
Product idea, intended use, engineering needs and any timing constraints. 20–2,000 characters.

Preparing a brief does not send it. Your email app handles delivery.