Glyph

Appearance

Integration Options ​

This guide helps you choose the right integration method for your application based on your needs and existing tech stack.

Integration Options Overview ​

1. Native Integration (Wagmi) ​

  • When to use:
    • You want to integrate Glyph as the native wallet connection option
    • You need full control over the wallet connection UI and experience
    • You want maximum flexibility for custom implementation
  • Best for: Applications that want direct control over the integration
  • Setup complexity: Higher (requires more configuration)
  • Learn more: Native Integration Guide

2. ConnectKit ​

  • When to use:
    • You want to integrate Glyph into an existing ConnectKit application
    • You need a consistent UI with other ConnectKit wallet options
    • You're already using ConnectKit for wallet management
  • Best for: Applications using ConnectKit
  • Setup complexity: Medium
  • Learn more: ConnectKit Integration Guide

3. RainbowKit ​

  • When to use:
    • You want to integrate Glyph into an existing RainbowKit application
    • You need a consistent UI with other RainbowKit wallet options
    • You're already using RainbowKit for wallet management
  • Best for: Applications using RainbowKit
  • Setup complexity: Medium
  • Learn more: RainbowKit Integration Guide

4. Privy (Cross-App) ​

  • When to use:
    • You want to integrate Glyph into an existing Privy application
    • You need advanced user management features
    • You want seamless integration with Privy's cross-app ecosystem
  • Best for: Applications needing both wallet connection and user authentication
  • Setup complexity: Medium
  • Learn more: Privy Integration Guide

5. Dynamic ​

  • When to use:
    • You want to integrate Glyph into an existing Dynamic application
    • You need a consistent UI with other Dynamic wallet options
    • You're already using Dynamic for wallet management
  • Best for: Applications using Dynamic
  • Setup complexity: Medium
  • Learn more: Dynamic Integration Guide

Choosing the Right Integration ​

Consider the following factors when choosing an integration method:

  1. Existing Tech Stack

    • If you're already using ConnectKit, RainbowKit, Dynamic or Privy, use their respective integration
    • If you're starting fresh or need custom implementation, consider Native Integration

  2. UI Requirements

    • Native Integration gives you full control over the UI
    • ConnectKit and RainbowKit provide consistent UI with their respective frameworks
    • Privy offers a comprehensive user management UI
    • Dynamic offers a consistent UI with other Dynamic wallet options

  3. Feature Requirements

    • Native Integration: Basic wallet connection
    • ConnectKit/RainbowKit/Dynamic: Standard wallet connection with framework-specific features
    • Privy: Advanced user management and authentication features

  4. Development Resources

    • Native Integration requires more development effort but offers more flexibility
    • Framework integrations (ConnectKit, RainbowKit, Privy, Dynamic) are quicker to implement but less customizable