How yumnumm/eqmonitor works
Below are the detailed instructions tailored to this project:
Relationships and Data Flow Between Components
• Also, show how the edge API interacts with databases (Cloudflare D1/Supabase) and caching (Cloudflare KV) systems.
Architectural Patterns and Key Technologies
• Client-side: Emphasize the use of a modern UI framework (Flutter) with reactive state management (Riverpod and Flutter Hooks). Mention that API interactions are handled through Dio and a custom eqapi_client.
• Service integration: Clearly mark where JSON serialization and data modeling occur using libraries (freezed, json_serializable) and highlight how the app integrates with maplibre_gl for mapping.
• On the service tiers: Illustrate microservice-like components (or containerized services managed by Docker Compose) and mention that multiple technologies (Node.js, Bun, Golang, C#) are used, which might interact as separate processes or services.
Packages/Submodules
• That these packages help encapsulate core functionalities such as parsing earthquake data or handling notification payloads.
• Clarity and not over-complicating details: separate the system into as many clear and distinct parts as possible as outlined above.
• Use annotation: provide notes or labels where necessary to describe responsibilities (for example, “Handles earthquake notifications” on the backend, or “Manages state with Riverpod” on the client).