A DESIGN LANGUAGE BY SIMT
Warm depth. Clear signals. A little wonder.
Interfaces that make the next step feel natural.
v2.4.0 · Normative specification Shared foundation + four platform parts. Updated .
SAME COLORS. A RICHER COMPOSITION.
The Cosmos idea stays: you are the center of your universe. The new system gives it a precise visual grammar—an aperture for attention, a spine for context, a horizon for time. It creates continuity without making every screen look the same.
One common contract governs color, type, accessibility and meaning. Four platform parts translate it into distinct experiences.
Frame one meaningful object.
Where you are. What comes next.
Time and distance, made legible.
Eight gradients drawn only from the Deep Space anchors. Each has one job, so depth reads as meaning instead of decoration.
Root depth behind every Deep Space screen. Opaque, so text is measured against void-edge and void.
One atmospheric field per screen, behind the focal object or a section entry; never behind reading text.
The only glow: the halo of the single focal object, painted in a box four to six times its diameter.
A 1–2 px ring around the focal object. Never progress, status or a control outline.
Light lines of 1–2 px: the top light of a surface, the horizon ribbon, a section signature.
A 1 px border light for the focal or selected surface, beside its essential boundary rather than replacing it.
Fill of the one primary action. The Void label passes on every stop.
The brand signature line. Category legends use solid labelled swatches instead.
Each platform earns its own composition, density and rhythm.
01 / WEB PAGE
Based on simt-social-landing. Create an invitation to real places and real people, with an open editorial composition and a glimpse of the product that feels usable.
Open web page specificationYOUR NEXT GOOD MOMENT
Go somewhere.
Find your people.
A walk, a shared sunset, an idea.
Real moments start nearby.
02 / WEB APP
Based on simt-social. The map establishes where; an aligned stream explains what; a context spine keeps the next decision close. The shell stays predictable while the experience becomes richer.
Open web app specificationToday, 18:30
Riverside · Approximate place
03 / MOBILE APP
Based on simt-app. Put the reading in a stable reference frame, the explanation beside it and the command under the thumb. A sense of wonder follows precision.
Open mobile app specification01 A stable context
02 One clear reading
03 Commands within reach
04 / WATCH APP
Based on wear inside simt-app. Keep the warmth, remove the spectacle. One reading, one qualifier, one action: enough information to act without asking for sustained attention.
Open watch app specificationTHE PRODUCTION CONTRACT
Loading, empty, denied, stale, offline, conflict and success have explicit behavior.
Readable contrast, full input support, large text, logical RTL and reduced motion.
Asset budgets, frame pacing, lifecycle ownership and named release evidence.
The web product and the mobile product are built on this specification. Conformance is recorded rule by rule in a release record; examples use illustrative data.
BUILT FOR IMPLEMENTATION
All five pages and every rule are generated from one source. Load the common contract, then the platform you are building.
USING COSMOS
One shared foundation and four platform parts: web page, web app, mobile app and watch app. Each platform inherits the common requirements and adds its own composition, input and release criteria.
No anchor color changed. The Deep Space surfaces and Ember, Rose, Violet, Gold, Cyan and Moss anchors are retained. Version 2.1 adds eight gradients and a deterministic star layer built only from those anchors, and version 2.2 makes the semantic profiles the single definition of a surface: light, astronomy red and watch ambient publish their own role values instead of leaving a component to read an anchor and guess.
Yes, where a platform draws them. The star layer is generated from a surface ID and size bucket by a published algorithm with a parity fixture, so web and Android produce the same sky. Watches, maps, sky charts and data never draw one.
Yes. The web product and the mobile product are built on it, and the platform mapping was authored as the target they were brought to. That makes the mapping the source they conform to rather than a description of them, so a product that diverges from a published value is the one out of date. Conformance is still recorded rule by rule: the release record names the build, the rule IDs it carries and the evidence, and accessibility, performance and device acceptance are measured on each implementation. The examples on these pages use illustrative data.
Load the manifest, common part and relevant platform part. Map applicable rule IDs to a screen brief, use exported tokens, implement the supported data and state contracts, then attach real release evidence.
