Minchyn Project Structure and Organization

Frontend Directory Layout: #

The project follows a feature-based organization pattern for maintainability. The /app directory contains all screens using Expo Router’s file-based routing–each file automatically becomes a route. The /components directory is organized by purpose: /components/features/ contains domain-specific components (seens, streaming, marketplace), /components/ui/ houses the reusable component library, /components/layouts/ includes navigation and page layouts, and /components/shared/ stores cross-feature utilities. The /services directory contains API clients and business logic. The /store directory manages MobX state stores. The /hooks directory provides custom React hooks. The /constants directory defines theme, colors, and configuration. The /types directory contains TypeScript interfaces and type definitions.

Backend Microservices Structure: #

Backend code lives in /backend with multiple microservices: minchyn_backend/ is the main Django API service handling authentication, users, content, and social features. analytics_service/ processes event tracking and metrics aggregation. ml_service/ contains machine learning models for recommendations using PyTorch. video_processor/ handles media encoding and optimization. streaming-server/ manages live streaming infrastructure. recommendation_api/ is a FastAPI service integrating ML models with the main API. Each service has its own requirements.txt, Dockerfile, and configuration. Services communicate via REST APIs and message queues (Redis) for async operations.

Configuration & Documentation: #

Project configuration files live in the root directory: package.json defines frontend dependencies and scripts, tsconfig.json configures TypeScript compilation, app.json contains Expo configuration, docker-compose.yml orchestrates services, and .env stores environment variables (gitignored). The /docs directory contains comprehensive documentation organized by topic: /docs/developers/ has setup guides and standards, /docs/features/ documents major features, /docs/architecture/ explains system design, and /docs/api/ provides API reference documentation. README.md provides a quick start guide. Each major feature includes a dedicated documentation file explaining its architecture, API, and usage.