How gotolstoy/tolstoy-flutter-sdk works
┌─ Presentation Layer ─────┐
• (Widgets & Screens) │
• Business Logic Layer ───┤
• (Services & Models) │
• Core Layer ────────────┤
• (Configuration & Types) │
• Utils Layer ───────────┘
Module Organization
Feed Module │ Rail Module │ Assets Module │ Products Module │ API Module
Component Details
For each module, show the following hierarchy:
• Widgets/Screens (Top)
• Services (Middle)
• Models (Bottom)
Key components to highlight:
a) Feed Module (Purple):
• FeedScreen & FeedView
• Feed-related widgets (FeedAsset, FeedOverlay)
• Product integration components
b) Rail Module (Blue):
• Rail & RailWithFeed widgets
• RailOptions configuration
• Rail-specific services
c) Assets Module (Green):
• Asset handling services (Image, Video)
• Asset models and types
• Asset widgets hierarchy
d) Products Module (Orange):
• Product models
• Product loaders (Batch, Simple)
• Product utilities
e) API Module (Red):
• TvConfigProvider
• API services
• Configuration models
• Configuration flow from API to modules
• Asset loading paths
• Product data distribution
• Widget composition relationships
Integration Points
External integration points:
• Analytics module connections
• API endpoints
• Asset service connections
🔷 Widget Component
🔶 Service Component
⬡ Model
↔️ Two-way Data Flow
→ One-way Data Flow
How the TvConfigProvider acts as a central configuration source.
3. Relationship between Feed and Rail components, as they can work independently or together.
Products module's integration with the feed display system.
Level of Detail:
• Keep high-level components visible at first glance
• Use expandable/collapsible sections for detailed implementation
• Maintain clear boundaries between modules while showing their interactions
• Configuration and type definitions without overwhelming detail
• Nested components
• Grouping of related elements