Package your watch face for review.

Device variants

A multi-package submission is one watch face with shared listing details. Prepare a separate ZIP using the format below for each device family that needs different assets or project settings, and assign each watch model to exactly one ZIP.

Outer ZIP

your-face.zip
├── coroslink-project.json
├── your-face.dat
└── preview.png (optional)

Use root-level files only. Include exactly one manifest and one DAT archive. The outer ZIP, root project manifest, and root DAT may each be up to 100 MiB, subject to the 130 MiB total-expanded limit. Extra files, folders, encrypted entries, nested archives, and unsafe paths are rejected.

Manifest fields

• format: coroslink-watchface-project
• version: a positive integer for the envelope format
• name: the project name
• firmwareType: the target firmware family
• sourceTemplateId: the source template identifier
• design: the original design metadata exported by the authoring tool

DAT archive

The DAT file is itself a ZIP-compatible archive. Its validated contents may expand to 200 MiB, with each member capped at 5 MiB. It must contain info.json, watchface_customize.png, and at least one watchface_WIDTHxHEIGHT directory with config.txt and PNG assets.

The values in info.json must match the archive: m_app names the watch-face directory and m_preview is watchface_customize.png.

What happens after upload

1. The package remains private in quarantine.
2. Archive limits, file paths, structure, malware, and images are checked.
3. Passing packages enter moderation. A moderator may reject inaccurate metadata or unsafe content.
4. Only approved packages can be published.

The manifest template documents the envelope but is not a complete watch face. Export the DAT and imagery from your COROS-compatible authoring workflow.