How rodrichie/bee-productivity-analyzer works
Project type and purpose
• This is a full-stack web application called “Bee Productivity Analyzer.”
• Front-end: React single-page application (SPA) that provides a chat UI, media upload, real-time camera integration, and data visualizations.
• Back-end: Python/Flask API server exposing REST endpoints and WebSocket events for real-time processing.
• Core functionality: AI-powered text and media analysis of beehive conditions, trend tracking, historical reporting, and real-time feedback.
File structure
• Top-level:
• Dockerfile, .dockerignore, .gitignore, .babelrc, package.json, requirements.txt
• README.md + API_DOCUMENTATION.md
• app/ (Flask application)
• app/controllers: API route handlers (analysis_controller.py)
• app/routes: route definitions (token_routes.py)
• app/handlers: domain-specific event handlers (media_events.py, socket_events.py, intergrated_handlers.py)
• app/services: business logic (data_integration_service.py)
• app/models: data and ML components (classifier, gemini_model, media_analyzer, trend_analyzer, reporting_system, knowledge_base, token, analysis_metrics)
• app/utils: cross-cutting concerns (auth, error_middleware, rate_limiter, session_manager, logging_config, feedback_system, progress_tracker, token_blacklist)
• app/static/js: React source code (App.jsx + component hierarchy)
• app/templates/index.html: single-page shell for React
• Other: package-lock.json, venv/
Extract architecture insights from the README
• REST endpoints for text queries, media uploads, token management
• Real-time WebSocket channels for immediate feedback
• React build step via Babel → dist/
• External dependency on “Gemini” AI API (requires GEMINI_API_KEY)
• Data visualization uses interactive charts (likely a JS charting library)