How azuro-protocol/example-app works
Main Components Identification
a) Frontend Layer:
• Next.js Application (App Router structure)
• Client-side Components
• UI Components Library
• Wallet Integration
b) Core Features:
• Sports Betting Engine
• Wallet Management
• User Authentication (Privy Integration)
• Event Management
• Betslip System
┌─ Client Layer ─────────────────────────────────────┐
• ┌─ Next.js App Router ─┐ ┌─ Component Library ──┐ │
• Pages │ │ - UI Components │ │
• Layouts │ │ - Compositions │ │
• Client Components │ │ - Feedback Elements │ │
• ┘ └───────────────────────┘ │
• ┌─ State Management ───┐ ┌─ Local Modules ──────┐ │
• Contexts │ │ - Wallet Provider │ │
• Hooks │ │ - SVG Provider │ │
• Global State │ │ - Cookie Storage │ │
• ┘ └───────────────────────┘ │
• ┘
┌─ Integration Layer ──────────────────────────────┐
• ┌─ Authentication ────┐ ┌─ Wallet Integration ─┐ │
• Privy │ │ - Web3 Providers │ │
• Social Login │ │ - Multiple Wallets │ │
• ┘ └───────────────────────┘ │
• ┘
┌─ Business Logic Layer ────────────────────────────┐
• ┌─ Betting Engine ────┐ ┌─ Event Management ───┐ │
• Odds Processing │ │ - Sports Data │ │
• Bet Placement │ │ - Live Updates │ │
• ┘ └───────────────────────┘ │
• ┘
Connection Flows
• User interaction flows
• Data flow between components
• Authentication processes
• Wallet connection flows
• Betting transaction flows
Important Details
• Next.js App Router structure (/src/app)
• Component organization (/src/components)
• Local modules integration (/local_modules)
• Authentication flow with Privy
• Sports betting business logic
• State management through contexts