How wyattlin001/invest_v3 works
Project type and purpose
• This is a full-stack “Invest Simulator” platform consisting of an iOS SwiftUI front-end, a Flask-based REST API back-end, and a PostgreSQL database (self-hosted or via Supabase). It also integrates external services (yfinance for market data, Twilio for OTP SMS) and runs scheduled jobs (price updates, ranking calculations).
File structure
• Top-level directories:
• Invest_V3/ – iOS SwiftUI app (Views, ViewModels, Models, Services)
• invest_simulator_backend/ – Flask back-end (app.py, services/, SQL scripts, tests)
• dependency_analysis/ & dependency_reports/ – code analysis tooling
• Tests and docs at root
• Patterns:
• iOS uses MVVM (View + ViewModel + Service)
• Back-end uses a service-layer pattern (auth_service, db_service, trading_service, market_data_service, scheduler_service)
• Build/deploy scripts, Dockerfile, SQL schema scripts
README for technical stack
• Front-end: SwiftUI (iOS 15+, Xcode 14+), MVVM, Combine
• Back-end: Flask (Python 3.8+), RESTful endpoints, scheduler tasks
• Database: PostgreSQL via Supabase (Auth, Real-time, Storage)
• External services: yfinance, Twilio SMS
• Scheduler: periodic jobs (every 30s, 1m, 5m)
Key components
a. Front-end (iOS SwiftUI)
• Views (AuthenticationView, TradingMainView, etc.)
• ViewModels (TradingViewModel, ChatViewModel, etc.)
• Network/Service layer (TradingService.swift, SupabaseService.swift)
b. Back-end (Flask API)
• app.py (routing)
• Service modules:
• auth_service.py (OTP, JWT)
• db_service.py (CRUD)
• trading_service.py (buy/sell logic)
• market_data_service.py (yfinance integration)
• scheduler_service.py (job scheduling)
c. Persistence and real-time
• PostgreSQL (tables: users, portfolios, transactions, rankings)
• Supabase (authentication, real-time updates, optional as a BaaS)
d. External integrations
• yfinance API (stock price data)
• Twilio SMS (OTP delivery)
e. Scheduler subsystem
• Cron-style tasks invoking market_data_service and ranking updates
Relationships and interactions
• iOS App ↔ (REST calls) ↔ Flask API
• iOS App ↔ (SDK/API calls) ↔ Supabase Auth & Real-time
• Flask API → PostgreSQL (via db_service)
• Flask scheduler → market_data_service → yfinance
• Flask auth_service → Twilio SMS
• Scheduler triggers ranking and portfolio recalculations
Architectural patterns and design principles
• MVVM in the iOS client for separation of UI and business logic
• Layered service architecture in the Flask back-end
• Clear separation of concerns: Authentication, Trading, Market Data, Scheduling
• Use of BaaS (Supabase) for auth and real-time capabilities
• Stateless REST API with JWT tokens for security