How apliarte/flutter-toktik works
Project type and purpose
• This is a cross-platform Flutter app named “Toktik” for playing local vertical videos.
• There is no remote backend: videos live in the local file system (assets/videos or downloaded into storage).
• Architecture follows a layered, domain-driven approach with Presentation → Domain → Infrastructure.
File structure
• Top-level directories:
• android, ios, linux, macos, windows, web: platform-specific Flutter host code
• lib: the Flutter “core”
• assets: holds placeholder for downloaded videos
• test: widget tests
• Under lib:
• config: theming and helper utilities (human_formats, app_theme)
• domain/entities: pure data models (VideoPost)
• infrastructure/models: mapping between domain entities and raw data sources (LocalVideoModel)
• presentation:
– providers: state management classes (DiscoverProvider)
– screens: UI pages (DiscoverScreen)
– widgets: reusable UI (video player, scrollable views, buttons)
• shared/data: a hard-coded list of video metadata (local_video_posts.dart)
• No HTTP clients, no external services, but uses video_player plugin under the hood via Flutter engine.
Extract insights from README
• All videos are local and must be named 1.mp4…8.mp4 in assets/videos (or device storage).
• No cloud-based data source: purely local playback demo.