How psycho-baller/convo-topics works
Main System Components
The system architecture should be divided into these key components:
a) Client Applications:
• Expo Mobile App (iOS/Android)
• Next.js Web App
• Marketing Website
b) Backend Services:
• Auth Proxy Service
• tRPC API Layer
• Authentication Service (Auth.js)
• Database Layer (Drizzle ORM + Turso SQLite)
c) Shared Packages:
• UI Components (Tamagui)
• API Definitions
• Database Schema
• Authentication Logic
[Client Layer]
• Expo App | | Next.js App | | Marketing |
• (Mobile/Native)| | (Web App) | | Website |
• ↓ ↓ ↓
[API/Communication Layer] | |
• tRPC Router | |
• ↓ ↓ ↓
[Service Layer]
• Auth Service | | Local API | | Server API |
• (Auth.js Core) | | (Questions) | | (Backend) |
• ↓ ↓ ↓
[Data Layer]
• Drizzle ORM Layer |
• ↓
• Turso SQLite DB |
Important Relationships to Highlight
• Bidirectional communication between clients and tRPC router
• Shared package usage across applications
• Authentication flow through Auth Proxy
• Database access patterns through Drizzle ORM
Technical Stack Indicators
• React/React Native
• Expo
• Next.js
• Tamagui
• tRPC
• Drizzle
• Turso
• TypeScript
Development Workflow
A separate section showing:
• Monorepo structure (Turborepo)
• Shared package dependencies
• Build/deployment flow
Remember to emphasize the core functionality of question management and relationship building, as this is the primary purpose of the application.