<slug>.cskn.app), on its owner’s profile (<username>.cskn.my/<slug>), inside the native mobile and desktop shells, and on TV. Two packages make that one codebase work everywhere.
@cskn/sdk
Talks to the platform. Reads the data the host injects, signs you in, calls the cskn API, and reaches native features (camera, storage, notifications, passkeys and more) through the shell’s bridge.
@cskn/ui
A platform-aware component kit. Behavior primitives (safe area, native header, keyboard avoidance, TV remote navigation) plus an optional themed skin you can recolor to your brand.
How the pieces fit
- The host writes app data into
window.csknbefore your code runs, and a native shell also attaches a message bridge atwindow.cskn.bridge. - @cskn/sdk reads both, and every native call degrades safely, or tells you clearly, when there is no bridge.
- @cskn/ui builds on the SDK’s platform information to pick the right behavior on each surface.
Where to start
Quickstart
Scaffold an app and render your first screen.
Surfaces
Understand where your app runs and what changes between surfaces.
Authentication
Get the signed-in user on every surface.