Product decision: make The Shed workspace-first, not timer-first

[Dandiggas]

Product question

Is The Shed primarily:

1. a practice tracker with media tools, or
2. a practice workspace that happens to track time?

Recent real-world use points strongly toward option 2.

The user needed to quickly upload an MP3, slow it down, and work out a part. The timer/session setup model made that feel clunky. The timer is useful, but it should not be the thing the whole app is organised around if it blocks the actual practice workflow.

Proposed direction

Treat the app as a persistent practice workspace:

• Media first: playlist, MP3 upload, YouTube, sheet music.
• Tools always available: slowdown, loop, tuner, metronome, notes.
• Timer runs in the background or starts optionally.
• Session metadata can be added/edited later.
• The workspace remembers what the user was doing.

Decisions to make

• Should media tools be usable without starting a timed session?
• Should timer start automatically when the user starts playback / begins work?
• Should the timer be optional, backgrounded, or always visible but non-blocking?
• Should session metadata be captured after the fact instead of before practice?
• What is the default landing view after login?

Acceptance criteria

• Decide the product model: workspace-first or timer-first.
• Document the chosen model in the issue or a short design note.
• Identify which pages/components need to change if workspace-first wins.
• Define the minimum viable workspace-first flow.
• Convert the decision into implementation issues if needed.

Suggested MVP flow

1. User logs in.
2. App opens last workspace by default.
3. User can immediately play existing media or add new media.
4. User can slow down / loop / use metronome / use tuner.
5. Timer can start, pause, stop, and save practice data — but it does not block access to the workspace.