How naserelziadna/doddle works
Main Components
a. Client-Side Architecture (Primary Focus)
• Flutter UI Layer
• Application Layer
• Domain Layer
• Platform-Specific Implementations
b. External Integrations
• Social Media Sharing
• Device Storage
• Google Ads Integration
Detailed Component Breakdown
Frontend Layer (Presentation):
• Canvas Screen (Main Drawing Interface)
• Home Screen
• Preview Screen
• About Me Screen
• To the common widgets and tools components
Application Layer:
• BrushSettingsProvider
• CanvasProvider
• ConfigProvider
• EffectsProvider
• RecorderProvider
• RouterProvider
• ThemeProvider
• Connection to Services:
• NavigationService
Domain Layer:
• Models Section:
• DrawController
• Frame
• Point
• RecorderState
• Stamp
• Effects Models
• Value Objects:
• ToolTypes
┌─────────────────────────────────────────────────┐
• Presentation │
• ┤
• Application │
• ┤
• Domain │
• ┤
• Platform Integration │
• ┘
Important Flows to Highlight
Drawing Flow:
User Input → SingleGestureRecognizer → DrawController → CanvasProvider → Sketcher → Screen
Effect Processing:
EffectsProvider → Various Effects (Glow/Normal/Spray) → Canvas
Recording Flow:
RecorderProvider → Frame Capture → Video Generation
Additional Details
• A small section showing the file structure organization
• Notes about the provider pattern implementation
• Separation of concerns between layers
Remember to emphasize the reactive nature of the application through the provider pattern and how it manages the state of the drawing canvas and tools.
This architecture should be represented in a way that shows both the high-level structure and the detailed implementation of key features like the symmetrical drawing system and the brush effects pipeline.