How rssnext/follow works
High-Level Architecture Components
a) Client Applications:
• Web App (Browser-based)
• Desktop App (Electron)
• Mobile App (React Native)
• Server Application
b) Core Services:
• Authentication Service
• Feed Management Service
• Content Processing Service
• AI Services (translation, summary)
• Wallet/Power Token Service
• Real-time Updates Service
Key Architectural Patterns to Highlight
• Monorepo structure with shared packages
• Multi-platform architecture
• Event-driven communication
• State management patterns
• Data synchronization flows
Detailed Component Breakdown
Create sections for:
Frontend Layer:
• UI Components (packages/components)
• State Management (using Jotai - evident from atoms folders)
• Routing System
• Platform-specific Views
• Shared Utils & Hooks
Backend Layer:
• API Routes
• Database Interactions
• Authentication
• Feed Processing
• Content Storage
Integration Layer:
• RSS Feed Handlers
• AI Service Integration
• Payment Processing
• Real-time Updates
Data Flow Representation
Flow of:
• Feed subscription and updates
• Content synchronization
• User authentication
• AI processing requests
• Power token transactions
Specific Implementation Details
Technology-specific elements:
• Vite for build system
• Electron for desktop
• React Native for mobile
• Tailwind for styling
• i18n for localization
• Database systems
• Client Applications |
• Web App | | Desktop Client | | Mobile App | | Progressive Web App | |
• v
• Shared Core Logic |
• State Manager | | UI Components | | Utils/Helpers | | Platform Adapters | |
• v
• Service Layer |
• Feed Service | | AI Processing | | Auth Service | | Power Token Service | |
• v
• External Services |
• RSS Sources | | AI APIs | | Payment Gates | | Storage Services | |