How maycon-crz/sdui_craftd_getx works
Main Components
• Flutter Frontend: Represent the overall Flutter application. Since this is a cross-platform project, include representations for Android, iOS, web, and desktop clients if needed.
• SDUI Engine: Since the project is built around a server-driven UI, illustrate the component or service that handles the dynamic JSON definitions (from the PHP server) and compiles them into Flutter views.
• API/Networking Layer: Include an API layer with components like the “rest_client.dart” and “api_path.dart”. This layer is critical for integration with the external PHP server.
• Local Database: Show the ObjectBox storage component with its generated files (objectbox.g.dart, database definitions) which are used for caching or offline storage.
Relationships and Data Flows
• UI and modules with the local database component (ObjectBox) to indicate state persistence and caching.
• Flow within modules (authentication: loginPage → loginController → loginRepository, etc.) to emphasize MVC/MVVM style separation using GetX.
Architectural Patterns and Technologies
• Multi-layered (modular) architecture, showing how modules are isolated by their responsibilities.
• That this SDUI approach involves a dynamic UI generation, so the JSON served by the PHP backend is “compiled” for Flutter representation.
• ObjectBox integration—mention both the dependency configuration (in pubspec.yaml) and the generation of objects (objectbox.g.dart) as part of the database layer.
• Use clear labels on each component (e.g., “Authentication Module”, “Home Module”, “API Client”, “SDUI Engine”, “ObjectBox Database”).