How benoiteirik/theochrone-mobile works
Main Components
a. Frontend Layer:
• Nuxt 3 Application Core
• Pages (fest, index, martyrologe, mass, settings)
• Components (Layout, Nav, UI components)
• Stores (using Pinia - fest, martyrologe, mass, nav, search)
• Vue Components Structure
• Asset Management System
b. Mobile Integration Layer:
• Capacitor Bridge
• Native Android Implementation
• Platform-specific Features
c. State Management:
• Pinia Stores
• Composables Layer
d. Utility Services:
• Image Handling
• Settings Management
• Internet Status Monitoring
• Back Button Handling
┌─ Client Layer ─────────────────────┐
• ┌─ UI Components ───┐ │
• Layout │ │
• Navigation │ ┌─ Pages ─┐ │
• UI Elements │ │ - Fest │ │
• ┘ │ - Mass │ │
• etc. │ │
• ┘ │
• Application Core ────────────────┤
• ┌─ State Management ┐ │
• Pinia Stores │ │
• ┘ │
• ┌─ Composables ────┐ │
• Settings │ │
• Image Viewer │ │
• Internet Status│ │
• ┘ │
• Platform Bridge ────────────────┤
• Capacitor │
• Native Layer ──────────────────┤
• Android Implementation │
• ┘
Important Elements to Highlight
• Bidirectional data flow between stores and components
• Capacitor plugins integration points
• Relationship between composables and components
• Asset management flow
• Build/deployment pipeline
Specific Implementation Details
• Vue Calendar plugin integration
• How image resources are managed across different screen densities
• How the martyrologe and fest features interact
• Settings persistence flow