Skip to content

docs: update AppKit terminology to Reown across documentation#738

Open
devin-ai-integration[bot] wants to merge 12 commits intomainfrom
devin/1770624249-update-appkit-terminology
Open

docs: update AppKit terminology to Reown across documentation#738
devin-ai-integration[bot] wants to merge 12 commits intomainfrom
devin/1770624249-update-appkit-terminology

Conversation

@devin-ai-integration
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot commented Feb 9, 2026

Description

Updates product terminology across the documentation, replacing "AppKit" references with "Reown" in all prose/descriptive text per the new branding guidelines. 230+ files modified.

Replacement rules applied:

  • Product references: "AppKit" → "Reown" (e.g., "AppKit offers…" → "Reown offers…")
  • Installation/package references: "AppKit" → "Reown AppKit" (e.g., "install AppKit" → "install Reown AppKit")
  • Configuration/instance references: "Reown instance/client/configuration" → "Reown AppKit instance/client/configuration" (e.g., "create a Reown instance" → "create a Reown AppKit instance")
  • SDK behavior descriptions: "Reown will/does/uses/creates/checks…" → "The SDK will/does/uses/creates/checks…" (e.g., "Reown will send a SIWE request" → "The SDK will send a SIWE request")
  • Code identifiers preserved: Reverted any incorrectly changed code identifiers back to AppKit.* (e.g., AppKit.ModalDelegate, AppKit.instance, AppKit.configure)
  • Redundant branding: "Reown AppKit" → "Reown" (in non-installation/non-instance contexts)
  • SDK references: "AppKit SDK" → "Reown SDK"
  • Feature references: Dropped "AppKit" prefix (e.g., "AppKit Pay with Exchange" → "Pay with Exchange")
  • Named variants: "AppKit CLI" → "Reown CLI", "AppKit Modal" → "Reown Modal", etc.
  • Navigation labels in docs.json: Updated dropdown/group display names (e.g., "AppKit - Overview" → "Reown - Overview")
  • Top-level tab: "AppKit" → "Reown" in the header navigation tab
  • Navbar button: "AppKit Demo" → "Reown Demo"
  • Dropdown descriptions: Updated remaining "AppKit on VueJS/Kotlin/Swift" descriptions to "Reown on …"
  • "Get started" cards: "Get started with Reown AppKit in React" → "Get started with Reown in React" (across all frameworks)

Preserved unchanged:

  • "AppKit Core" — kept as-is per reviewer feedback (not renamed to "Reown Core")
  • Code identifiers like AppKit.ModalDelegate, AppKit.instance, AppKit.configure, AppKit.Evm, AppKit.Solana — these are API class names, not product names
  • All package names in code snippets (@reown/appkit, @reown/appkit-adapter-wagmi, etc.)
  • Code identifiers (createAppKit, useAppKit, AppKitProvider, etc.)
  • URL paths (/appkit/overview, /appkit/react/core/installation)
  • Mermaid diagram node syntax
  • displayed_sidebar config values
  • Code block metadata strings (e.g., name: 'Appkit Solana' inside code examples)
  • Business/pricing descriptions (e.g., "Reown uses a tiered pricing model" kept as "Reown")

Latest updates (since last revision) — Comments 69-111

Accepted and applied additional suggestions from Jem-reown, and propagated same changes to equivalent pages across frameworks where applicable.

  1. Next SIWE
  • "Install the Reown SIWE package…" → "Install the Reown SIWE package. For the best experience, we recommend also installing siwe to abstract a lot of the required logic."
  • "With help of the siwe package… configuration for Reown." → "…configuration for Reown AppKit."
  • "Initialize Reown with your siweConfig" → "Initialize Reown AppKit with your siweConfig"
  1. Nuxt
  • Actions/Components/Composables notes: "Reown" → "Reown AppKit" within client-only SSR guidance
  • Installation: → ; "client-only wrapper ensures Reown components…" → "…ensures Reown AppKit components…"
  1. Payments – Pay with Exchange
  • "Pay with Exchange is part of Reown Payments, it is available as a modal and a headless flow." → "Pay with Exchange is available as a modal and a headless flow."
  • "Yes, if usage exceeds Reown tier limits." → "Yes, if usage exceeds your pricing plan limits." (both occurrences)
  • Adjusted the two "Can we monitor transactions in real time?" answers to remove prior transaction-ID statements per suggestion and use the simplified availability sentence
  • Typos/spacing fixes: "process.They" → "process. They"; "visibleupon" → "visible upon"
  1. React Native
  • Email & Socials: grammar/polish ("connect to your application", "integrates the Reown SDK")
  • Hooks: "beyond the standard Reown actions" → "beyond Reown AppKit's standard actions"; logging hook now references "Reown AppKit's internal logging system" and "the SDK's behavior"
  • Installation: "Initialize Reown" → "Initialize Reown AppKit"; example link label updated to "Reown AppKit + Wagmi"; "Default Features: Reown AppKit comes with…"; "Update Reown AppKit Configuration"
  1. Cross-framework SIWE (React, Vue, JavaScript)
  • Matched Next SIWE phrasing changes:
    • Install sentence updated to "For the best experience, we recommend also installing siwe…"
    • "Initialize Reown with your siweConfig" → "Initialize Reown AppKit with your siweConfig"
  1. Unity
  • SIWE: "Initialize Reown with your SiweConfig" → "Initialize Reown AppKit with your SiweConfig"; fixed "verification and" spacing
  • Socials: email paragraph grammar ("connect to your application", "integrates the Reown SDK")
  1. Installation tabs (consistency)
  • Changed "" → "" in React, Vue, and JavaScript installation pages (to match prior Next/Nuxt updates)
  1. Minor typo fixes
  • Corrected small spacing/typo issues introduced during edits in Payments and Unity SIWE.

Latest updates (18 files) — Comments 60-67

Accepted additional PR suggestions from Jem-reown and applied to all framework pages:

  1. iOS Usage page:

    • Rewrote Sign methods paragraph: "Reown AppKit uses the Sign SDK to implement the WalletConnect Protocol..."
    • Removed "Where to go from here" section entirely
  2. Custom Connectors pages (JavaScript, React, Vue, Next):

    • "In Reown, a 'connector'" → "In Reown Appkit, a 'connector'"
    • "integrate Reown on top of it" → "integrate Reown Appkit on top of it"
  3. Custom Networks pages (JavaScript, React, Vue, Next):

    • "Since Reown v1.1.0" → "Since version v1.1.0, there are two ways to add your network to Reown AppKit"
  4. Installation pages (JavaScript, React, Vue, Next):

    • AI setup section: "to build a project with Reown, Reown provides" → "to build, Reown Appkit provides"
    • Removed redundant "for Reown" at end of type hints sentence
  5. SIWE pages (JavaScript, React, Vue, Next, Unity):

    • "a new form of authentication" → "a form of authentication" (removed "new")

Updates since last revision (18 files) — Comments 30-58

Accepted additional PR suggestions from Jem-reown:

  1. Solana Adapter page:

    • "Reown now supports multichain" → "Reown supports multichain"
    • "within your instance of Reown" → "within your instance of Reown AppKit"
  2. One-Click Auth descriptions (Android, Flutter, iOS):

    • Rewrote to remove "represents a key advancement within WalletConnect v2" phrasing
    • Android: "One-Click Auth streamlines the user authentication process, giving users the power to connect..."
    • Flutter: "One-Click Auth streamlines the user authentication process by enabling them to seamlessly connect..."
    • iOS: "One-Click Auth streamlines the user authentication process, letting users connect..."
  3. Features pages:

    • Chain Abstraction: "experience Reown's Chain Abstraction flow" → "experience the flow"
    • Features Overview: Rewrote intro to "Reown offers a wide range of features... Some features are limited to specific frameworks."
    • Features Overview: "The following table provides..." → "See the full list of features available on each framework in the table below."
    • Multichain: "Reown is now multichain. The architecture is designed to..." → "Reown is multichain; designed to..."
    • On-Ramp: Rewrote to "On-Ramp makes it easy for users to purchase crypto with fiat currencies; without the hassle..."
    • Smart Accounts: "Reown now supports" → "Reown supports", "will be given the option to upgrade" → "can also upgrade"
    • Smart Accounts Interaction: "Reown integrates" → "Reown AppKit integrates", "Reown inspects" → "The SDK inspects"
  4. Flutter docs:

    • Installation: "enable Reown to detect" → "enable the SDK to detect"
    • Link Mode: "Reown Link Mode" → "Link Mode", "pass it to Reown" → "pass it to the SDK"
    • Options: "Reown already defines" → "Reown AppKit already defines"
    • SIWE: Removed "new" from "new form of authentication"
    • Usage: "Reown's metadata object" → "Reown AppKit's metadata object", "override Reown's buttons" → "override Reown AppKit's buttons"
  5. iOS docs:

    • Installation: "add Reown to your project" → "add Reown AppKit to your project" (3 occurrences)
    • Installation: "Reown with Swift example" → "AppKit with Swift example"
    • Installation: "sample Reown apps" → "sample apps"
    • Options: "Reown configure call" → "Reown AppKit configure call"
    • Usage: "Initialize Reown Client" → "Initialize Reown AppKit Client"
  6. SIWX page:

    • "provided by Reown" → "provided by Reown AppKit"

Requested by: Jem Conlon
Link to Devin run: https://app.devin.ai/sessions/bea6e7101b56464ba2c591bd4230f8f3

Key areas for reviewer attention

  1. Capitalization consistency: Some suggestions use "Reown Appkit" (lowercase k) vs "Reown AppKit" elsewhere. Confirm the intended style.
  2. Payments FAQs alignment: Per suggestion, "Can we monitor transactions in real time?" now uses the simplified availability sentence; confirm this is the desired content.
  3. SIWE pages: Confirm new install sentence and "Initialize Reown AppKit…" heading are preferred across React, Vue, JavaScript, Next, and Unity.
  4. RN docs: Confirm terminology updates ("Reown AppKit's standard actions", logging hook wording, "Initialize Reown AppKit") align with product voice.
  5. Installation tabs: Confirm using "AppKit" as the Tab title (React/Vue/JavaScript/Nuxt/Next) is consistent with navigation style.

Local Testing Screenshots

Homepage with updated terminology:
Homepage

Overview page:
Overview

Pay with Exchange page:
Pay with Exchange

Tests

  • Ran the changes locally with Mintlify and confirmed that the changes appear as expected.
  • Ran a grammar check on the updated/created content using ChatGPT.

Direct link to the deployed preview files

Co-Authored-By: Jem Conlon <jem@walletconnect.com>
@devin-ai-integration
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

Co-Authored-By: Jem Conlon <jem@walletconnect.com>
…ect-verb agreement)

Co-Authored-By: Jem Conlon <jem@walletconnect.com>
Co-Authored-By: Jem Conlon <jem@walletconnect.com>
Co-Authored-By: Jem Conlon <jem@walletconnect.com>
…, and SDK behavior

Co-Authored-By: Jem Conlon <jem@walletconnect.com>
…erences, and remaining setup/version terminology

Co-Authored-By: Jem Conlon <jem@walletconnect.com>
### Reown

The following is a **partial CSP** that covers WalletConnect's libraries and services for [AppKit](https://docs.walletconnect.com/appkit/overview). Note that **you may need to define additional sources based on your application's requirements**.
The following is a **partial CSP** that covers WalletConnect's libraries and services for [Reown](https://docs.walletconnect.com/appkit/overview). Note that **you may need to define additional sources based on your application's requirements**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The following is a **partial CSP** that covers WalletConnect's libraries and services for [Reown](https://docs.walletconnect.com/appkit/overview). Note that **you may need to define additional sources based on your application's requirements**.
The following is a **partial CSP** that covers WalletConnect's libraries and services for [Reown Appkit](https://docs.walletconnect.com/appkit/overview). Note that **you may need to define additional sources based on your application's requirements**.


### Architecture and Custody
AppKit Embedded wallets enable applications to provide end-users with a quick onboarding experience by provisioning a non-custodial wallet through social login or email wallets. While the implementation varies per network, Reown relies on a SOC 2 Type 2 compliant third-party vendor for key management. The vendor's [security overview](https://magic.link/docs/home/security/product-security) and [list of audits](https://magic.link/docs/home/security/security-compliance) are available in their documentation.
Embedded wallets enable applications to provide end-users with a quick onboarding experience by provisioning a non-custodial wallet through social login or email wallets. While the implementation varies per network, Reown relies on a SOC 2 Type 2 compliant third-party vendor for key management. The vendor's [security overview](https://magic.link/docs/home/security/product-security) and [list of audits](https://magic.link/docs/home/security/security-compliance) are available in their documentation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Embedded wallets enable applications to provide end-users with a quick onboarding experience by provisioning a non-custodial wallet through social login or email wallets. While the implementation varies per network, Reown relies on a SOC 2 Type 2 compliant third-party vendor for key management. The vendor's [security overview](https://magic.link/docs/home/security/product-security) and [list of audits](https://magic.link/docs/home/security/security-compliance) are available in their documentation.
Embedded wallets enable applications to provide end-users with a quick onboarding experience by provisioning a non-custodial wallet through social login or email wallets. While the implementation varies per network, Reown Appkit relies on a SOC 2 Type 2 compliant third-party vendor for key management. The vendor's [security overview](https://magic.link/docs/home/security/product-security) and [list of audits](https://magic.link/docs/home/security/security-compliance) are available in their documentation.


### Audits
Both the key management vendors and Smart Account vendors have undergone multiple audits (see links above). The integration of the key management provider into AppKit has been audited by Halborn. The complete audit report is available [here](https://drive.google.com/file/d/1LQ6BkcI4PHs_FKAzpCRMqwD--rq6uOy6/view).
Both the key management vendors and Smart Account vendors have undergone multiple audits (see links above). The integration of the key management provider into Reown has been audited by Halborn. The complete audit report is available [here](https://drive.google.com/file/d/1LQ6BkcI4PHs_FKAzpCRMqwD--rq6uOy6/view).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Both the key management vendors and Smart Account vendors have undergone multiple audits (see links above). The integration of the key management provider into Reown has been audited by Halborn. The complete audit report is available [here](https://drive.google.com/file/d/1LQ6BkcI4PHs_FKAzpCRMqwD--rq6uOy6/view).
Both the key management vendors and Smart Account vendors have undergone multiple audits (see links above). The integration of the key management provider into Reown Appkit has been audited by Halborn. The complete audit report is available [here](https://drive.google.com/file/d/1LQ6BkcI4PHs_FKAzpCRMqwD--rq6uOy6/view).

## Third-Party Reviews

The security infrastructure of Reown has undergone multiple rounds of audits by independent security auditing firms, including Trail of Bits, Halborn, and Spearbit. These audits cover both AppKit and WalletKit, along with a comprehensive company-wide Threat Model.
The security infrastructure of Reown has undergone multiple rounds of audits by independent security auditing firms, including Trail of Bits, Halborn, and Spearbit. These audits cover both Reown and WalletKit, along with a comprehensive company-wide Threat Model.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The security infrastructure of Reown has undergone multiple rounds of audits by independent security auditing firms, including Trail of Bits, Halborn, and Spearbit. These audits cover both Reown and WalletKit, along with a comprehensive company-wide Threat Model.
Reown's security infrastructure of Reown has undergone multiple rounds of audits by independent security auditing firms, including Trail of Bits, Halborn, and Spearbit. These audits cover both Reown Appkit and WalletConnect's WalletKit, along with a comprehensive company-wide Threat Model.


- [Awesome WalletConnect](https://github.com/WalletConnect/awesome-walletconnect) - Community-curated collection of WalletConnect-enabled wallets, libraries, and tools.
- [AppKit Laboratory](https://appkit-lab.reown.com/) - A place to test your wallet integrations against various setups of AppKit.
- [Reown Laboratory](https://appkit-lab.reown.com/) - A place to test your wallet integrations against various setups of Reown.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [Reown Laboratory](https://appkit-lab.reown.com/) - A place to test your wallet integrations against various setups of Reown.
- [Reown Laboratory](https://appkit-lab.reown.com/) - A place to test your wallet integrations against various setups of Reown Appkit.

### Get Active Account

Returns the current active account connected via AppKit
Returns the current active account connected via Reown
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Returns the current active account connected via Reown
Returns the current active account connected via the Reown SDK

### Reown State

AppKitState is an object that ensures communication between your application and the state of the AppKit.
AppKitState is an object that ensures communication between your application and the state of the Reown.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
AppKitState is an object that ensures communication between your application and the state of the Reown.
AppKitState is an object that ensures communication between your application and the state of your Reown Appkit instance.

```

returns `StateFlow<Boolean>` whose value depends on the active session in AppKit
returns `StateFlow<Boolean>` whose value depends on the active session in Reown
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
returns `StateFlow<Boolean>` whose value depends on the active session in Reown
returns `StateFlow<Boolean>` whose value depends on the active session in your Reown Appkit instance.

## Configure your AppKit Client

To integrate SIWE with AppKit, you need to configure your AppKit client using `Modal.Model.AuthPayloadParams`, which are required to create a SIWE message for the user to sign:
To integrate SIWE with Reown, you need to configure your AppKit client using `Modal.Model.AuthPayloadParams`, which are required to create a SIWE message for the user to sign:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To integrate SIWE with Reown, you need to configure your AppKit client using `Modal.Model.AuthPayloadParams`, which are required to create a SIWE message for the user to sign:
To integrate SIWE, you must configure your Reown AppKit client using `Modal.Model.AuthPayloadParams`. This is required to create a SIWE message for the user to sign:

## Getting Started

**SIWX** works as a plugin system for AppKit and you are going to add the plugin in the AppKit configuration. There are some ways to implement the **SIWX** feature:
**SIWX** works as a plugin system for Reown and you are going to add the plugin in the Reown AppKit configuration. There are some ways to implement the **SIWX** feature:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**SIWX** works as a plugin system for Reown and you are going to add the plugin in the Reown AppKit configuration. There are some ways to implement the **SIWX** feature:
**SIWX** works as a plugin, which can be added in your Reown AppKit configuration. There are several ways to implement the **SIWX** feature:

you can configure the `siwx` parameters expected to receive. This is what allows you to customize the feature to suit your specific requirements.

The defined interface must follow specific rules to make sure that AppKit can interact with it correctly. Read more about how to have your [Custom Implementation](./siwx-custom).
The defined interface must follow specific rules to make sure that Reown can interact with it correctly. Read more about how to have your [Custom Implementation](./siwx-custom).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The defined interface must follow specific rules to make sure that Reown can interact with it correctly. Read more about how to have your [Custom Implementation](./siwx-custom).
The defined interface must follow specific rules to make sure that the SDK can interact with it correctly. Read more about how to have your [Custom Implementation](./siwx-custom).

<CardGroup cols={2}>
<Card title="React" icon="react" href="/appkit/react/core/siwe">
Get started with AppKit in React.
Get started with Reown AppKit in React.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Get started with Reown AppKit in React.
Get started with Reown in React.


<Card title="Next.js" icon="square-n" href="/appkit/next/core/siwe">
Get started with AppKit in Next.js.
Get started with Reown AppKit in Next.js.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Get started with Reown AppKit in Next.js.
Get started with Reown in Next.js.


<Card title="Vue" icon="vuejs" href="/appkit/vue/core/siwe">
Get started with AppKit in Vue.
Get started with Reown AppKit in Vue.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Get started with Reown AppKit in Vue.
Get started with Reown in Vue.


<Card title="JavaScript" icon="js" href="/appkit/javascript/core/siwe">
Get started with AppKit in JavaScript.
Get started with Reown AppKit in JavaScript.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Get started with Reown AppKit in JavaScript.
Get started with Reown in JavaScript.

- Using cookies is completely optional and by default Wagmi will use `localStorage` instead if the `storage` param is not defined.
- The `ssr` flag will delay the hydration of Wagmi's store to avoid hydration mismatch errors.
- AppKit doesn't fully support the `ssr` flag.
- Reown doesn't fully support the `ssr` flag.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Reown doesn't fully support the `ssr` flag.
- Reown AppKit doesn't fully support the `ssr` flag.

### Context Provider

Let's create now a context provider that will wrap our application and initialized AppKit (`createAppKit` needs to be called inside a Next Client Component file).
Let's create now a context provider that will wrap our application and initialized Reown (`createAppKit` needs to be called inside a Next Client Component file).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Let's create now a context provider that will wrap our application and initialized Reown (`createAppKit` needs to be called inside a Next Client Component file).
Now we'll create a context provider that will wrap our application and initialized Reown AppKit instance (`createAppKit` needs to be called inside a Next Client Component file).

```

Learn more about the AppKit web components [here](/appkit/next/core/components)
Learn more about the Reown web components [here](/appkit/next/core/components)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Learn more about the Reown web components [here](/appkit/next/core/components)
Learn more about Reown's web components [here](/appkit/next/core/components)

```

Learn more about the AppKit composables [here](/appkit/nuxt/core/composables)
Learn more about the Reown composables [here](/appkit/nuxt/core/composables)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Learn more about the Reown composables [here](/appkit/nuxt/core/composables)
Learn more about Reown's composables [here](/appkit/nuxt/core/composables)

```

Learn more about the AppKit web components [here](/appkit/react/core/components)
Learn more about the Reown web components [here](/appkit/react/core/components)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Learn more about the Reown web components [here](/appkit/react/core/components)
Learn more about Reown's web components [here](/appkit/react/core/components)

@@ -1,4 +1,4 @@
The theme for the AppKit integration in your dApp can be fully customized.
The theme for the Reown integration in your dApp can be fully customized.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The theme for the Reown integration in your dApp can be fully customized.
You can customize the theme of your Reown AppKit integration fully.


<Note>
The `browser` check ensures AppKit is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.
The `browser` check ensures Reown is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The `browser` check ensures Reown is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.
The `browser` check ensures Reown AppKit is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.


<Note>
The `browser` check ensures AppKit is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.
The `browser` check ensures Reown is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The `browser` check ensures Reown is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.
The `browser` check ensures Reown AppKit is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.


<Note>
The `browser` check ensures AppKit is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.
The `browser` check ensures Reown is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The `browser` check ensures Reown is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.
The `browser` check ensures Reown AppKit is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.


<Note>
The `browser` check ensures AppKit is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.
The `browser` check ensures Reown is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The `browser` check ensures Reown is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.
The `browser` check ensures Reown AppKit is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.


<Note>
The `browser` check ensures AppKit is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.
The `browser` check ensures Reown is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The `browser` check ensures Reown is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.
The `browser` check ensures Reown AppKit is only initialized in the browser environment, which is important for SvelteKit's SSR compatibility.

```

Learn more about the AppKit web components [here](/appkit/vue/core/components)
Learn more about the Reown web components [here](/appkit/vue/core/components)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Learn more about the Reown web components [here](/appkit/vue/core/components)
Learn more about Reown's web components [here](/appkit/vue/core/components)

```

Learn more about the AppKit composables [here](/appkit/vue/core/composables)
Learn more about the Reown composables [here](/appkit/vue/core/composables)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Learn more about the Reown composables [here](/appkit/vue/core/composables)
Learn more about Reown's composables [here](/appkit/vue/core/composables)

```

Learn more about the Appkit web components [here](/appkit/vue/core/components)
Learn more about the Reown web components [here](/appkit/vue/core/components)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Learn more about the Reown web components [here](/appkit/vue/core/components)
Learn more about Reown's web components [here](/appkit/vue/core/components)

```

Learn more about the AppKit composables [here](/appkit/vue/core/composables)
Learn more about the Reown composables [here](/appkit/vue/core/composables)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Learn more about the Reown composables [here](/appkit/vue/core/composables)
Learn more about Reown's composables [here](/appkit/vue/core/composables)

```

Learn more about the AppKit web components [here](/appkit/vue/core/components)
Learn more about the Reown web components [here](/appkit/vue/core/components)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Learn more about the Reown web components [here](/appkit/vue/core/components)
Learn more about Reown's web components [here](/appkit/vue/core/components)

Learn more about the Blockchain API [here](./blockchain-api)

### AppKit
### Reown
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Reown
### Your App Performance

#### Avg. Daily Visitors

Indicates the daily average of unique visitors to your app’s AppKit.
Indicates the daily average of unique visitors to your app’s Reown.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Indicates the daily average of unique visitors to your app’s Reown.
Indicates the daily average of unique visitors to your app.

#### All Events

This table and chart shows the count of various events that are triggered as the users interact with AppKit.
This table and chart shows the count of various events that are triggered as the users interact with the modal.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This table and chart shows the count of various events that are triggered as the users interact with the modal.
This table and chart shows the count of various events triggered by your users.

#### Visitors

Shows the daily trend of unique visitors to your app’s AppKit.
Shows the daily trend of unique visitors to your app’s Reown.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Shows the daily trend of unique visitors to your app’s Reown.
Shows the daily trend of unique visitors to your app.

@reown-com reown-com deleted a comment from github-actions bot Feb 13, 2026
@reown-com reown-com deleted a comment from github-actions bot Feb 13, 2026
@reown-com reown-com deleted a comment from github-actions bot Feb 13, 2026
@reown-com reown-com deleted a comment from github-actions bot Feb 13, 2026
@reown-com reown-com deleted a comment from github-actions bot Feb 13, 2026
@reown-com reown-com deleted a comment from github-actions bot Feb 13, 2026
@reown-com reown-com deleted a comment from github-actions bot Feb 13, 2026
@bkrem
Copy link
Member

bkrem commented Feb 16, 2026

@claude review

@claude
Copy link

claude bot commented Feb 16, 2026

Claude finished @bkrem's task in 2m 23s —— View job


Code Review Complete

🚨 Critical Issues Found

Found 5 issue(s)

Issue 1: PR exceeds recommended size

ID: pr-size-limit-exceeded-7f3a
Files: 100 changed files
Severity: HIGH
Category: maintainability

Context:

  • Pattern: This PR modifies 100 files with 1246 additions and 1250 deletions
  • Risk: Large PRs are difficult to review thoroughly, increasing the likelihood of bugs slipping through
  • Impact: Harder to identify issues, longer review cycles, potential merge conflicts
  • Trigger: Any documentation update requiring extensive find-and-replace across the codebase

Recommendation: While this PR is nearly complete and has undergone multiple review rounds, future terminology updates should be split into focused PRs:

  • PR 1: Core terminology updates (appkit/overview, features/, authentication/) - 20-30 files
  • PR 2: Framework-specific docs (react/, next/, vue/, javascript/) - 20-30 files
  • PR 3: Platform-specific docs (ios/, android/, flutter/, unity/) - 20-30 files
  • PR 4: Migration guides, recipes, and misc files - remaining files

Issue 2: Inconsistent capitalization - "Appkit" vs "AppKit"

ID: security-csp-appkit-case-f3a2
File: advanced/security/content-security-policy.mdx:13
Severity: MEDIUM
Category: consistency

Context:

  • Pattern: Line 13 uses "Reown AppKit" (capital K), but review comment Home UI #1 from Jem-reown suggests "Reown Appkit" (lowercase k)
  • Risk: Brand inconsistency across documentation
  • Impact: Confused developers, inconsistent brand presentation
  • Trigger: Any reference to the product name in documentation

Recommendation: Clarify the official capitalization standard. Current PR uses "Reown AppKit" (capital K) throughout. If "Reown Appkit" is preferred, update all 100+ files. The review suggestion shows:

[Reown Appkit](https://docs.walletconnect.com/appkit/overview)

But current code uses Reown AppKit everywhere else. Standardize one way.


Issue 3: FAQ answer doesn't match question

ID: payments-faq-monitor-f8d1
File: appkit/payments/pay-with-exchange.mdx:184-186, 282
Severity: HIGH
Category: content_quality

Context:

  • Pattern: "Can we monitor transactions in real time?" answers with "Pay with Exchange is available as a modal and a headless flow." (lines 185, 282)
  • Risk: Answer is completely unrelated to the question about transaction monitoring
  • Impact: Developers cannot find information about transaction monitoring capabilities
  • Trigger: Users reading FAQ to understand monitoring capabilities

Recommendation: Review comment #90 suggests simplifying to availability statement, but the answer still doesn't address monitoring. Should be:

<Accordion>
  Yes, transaction monitoring is available through [Analytics dashboard/API endpoint]. You can track transaction status, confirmations, and receive webhooks for state changes.
</Accordion>

Or remove the FAQ item if monitoring isn't supported yet.


Issue 4: Incorrect GitHub link reference

ID: ios-usage-wrong-repo-a4b7
File: appkit/ios/core/usage.mdx:110
Severity: MEDIUM
Category: documentation

Context:

  • Pattern: Line references "reown-dotnet" repository Unity C# code in iOS Swift documentation
  • Risk: Broken/misleading documentation link
  • Impact: Developers clicking the link expecting iOS/Swift code will see Unity/C# instead
  • Trigger: Any developer following the iOS usage guide

Current code:

Reown AppKit uses the Sign SDK to implement the WalletConnect Protocol. Most Sign SDK functionality is exposed through the [`AppKit`](https://github.com/reown-com/reown-dotnet/blob/main/src/Reown.AppKit.Unity/Runtime/AppKit.cs#L17-L45) class, the main entry point for developers.

Recommendation: Fix link to point to iOS/Swift repository:

Reown AppKit uses the Sign SDK to implement the WalletConnect Protocol. Most Sign SDK functionality is exposed through the [`AppKit`](https://github.com/reown-com/reown-swift/tree/develop/Sources/ReownAppKit) class, the main entry point for developers.

Issue 5: Unapplied review suggestions from Jem-reown

ID: review-suggestions-pending-9c2f
Files: Multiple files (see list below)
Severity: MEDIUM
Category: code_quality

Context:

  • Pattern: 90+ review suggestions from Jem-reown remain unapplied since Feb 12-13
  • Risk: PR description claims "accepted and applied" but current code doesn't reflect all changes
  • Impact: Inconsistent terminology, missed improvements, stale PR state
  • Trigger: Final merge will include unresolved feedback

Files with pending suggestions (sample):

  • advanced/security/content-security-policy.mdx:13 - "Reown Appkit" capitalization
  • advanced/security/security-information.mdx:6, 10 - "Reown Appkit" references
  • appkit/android/core/components.mdx:7 - "### Reown AppKit State" header
  • appkit/migration/from-anza-adapter-react.mdx:7 - Multiple "Reown AppKit" references
  • appkit/migration/from-connectkit-next.mdx:1 - Title and references
  • appkit/migration/from-privy-next.mdx:11, 21, 31 - Configuration and provider references
  • appkit/networks/evm.mdx:9 - "Reown provides..." sentence
  • appkit/next/core/hooks.mdx:28, 31, 33 - Diagram description and state descriptions
  • appkit/next/core/installation.mdx:45 - Tab title and SSR note
  • appkit/react-native/core/installation.mdx:98, 101, 103, 105 - Multiple initialization references

Recommendation: Apply remaining review suggestions systematically:

  1. Decide on "AppKit" vs "Appkit" capitalization (see Issue re:org ui: updating welcome page UI and general theme #2)
  2. Apply all Jem-reown suggestions from comments Fix wagmiAdapter spelling. Update implementation.mdx #69-111
  3. Verify each change matches the suggestion exactly
  4. Re-test preview site to ensure no broken links

✅ Positive Observations

Terminology consistency: The core replacement rules are well-executed:

  • Product references correctly changed: "AppKit offers" → "Reown offers"
  • Installation preserved: "install Reown AppKit" ✓
  • Code identifiers preserved: AppKit.configure(), createAppKit()
  • SDK behavior: "The SDK will..." pattern correctly applied
  • Feature names: "Pay with Exchange" (no AppKit prefix) ✓

Documentation quality:

  • Clear, developer-focused language throughout
  • Professional yet approachable tone aligns with Web3 documentation standards
  • Good use of MDX components (Cards, Accordions, CodeGroups)
  • Consistent structure across framework-specific docs

No automated violations detected:

  • No external domain URLs requiring review
  • No GitHub Actions workflow security issues (no workflow files changed)
  • No WalletConnect Pay architecture anti-patterns

Recommended Actions

  1. CRITICAL: Clarify "AppKit" vs "Appkit" capitalization standard with stakeholders
  2. HIGH: Fix FAQ monitoring answers (Issue feat: add conf and default for socials and email #3) - completely wrong content
  3. HIGH: Fix iOS usage GitHub link (Issue Flutter & RN Link Mode #4) - points to wrong repo
  4. MEDIUM: Apply remaining 90+ review suggestions from Jem-reown
  5. LOW: Consider splitting future large-scale updates into smaller PRs

### Reown

The following is a **partial CSP** that covers WalletConnect's libraries and services for [AppKit](https://docs.walletconnect.com/appkit/overview). Note that **you may need to define additional sources based on your application's requirements**.
The following is a **partial CSP** that covers WalletConnect's libraries and services for [Reown AppKit](https://docs.walletconnect.com/appkit/overview). Note that **you may need to define additional sources based on your application's requirements**.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Auto Review Issue: Inconsistent capitalization - "Appkit" vs "AppKit"

Severity: MEDIUM
Category: consistency
Tool: Claude Auto Review

Context:

  • Pattern: Line 13 uses "Reown AppKit" (capital K), but review comment Home UI #1 from Jem-reown suggests "Reown Appkit" (lowercase k)
  • Risk: Brand inconsistency across documentation
  • Impact: Confused developers, inconsistent brand presentation
  • Trigger: Any reference to the product name in documentation

Recommendation: Clarify the official capitalization standard. Current PR uses "Reown AppKit" (capital K) throughout. If "Reown Appkit" is preferred, update all 100+ files. The review suggestion shows:

[Reown Appkit](https://docs.walletconnect.com/appkit/overview)

But current code uses Reown AppKit everywhere else. Standardize one way.

@@ -182,19 +182,19 @@ This feature is currently in early access. If you are **interested in getting ea
</Accordion>

<Accordion title="Can we monitor transactions in real time?">

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Auto Review Issue: FAQ answer doesn't match question

Severity: HIGH
Category: content_quality
Tool: Claude Auto Review

Context:

  • Pattern: "Can we monitor transactions in real time?" answers with "Pay with Exchange is available as a modal and a headless flow." (lines 185, 282)
  • Risk: Answer is completely unrelated to the question about transaction monitoring
  • Impact: Developers cannot find information about transaction monitoring capabilities
  • Trigger: Users reading FAQ to understand monitoring capabilities

Recommendation: Review comment #90 suggests simplifying to availability statement, but the answer still doesn't address monitoring. Should be:

<Accordion>
  Yes, transaction monitoring is available through [Analytics dashboard/API endpoint]. You can track transaction status, confirmations, and receive webhooks for state changes.
</Accordion>

Or remove the FAQ item if monitoring isn't supported yet.

### Reown

The following is a **partial CSP** that covers WalletConnect's libraries and services for [AppKit](https://docs.walletconnect.com/appkit/overview). Note that **you may need to define additional sources based on your application's requirements**.
The following is a **partial CSP** that covers WalletConnect's libraries and services for [Reown AppKit](https://docs.walletconnect.com/appkit/overview). Note that **you may need to define additional sources based on your application's requirements**.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Auto Review Issue: Unapplied review suggestions from Jem-reown

Severity: MEDIUM
Category: code_quality
Tool: Claude Auto Review

Context:

  • Pattern: 90+ review suggestions from Jem-reown remain unapplied since Feb 12-13
  • Risk: PR description claims "accepted and applied" but current code doesn't reflect all changes
  • Impact: Inconsistent terminology, missed improvements, stale PR state
  • Trigger: Final merge will include unresolved feedback

Recommendation: Apply remaining review suggestions systematically:

  1. Decide on "AppKit" vs "Appkit" capitalization (see Issue re:org ui: updating welcome page UI and general theme #2)
  2. Apply all Jem-reown suggestions from comments Fix wagmiAdapter spelling. Update implementation.mdx #69-111
  3. Verify each change matches the suggestion exactly
  4. Re-test preview site to ensure no broken links

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants