How kefirchk/animatica-frontend works
Project type and purpose
• This is a single‐service frontend application built on Streamlit (Python) that provides a UI for Animatica’s video‐generation API. It automates page rendering (home, auth, pricing, about), static asset hosting, user authentication, subscription/payment flows, and calls out to an external backend API for actual video generation.
File structure
• Top level
• app/ ← Streamlit app root
– Dockerfile ← container definition
– requirements.txt ← Python deps
– src/ ← application source
• app/src
• main.py ← Streamlit entry point
• configs/ ← environment‐driven endpoint and feature flags
• renders/ ← functions that build Streamlit page layouts
• services/ ← business‐logic layer for auth, payment, animations
• templates/ ← Jinja or HTML snippets used in renders
• views/ ← high‐level page controllers tying renders + services
• assets/ ← static CSS/images used by pages
• Other files
• README.md ← deployment steps, purpose
• Docker integration
• .gitignore, pyproject.toml
README for additional insights
• Describes local and Docker deployment
• Points to an external API (API_URL) for actual work
• No backend code here—this is the UI only
Detailed checklist
– Frontend container boundary
– Entry point (main.py)
– Config module reading .env/API_URL
– Service modules (animation, auth, payment)
– External API endpoints
– Renderers + templates feeding Streamlit UI
– Static assets folder
– Docker build & run relationship