How vavakado/everyframe works
Main Components
A. Frontend Layer:
• Single Page Application (SPA) built with Rust (likely using a framework like Yew or Leptos, given the web assembly approach)
• Static assets (from the assets/ directory)
• Service Worker (sw.js) for PWA capabilities
• Web Assembly Module (compiled Rust code)
B. Application Core:
• Task Management Logic (contained in src/app.rs)
• Core Business Logic (src/lib.rs)
• Application Entry Point (src/main.rs)
┌─────────────────────────────────────────┐
• Client Browser │
• ┤
• ┌─────────────┐ ┌─────────────┐ │
• Static │ │ Service │ │
• Assets │ │ Worker │ │
• ┘ └─────────────┘ │
• ┌─────────────────────────────────────┐ │
• Web Assembly Module │ │
• ┌─────────────┐ ┌─────────────┐ │ │
• App │ │ Core │ │ │
• Component │ │ Logic │ │ │
• ┘ └─────────────┘ │ │
• ┘ │
• ┘
Key Relationships to Highlight
• Service Worker ←→ Static Assets (caching)
• WASM Module ←→ Browser Runtime
• App Component ←→ Core Logic
• Static Assets → Client Browser
Additional Elements
• A build pipeline section showing:
• Rust Compilation
• Trunk bundling
• Asset processing
Important Notes
• Version information for major components
• Local storage/state management flow
• PWA installation flow
• Entry points clearly