# Framework guides

One SDK per platform, but a tailored install path for every framework. Rather than adapt a generic snippet, pick your stack and get the exact provider, hook, or middleware it expects.

Source: https://cross-deck.com/university/framework-guides/
Verified Crossdeck University lesson — prose plus real, runnable code.

## Same SDK, idiomatic to your framework

The same web SDK powers Next.js, React, Vue, Svelte, and plain HTML — but each framework has its own idioms: a provider here, a composable there, a route guard, a piece of middleware. A generic snippet would make you do the adapting. Instead, Crossdeck ships a tailored guide per framework, so you copy the version that already speaks your stack's language.

## Pick your framework on the SDKs page

In the dashboard, open the SDKs page and choose your framework. The stable, supported paths today:

## One package per platform, many doorways in

The structure is simple once you see it: there's one package per platform — @cross-deck/web for the browser, @cross-deck/node for servers, the Swift Package and @cross-deck/react-native for mobile — and each framework guide is just the idiomatic way to wire that package into that stack. You're not learning a different SDK for Vue than for React; you're getting the Vue-shaped doorway into the same web SDK.

And the map keeps growing: Angular, Python, Ruby, Go, and Flutter are on the roadmap, each bringing the same entitlement-grant and verification model to its ecosystem. If your framework's guide isn't there yet, the underlying package usually still works — the guide just makes it idiomatic.

## An install path that fits

Pick your framework, copy the path that's written for it, and you skip the "how do I adapt this to SvelteKit?" detour entirely. That's the end of Server & frameworks — and the end of the build side of Crossdeck.

your framework, tailored
 Next.js, Express, Cloudflare Workers, Expo — each with the provider, middleware, or hook it expects, all from one package per platform.