F
Filo
Description:
Add a dedicated “Recent Projects” folder to the Projects browser that automatically lists the last few projects the user has opened (for example, the 5–10 most recent). This folder would be available alongside the existing folder hierarchy and root, providing a fast shortcut to jump back into recently used projects without needing to remember their exact location.
Problem:
Users often organize their projects into multiple folders for different purposes (gigs, sessions, experiments, templates, etc.). In practice, this leads to a couple of common issues:
  • They frequently switch between several projects that live in different folders.
  • To reopen a recent project, they must remember:
- Which folder it lives in, and
- Where it sits inside that folder (especially if the folder contains dozens of projects).
  • Without a dedicated “recent” list, reopening a previous project can require:
- Navigating through the folder tree,
- Visually scanning long lists of project names, or
- Using search, which is slower for quick back-and-forth switching.
This slows down workflows where users are actively bouncing between multiple projects during a session or rehearsal and adds friction to a task that should feel instant.
Proposed Solution:
  • Add a
    “Recent Projects” virtual folder
    in the Projects list:
- Displays a configurable number of recently opened projects (e.g. at least the last 5; ideally user-configurable to 10, 20, etc.).
- Projects appear in reverse chronological order (most recently opened at the top).
  • Behavior details:
- The Recent Projects folder is automatically maintained by Loopy, with no manual organization required.
- Entries in the Recent Projects folder are
shortcuts/links
to the actual project files in their existing folders; they do not move or duplicate the real projects.
- Each entry could optionally show:
- Project name,
- Original folder path (e.g. “Gigs / 2025-11-20 – Berlin Set”),
- Last opened date and time.
  • Optional enhancements:
- Settings for:
- How many recent projects to display.
- Whether to show a “pinned” section for favorites.
- Context menu item to:
- “Remove from Recent Projects” (without deleting the project).
- Platform-aware behavior:
- On iPad or macOS, Recent Projects could also appear in quick-access areas like the start screen or “Open Project” dialog.
Benefits:
  • Faster navigation:
    Users can jump back into the last few projects they were working on without navigating the folder hierarchy or remembering file locations.
  • Better for multi-project workflows:
    Ideal for users who constantly alternate between a couple of projects (e.g. rehearsal vs. performance version, or different setlists).
  • Less cognitive load:
    No need to recall which folder a project is filed under; “Recent Projects” acts as a short-term memory buffer.
  • Scales with large libraries:
    Even if a folder contains dozens of projects, the most relevant ones (recently opened) are always just one tap/click away.
Examples:
  • A performer rehearses three different show projects stored in different folders:
- Instead of navigating “Shows → Club Set”, then “Shows → Festival Set”, then “Rehearsals → Practice Rig”, they open all three once.
- After that, all three appear in “Recent Projects,” allowing rapid switching during rehearsal.
  • A user experiments with new templates:
- They open and tweak several template-based projects spread across “Templates,” “Experiments,” and “Live Sets.”
- The Recent Projects folder keeps these at the top, so they can easily return to yesterday’s experiments without remembering where they filed them.
  • A busy session workflow:
- During a recording day, the user jumps between a “Recording” project, a “Soundcheck” project, and a “Test” project.
- “Recent Projects” always shows these three at the top, reducing friction when moving back and forth.
This summary was automatically generated by GPT-5.1 Thinking on 2025-11-20
.