How mamarco13/emoodiario works
File structure
• Top-level directories:
• android, ios, linux, macos, windows, web → platform hosts & native code (Gradle, Xcode, CMake)
• lib → the entire Flutter/Dart codebase, subdivided into:
– constants (emotion definitions, resource paths)
– models (e.g., MediaFile, representing a day’s media)
– screens (Calendar, EditDay, Video, FullscreenImage)
– utils (EmotionUtils, FFmpegHelpers)
– widgets (custom UI components)
• assets/audio & assets/readme_images → bundled media & documentation images
• pubspec.yaml / pubspec.lock → dependencies, including FFmpeg plugin
• test → widget tests
• No remote backend or network-related files: data is local (likely file system or embedded DB).
README for insights
• Four core UI flows:
2. Edit_day_screen (enter title, phrase, attach ≤3 media, assign 1–2 emotions with slider)
3. Video_screen (configure & generate month-summary video, choose music, filters, random order)
4. Fullscreen_image_page (view/download media, minimal UI)
• FFmpeg is used at runtime to stitch media clips into videos (via a custom helper).