IdeaSift

Developers struggle to keep editor settings portable and machine-specific

Developers using editors on multiple computers want consistent settings, but some preferences should remain local to a particular machine. Existing sync options can restrict which Git backends are usable, while stale local settings can overwrite newer synced ones. A related need is applying different preferences to particular files when language-wide settings do not fit.

For developers who use editors across multiple computers. Mentioned from May 2018 to Oct 2023 on Bluesky and GitHub.

4 different people described this problem in 4 separate discussions.

Week of 2026-07-13: 0Week of 2026-07-20: 0Week of 2026-07-27: 0Week of 2026-08-03: 0Week of 2026-08-10: 0Week of 2026-08-17: 0Week of 2026-08-24: 0Week of 2026-08-31: 0Week of 2026-09-07: 0Week of 2026-09-14: 0Week of 2026-09-21: 0Week of 2026-09-28: 0
0 mentions in the last 12 weeks
Indie fit
3.0/10
Pain
6.0/10
Frequency
5.8/10
Willingness to pay
0.0/10
Momentum
5.0/10
Who pays
Professionals
Competition
Medium
Build difficulty
Medium

What people said

Quoted word for word. Follow a link to read the whole discussion.

  1. The JetBrains IDE Settings Sync is so frustrating. Oh, you opened the IDE on a computer you haven't used in months? Why don't we UPLOAD your outdated settings and overwrite your newer ones already in the cloud
  2. What if we wanted to use a Github Enterprise backend, or any other git remote ( Gitlab, Gogs, whatever... ) ?
    jmarandet on GitHub (microsoft/vscode)Mar 2020+76 upvotesAsked for a tool
Build brief

See what to build and who will buy it

  • 1 product idea with the smallest useful version and pricing
  • 4 places to find your first customers
  • 2 more quotes from people who have this problem
  • Current workarounds, existing solutions and risks