How astashov/liftosaur works
Main Components
a. Client-Side (Frontend):
• PWA Application (Preact/TypeScript)
• Service Worker (for offline functionality)
• Local Storage/IndexedDB (for offline data persistence)
• CodeMirror Editor (for Liftoscript)
• uPlot (for graphs/charts)
• Tailwind CSS (for styling)
b. Server-Side (Backend):
• AWS Lambda Functions
• API Gateway
• DynamoDB (main database)
• S3 (static assets and storage)
• AWS Secrets Manager
• CloudFront (CDN)
• SES (email services)
Architecture Patterns
• Serverless Architecture (AWS Lambda)
• PWA Architecture (Service Worker, caching)
• Event-driven Architecture (for real-time updates)
• Custom State Management (Redux-like with lens-shmens)
Key Flows
a. Authentication Flow:
• Google Auth
• Apple Auth
• Session Management
b. Data Synchronization:
• Offline/Online sync mechanism
• Cloud storage sync
• Progress tracking
c. Program Management:
• Custom program creation
• Program sharing
• Exercise tracking
[Client Layer]
• PWA Container
• Service Worker
• Local Storage
• State Management
• UI Components
[API Layer]
• API Gateway
• Lambda Functions
• Auth Handler
• Program Handler
• Exercise Handler
• Stats Handler
[Storage Layer]
• DynamoDB Tables
• Users
• Programs
• Progress
• Statistics
• S3 Buckets
• Static Assets
• User Data
• Program Data
[External Services]
• CloudFront CDN
• SES Email Service
• Secrets Manager
• Auth Providers
Important Details
• Offline capability mechanism
• Liftoscript evaluation flow
• Data synchronization patterns
• Security boundaries
• Cache layers
• API endpoints structure
Interactions to Highlight
• How the PWA handles offline/online transitions
• Program creation and sharing flow
• Exercise tracking and progress monitoring
• Authentication and authorization flow
• Data backup and recovery processes