THOX Experience Fabric
One experience. Unmistakably THOX.
Familiar where it matters. Native where it counts. TXF brings our design principles, shared interactions and development standards into one experience layer — so THOX products feel connected, and you stay in control.
Your AI. Your Data. Your Rules.™
- 01
The products you use
ThoxOS and MeshStack across THOX devices, with ThoxWork Coming Soon.
- 02
TXF · the shared experience
Familiar navigation, clear states and explicit control over actions and data.
- 03
The design foundations
Shared color, typography, spacing and motion tokens, with platform-specific components.
Our philosophy
Built around the person using it.
The details matter: knowing where your work runs, finding a familiar control, reading a state at a glance. TXF turns those expectations into shared standards for the experiences we build.
- 01Ownership and consent
Ownership and consent
Start with local ownership. Before information crosses a device boundary, show what will move, where it will go and what the person is approving. Connecting an account is not blanket consent.
- 02Familiar, but native
Familiar, but native
Respect the host platform’s input, layout and accessibility conventions. Shared destinations adapt to desktop, touch and watch experiences instead of forcing identical pixels onto every screen.
- 03Accessible from the start
Accessible from the start
Readable contrast, meaningful labels, keyboard access, visible focus, reduced motion and generous touch targets belong in the design and component checks — not as an afterthought before release.
- 04Visible, truthful states
Visible, truthful states
Make loading, activity, interruption, errors and completion understandable. Use words and structure, not color alone. Give people a way to stop, recover and know what happened.
- 05Continuity, without unlimited access
Continuity, without unlimited access
Carry familiar context across authorized surfaces without granting unlimited access. A local-only choice must stay local: show missing capabilities clearly instead of silently sending work elsewhere.
- 06The same care, inside and out
The same care, inside and out
These expectations apply to the tools behind the products, too: provisioning, support, operations and release review. Internal users deserve the same clarity, accessible controls and accountable actions as customers.
These are shared design and development standards. Adoption and verification belong to specific builds and platforms — not a blanket claim that every THOX product is certified.
Interactive illustration — no account or device connection
The experience, one form factor at a time
Choose a form factor to explore the navigation defined by TXF 2.2. The destinations stay familiar while the primary navigation adapts to the screen. This is a local illustration — not a detected device, connected account or live application.
Form factor
Pattern: sidebar · All seven planes, always visible, in a persistent sidebar.
7 of 7 planes visible on desktop
Home
/Overview, what changed, and resuming work.
A status summary, what changed since your last visit, and resume points for anything you left open. On classes that hide planes, Home also hosts the overflow entry points.
Example commands for this surface
The shared command set stays consistent even when the navigation layout changes.
Across the THOX experience
From the framework to the screen.
Explore selected ThoxOS and MeshStack captures alongside earlier design previews. Each view highlights an interaction pattern and tells you exactly what the media shows.
Stills from selected ThoxOS and MeshStack desktop builds. On-screen labels describe the captured interface, not a live connection or a fleet-wide verification.
A clear starting point: status, recent work and setup belong together.
A decision you can see
Your choice comes before the action.
Try a local task, an authorized peer or a hosted destination. See where consent and review belong. This illustration uses synthetic local state: no file is read, no model runs and no request is sent.
- prepare
- consent
- review
- result
1. Prepare
Choose where this example task would run. Local skips external-sharing consent, but still requires you to review the proposed action.
Demo task: Summarize demo-notes.txt
How the experience is built
Design to delivery, one shared process.
Start with the journey, define the shared rules, generate platform resources and test them in the product. Inter and JetBrains Mono keep our website’s UI and technical text consistent; native surfaces can use their platform’s text conventions.
- Include loading, offline, error, consent and approval states. Designers, engineers and test authors should work from the same expected behavior.
- An artifact that builds is available to integrate. That alone does not prove a specific product uses it or has passed its interaction checks.
- A tested integration connects the shared resources to the actual application and its host conventions. Consistency does not require every screen to look identical.
- Record failures and resolve them before calling a build verified. Results for one platform or release do not automatically apply to another.
- Keep framework availability, product integration and verified behavior distinct. That is how a design promise becomes something a team can inspect and maintain.
Questions
Your AI. Your Data. Your Rules.™