---
summary: Developer guide for choosing SigID SDK packages, example applications, and integration paths across frontend, backend, mobile, and desktop runtimes.
tags:
  - developers
  - sdks
  - examples
  - integration
categories:
  - For Developers
---

# SDKs And Examples

<!-- agent:page
You are a coding agent choosing the right SigID package for the user's runtime before integrating.
First determine the runtime from the workspace (framework, package manager, frontend vs backend), and collect the usual app configuration from the workspace admin: issuer URL, client ID, redirect URI, scopes, API audience, and tenant.
Pick from this page's tables: @sigid/client for browser TypeScript; @sigid/react, @sigid/vue, @sigid/solid, @sigid/svelte for frontend frameworks; @sigid/next, @sigid/sveltekit, @sigid/solidstart for full-stack frameworks; @sigid/expo and @sigid/electron for mobile and desktop; sdks/go, sdks/rust, sdks/elixir for backend languages.
For languages without an official SDK, use standard OAuth/OIDC libraries with the deployment's API reference.
Then follow the matching quickstart end to end (quickstart-nextjs.md, quickstart-react-spa.md, quickstart-backend-api.md, or run-example-app.md) in the recommended order: quickstart, SDK closest to the app, backend token verification, per-route protection, then webhooks or agent auth only if the product needs them.
Start with hosted-login helpers; do not hand-roll OAuth where a helper exists, and do not install packages for runtimes the project does not use.
-->

Use this page when you need to pick the package closest to your app runtime.

Start with hosted-login helpers. Use low-level OAuth helpers only when your app
needs full protocol control.

## Start By Runtime

| Runtime | First guide |
|---|---|
| Next.js App Router | [Next.js Quickstart](quickstart-nextjs.md) |
| React SPA | [React SPA Quickstart](quickstart-react-spa.md) |
| Backend API only | [Backend API Quickstart](quickstart-backend-api.md) |
| Local working example | [Run The Example App](run-example-app.md) |

## Choose An SDK

<!-- agent:action Pick and install the SDK
Inspect the workspace to identify the runtime (framework config, package.json, go.mod, Cargo.toml, mix.exs), then install only the matching package from this table: hosted-login helpers like @sigid/next or @sigid/react for frontend/full-stack, or the sdks/go, sdks/rust, sdks/elixir paths for backend languages.
Frontend frameworks also need @sigid/client as the underlying browser client.
Confirm the choice with the user if the repository contains multiple runtimes.
-->

| Runtime | Package or path | Use it for |
|---|---|---|
| Browser TypeScript | `@sigid/client` | Hosted login, callback handling, logout, and client session helpers. |
| React | `@sigid/react` | React hooks and session state. |
| Vue | `@sigid/vue` | Vue composables. |
| Solid | `@sigid/solid` | Solid primitives. |
| Svelte | `@sigid/svelte` | Svelte stores. |
| Next.js | `@sigid/next` | Route handlers, server integration, and access-token helpers. |
| SvelteKit | `@sigid/sveltekit` | Hooks and server load integration. |
| SolidStart | `@sigid/solidstart` | Routes and server functions. |
| Expo | `@sigid/expo` | React Native / Expo storage and redirects. |
| Electron | `@sigid/electron` | Electron main/renderer authentication helpers. |

## Backend SDKs

| Runtime | Directory | Use it for |
|---|---|---|
| Go | `sdks/go` | Go services, CLIs, and infrastructure tooling. |
| Rust | `sdks/rust` | Rust services and security-sensitive integrations. |
| Elixir | `sdks/elixir` | Phoenix, BEAM services, and server-side integrations. |

For languages without an official SDK, use standard OAuth/OIDC libraries and
the API reference for the deployment.

## Example App Path

Use [Run The Example App](run-example-app.md) for a runnable walkthrough of
`examples/sdk-lab-next`. It demonstrates:

- browser setup with `@sigid/client`
- hosted login with `login()`
- callback handling with `handleCallback()`
- logout with `logout()`
- protected Next.js routes
- server-side token validation

## Recommended Order

1. Start with the quickstart that matches your runtime.
2. Use the SDK closest to your app.
3. Verify tokens on your backend.
4. Protect each API route or resource.
5. Add webhooks or agent auth only if the product needs them.

For the full API surface, continue to
[Reference: API And SDK Reference](../reference/api-sdk-reference.md).