# Reown AppKit: one chain agnostic core, eleven SDK targets, one license

> AppKit is Reown's toolkit for onchain app UX: a chain agnostic core published through eleven SDK targets, with wallet services such as swaps, on-ramp, and sponsored transactions on top. The repository is a pnpm and turbo monorepo of packages and 25 example apps, and the short readme leaves the wiring to hosted docs.

**reown-com/appkit** — The full stack toolkit to build onchain app UX

- Repository: https://github.com/reown-com/appkit
- Website: https://reown.com/appkit
- Stars: 5,447 · Forks: 1,653
- Language: TypeScript
- License: NOASSERTION
- Published: 2026-09-22 · Updated: 2026-09-22 · Language: en
- Canonical page: https://hysenlabs.com/projects/reown-com-appkit

## One chain agnostic core behind eleven SDK targets

AppKit presents itself as the full stack toolkit to build onchain app UX, and the published surface matches that claim better than a readme this short usually manages. Eleven SDK targets are linked, each with its own installation page: React, Next, Vue, Nuxt, Svelte, plain Javascript, React Native, Flutter, Android, iOS, and Unity. Having an Android target and a Unity target in the same list is the interesting part, because it means the wallet layer is packaged separately from the UI framework rather than being one React component library with a mobile port bolted on.

Underneath sits AppKit Core, marked chain agnostic, and the network coverage is named per family rather than per framework: EVM Chains, Solana, and Bitcoin, with Multi Chain as its own entry. The structure being described is a shared connection layer over pluggable network adapters. What the readme does not give you is the configuration surface for any of it, since it points at the Features section of the AppKit docs for what each capability does. From the repository you get the coverage matrix, not the settings.

## Swaps, on-ramp, and sponsored transactions are service features

Read the feature list as a list of services rather than a list of widgets. Swaps, On-Ramp, Smart Accounts, Sponsored Transactions, and Telegram Mini Apps sit beside the plumbing entries of Multi Chain, Multi Wallets, and Authentication, and the split matters. The first group needs a counterparty. An on-ramp turns fiat into tokens, a swap needs a route and a quote, and a sponsored transaction needs somebody else paying the gas. A toolkit that only embeds a connect button needs none of that, which is why a project that lists on-ramp next to smart accounts is selling a wallet plus a set of rails.

Authentication is named with more detail than the rest: Email & Social Login, and One-Click Auth & Sign with X (SIWX). That last label is worth reading slowly, because the acronym puts signing inside the login flow instead of next to it. The repository carries no key names, no provider list, and no setup snippet for any of these features. The examples directory is where a working shape is supposed to come from, and the readme points at a separate appkit-web-examples repository for that.

## The Community License makes the connection to Reown mandatory

The license is not MIT and not Apache, and that shapes who can use the SDK for what. AppKit ships under the Reown AppKit Community License, stored at the repository root as LICENSE.md, which the root package.json points at with SEE LICENSE IN LICENSE.md. Six areas are called out as governed: permitted non-commercial use, RPC and MAU thresholds for commercial licensing, required connection to Reown's proprietary infrastructure, redistribution and attribution obligations, ownership of modifications, and mandatory binding arbitration for disputes.

Three of those lines change what you are building. Non-commercial use is permitted, so a prototype or a side project is not the problem. Commercial use is measured against RPC and monthly active user thresholds, so the license meters rather than simply charging a flat fee. And the connection requirement means the SDK is expected to talk to Reown's own infrastructure, which is also the reason swaps and on-ramp can appear in a feature list at all. Downloading, installing, integrating, or using the SDK counts as accepting the license, and the dispute clause is binding arbitration rather than a court.

## Web3Modal users get a migration guide, not a version bump

The most consequential line for an existing project is a note, not a feature. If you are on Web3Modal v1 through v5, the readme sends you to a migration guide rather than telling you to raise a version number, and it links a page named for the move from Web3Modal v5 to Reown AppKit Web. The distinction is the point. Web3Modal was the earlier name of this product, and the naming change came with a different package scope, so a caret range bump will not carry an integration across on its own.

The published packages make that visible. Three names are cut and released together: @reown/appkit, @reown/appkit-wallet, and @reown/appkit-wallet-button, all at 1.8.24 on 2026-09-16. Anyone maintaining an existing Web3Modal integration should read the upgrade path before touching a dependency, because the mapping between old and new module names lives in that guide and not in the release notes.

## A pnpm and turbo monorepo holding 25 example apps

The build layout is a pnpm workspace driven by turbo, and the root package.json shows the shape without any prose. It is a private package named @reown/appkit-monorepo, type module, whose scripts fan out through turbo run build filtered to ./packages/**/*, with the default build explicitly excluding ./packages/cdn:

```json
  "scripts": {
    "prebuild": "node scripts/inject-version.js",
    "build": "turbo run build --filter={./packages/**/*} --filter=!{./packages/cdn} --concurrency=31",
    "watch": "turbo run watch --filter={./packages/*,./packages/adapters/*} --concurrency=50 --continue",
    "examples": "turbo run dev --filter={./examples/*}"
  }
```

Other scripts target single slices: build:sample-apps filters to the examples, laboratory starts the lab app, demo:dev and builder:dev both start the demo app, and there are per-example build scripts for the wagmi CDN, Vue, Parcel React, and Next app router examples. The examples directory holds 25 projects, and their names are the fastest map of the supported stack: html-ak-basic, html-headless, html-bitcoin, html-solana, html-ethers, html-wagmi, html-wagmi-cdn, html-wagmi-wallet-button, next-ak-basic, next-bitcoin, next-wagmi-solana-bitcoin, nuxt-wagmi, and parcel among them.

## Bundle size and review policy are config files, not prose

The quality gates are visible in the tree rather than explained anywhere. BUNDLE_SIZE_TRACKING.md and a .size-limit.js file at the root say that shipped weight is tracked, which matters for a widget every visitor's page loads, and the CDN package being excluded from the default build hints that there is more than one distribution shape. vitest.config.ts and vitest.workspace.ts handle tests, .eslintrc.json with .prettierrc.json and .prettierignore handles style, dangerfile.ts is a root level review configuration, and renovate.json is the dependency update path. Dockerfile.canary implies a container image exists for canary builds.

A patches/ directory means some dependencies are patched in place, and fix_parentheses.py next to it is a one-off maintenance script rather than part of the build. AGENTS.md, CLAUDE.md, .cursor/, and .agents/ show that the repository carries instructions aimed at coding agents, .changeset/ is where release notes are drafted, and status.json is a machine readable status file. pnpm-workspace.yaml, turbo.json, tsconfig.json, and the vite configs tie the pieces together.

## The monorepo says 1.7.1, the published packages say 1.8.24

Two version numbers in this repository describe different things, and telling them apart saves a confusing afternoon. The root package.json carries version 1.7.1 on a private package named @reown/appkit-monorepo: that is the workspace container, not anything you install. The version you consume comes from the published packages, and all three were cut at 1.8.24 on 2026-09-16, meaning @reown/appkit, @reown/appkit-wallet, and @reown/appkit-wallet-button move together. The build scripts also run scripts/inject-version.js before anything is built, which is the step that keeps a published artifact in step with its tag.

A third number is the one to watch in CI, since the Dockerfile is named for a canary image and a canary build can exist at a version that is neither 1.7.1 nor 1.8.24. The repository is not archived, and the last push to main landed on 2026-10-02, days after the 1.8.24 cut, so the published version is not the whole story either. The host project page is reown.com/appkit, and the documentation lives at docs.reown.com/appkit.

## The readme answers no configuration question at all

It is worth being explicit about the gaps, because a readme this short sends most questions to hosted documentation. At the top level of the repository there is no env sample, no chain list, no project ID constant, no API key name, and no theme file, and there is no framework setup snippet for any of the eleven SDK targets, only one link per framework. There is no version support statement, no browser matrix, and no note about what a user sees when the connection to Reown's infrastructure is unavailable at runtime, which is the failure mode a hosted wallet layer lives with. Multi Wallets, Smart Accounts, and Telegram Mini Apps get one line each, so from the repository alone you cannot tell which of them need a server you operate.

What you can tell is the shape of the thing: one chain agnostic core, per framework adapters, a wallet package, a wallet button package, and a large example set to copy from. Whether a given feature needs a backend, a project ID, or a merchant relationship is answered in the docs, not in the code you can read here.

## Conclusion

AppKit earns its place for teams that want wallet connection plus swaps, on-ramp, and smart accounts behind one chain agnostic core, and that ship across more than one framework. Two things are worth checking before you adopt it. The Community License permits non-commercial use and gates commercial use on RPC and MAU thresholds, and it requires a connection to Reown's infrastructure, so a product that must run without that connection has to be measured against those terms first. Second, if any part of your stack still says Web3Modal, read the migration guide rather than bumping a version. And read the version you actually install, 1.8.24 for the published packages, not the 1.7.1 in the monorepo root.

## FAQ

### What is AppKit used for?

AppKit is Reown's full stack toolkit for building onchain app UX. It is a chain agnostic core with SDKs for eleven targets, plus wallet features including swaps, on-ramp, multi chain and multi wallet support, smart accounts, sponsored transactions, and email or social login.

### How do you install AppKit?

Each framework has its own installation page in the AppKit docs, and eleven are linked from the readme: React, Next, Vue, Nuxt, Svelte, Javascript, React Native, Flutter, Android, iOS, and Unity. The repository itself ships no per framework setup snippet.

### Is AppKit deprecated?

Nothing in the repository suggests that. It is not archived, the last push to the main branch was on 2026-10-02, and @reown/appkit, @reown/appkit-wallet, and @reown/appkit-wallet-button were all published at 1.8.24 on 2026-09-16. Web3Modal v1 to v5 users are pointed at a migration guide instead.

### How do I use AppKit if I already have a Web3Modal integration?

The note in the readme covers that case: if you are on Web3Modal v1 through v5, follow the migration guides rather than raising a version number, and one of them is named for the move from Web3Modal v5 to Reown AppKit Web. Examples for the supported stacks sit in the examples directory.

## Sources

- [Issues](https://github.com/reown-com/appkit/issues)
- [Project website](https://reown.com/appkit)
- [README](https://github.com/reown-com/appkit/blob/main/README.md)
- [Releases](https://github.com/reown-com/appkit/releases)
- [reown-com/appkit on GitHub](https://github.com/reown-com/appkit)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/reown-com-appkit