Launcher
Play, instances, versions, loaders, runtimes, content, migration, repair, downloads and release management.
CONNECTED PLATFORM
One ecosystem.
Clear boundaries.
Leviathan connects Web, Launcher, Client, Mobile and TV through shared identity, public data, support and discovery systems without turning every product into the same browser shell.
Leviathan Platform
Connected, not tangled.
Shared truth, device-native presentation.
PLATFORM COREIdentity + services
Web · Launcher · Client · Mobile · TV
IDENTITYVerified
PUBLIC APIV1
DESIGNShared
PLATFORM LAYERS
Everything has a place.
The goal is a coherent experience where each product shares terminology, states, content and design language while keeping the interaction model appropriate for desktop, mobile, in-game and ten-foot TV interfaces.
Client
Performance, modules, HUD profiles, accessibility, cosmetics, social and connected in-game features.
Mobile
Social, Wardrobe, Capes, Leaderboards, Servers, Downloads, Devices & Cast, Wallet, Notifications, Support, Security and Settings.
TV
Remote-friendly Home, Cast, Wardrobe, Capes, Discover, Leaderboards, Servers and Settings with clear focus navigation.
Identity
Leviathan account, verified Minecraft ownership, profile continuity, ranks and privacy controls.
Support
Error codes, diagnostics, private tickets, public bugs, known issues and lifecycle updates.
Discovery
Profiles, capes, leaderboards, servers, status, news and useful platform search.
Community
Forum, articles, creators, localization, feedback and contribution pathways.
SHARED PLATFORM API
Capes and leaderboards should not be rebuilt five times.
The versioned public API now provides the shared content and surface manifest used by Web, Launcher, Client, Mobile and TV. A client asks for its surface and receives consistent navigation labels, capabilities, design tokens and public content endpoints.
1BootstrapRequest
/api/v1/bootstrap?surface=launcher, mobile or tv.2Shared contentCapes, profiles, textures and leaderboard data come from the same backend.
3Native renderingApps render Leviathan UI themselves instead of embedding the website inside a browser.
4Offline safetyClients can cache public catalog data and the last-known manifest for degraded states.
Surface manifestAPI v1
L
LauncherCapes · Leaderboards · Servers · Store
SharedM
MobileWardrobe · Cast · Wallet · Support
NativeTV
TVFocus navigation · Cast · Discover
10-foot UIAPI
Public contentVersioned and cacheable
V1VERIFIED IDENTITY
Prove ownership without exposing secrets.
Account linking uses the user’s own Microsoft and Minecraft authentication flow. Passwords and service tokens do not belong in Discord, public profile pages, TV storage or public API responses.
1LinkStart from Leviathan with a short-lived challenge.
2VerifyConfirm Minecraft ownership and stable UUID identity.
3ControlManage visibility, unlinking and safe transfer flows.
Identity recordPrivate by default
✓
Minecraft UUIDStable profile identity
Verified✓
Ownership methodRecorded without password storage
Safe◫
Public profileUser-controlled visibility
OptionalOPERATIONS
The boring parts should be excellent.
Updates, telemetry, support, diagnostics, service health and API compatibility are part of the product experience, not afterthoughts.
Release engineering
Versioned releases, checksums, staged channels, rollback and transparent changelogs.
Diagnostics
Stable error codes plus separate crash and correlation IDs with original errors preserved.
Telemetry governance
Collect useful product signals with purpose, retention and privacy boundaries instead of uncontrolled event sprawl.
API compatibility
Versioned public schemas, capability discovery and graceful fallback when a client is older than a backend feature.
COMMUNITY LAYER
Players should know where to go.
Feedback, bugs, support, localization and creator participation use separate workflows that still connect back to the same Leviathan identity.
One platform, purpose-built surfaces.
Shared API data keeps Leviathan consistent. Native apps keep it fast and appropriate for the device.