Create a visual guide for listening to Tagium downloads

[flamboh]

Goal

Complete Tagium's core user journey by helping someone move from a downloaded Tagium track or ZIP archive to successfully listening in their preferred music app.

This is a product-education experience, not just a documentation dump. The final wording and media should be developed closely with Oliver and optimized for someone who has never worked with local music files.

Scope

Create a lightweight, static help page reachable before and after tracks are loaded. Cover:

• Spotify on desktop
• Spotify on iPhone/iPad
• Spotify on Android
• Apple Music on Mac
• Apple Music on Windows
• Apple Music on iPhone/iPad with Sync Library
• Apple Music on iPhone/iPad without a subscription, using manual device sync

Start with the common Tagium steps:

1. Download a track or library.
2. Extract the ZIP when downloading multiple tracks.
3. Find and retain the resulting MP3 files.
4. Choose a destination app and device.

Clearly distinguish Spotify's Local Files workflow from Apple's library import and device/cloud sync workflows. Do not imply that Tagium uploads files into either service.

Content and media

• Short, plain-language ordered steps
• Current annotated screenshots
• Brief videos or looping demonstrations where motion materially clarifies the flow
• Captions or equivalent written instructions for every video
• Troubleshooting for common failure modes
• Links to authoritative resources, including:
  • Spotify: Local Files
  • Apple: Import music on Mac
  • Apple: Import music on Windows
  • Apple: Use Sync Library
  • Apple: Sync with Finder
• A visible "last verified" date

Keep media optimized and lazy-loaded so visiting Tagium does not eagerly download several videos.

Product review checkpoints

• Approve the page outline and supported device paths
• Approve the written instructions before capturing assets
• Agree on which steps need screenshots versus video
• Review the first complete page for clarity
• Re-test every documented flow immediately before release

Acceptance criteria

• The guide is accessible before and after tracks are loaded.
• Each supported path ends by explaining where the tracks should appear.
• Subscription requirements and destructive sync warnings appear before the relevant actions.
• Every video has captions or complete accompanying text.
• The page is responsive, accessible, and understandable without media playback.
• Official external resources are linked for deeper troubleshooting.
• A user unfamiliar with local music can follow the guide from a Tagium download to playing a track.