Developers struggle to organize multi-project workspaces
Developers working across several projects or nested repositories struggle to find the right files and keep project roots distinct in editor workspaces. Folder-based workspace layouts can flatten nested projects, show unrelated files, or make it awkward to include a few files from outside a project folder. The reported workarounds include opening an entire solution or manually tracking project folders, while some users also want faster ways to find and switch between saved workspaces.
For developers working across multiple projects or monorepos. Mentioned from Oct 2017 to Aug 2026 on product forums and GitHub.
13 different people described this problem in 8 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 5.2/10
- Frequency
- 9.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 4.7/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
The only workaround i have currently is to include my entire solution which isn't very desirable
Obviously working on 1 project, the file explorer is very "cluttered" with irrelevant stuff
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 11 more quotes from people who have this problem
- Current workarounds, existing solutions and risks