UI Version Pinning for SaaS (opt-out from forced redesigns)
Problem
Users are routinely frustrated when SaaS products force UI overhauls that break their workflows — APIs keep versions around, but no site or app lets users stay on a familiar interface version. The pain is recurring (every redesign cycle) and commenters confirm opt-in/opt-out mechanisms are rare, ad-hoc, and disappear quickly.
Opportunity
A drop-in SDK/middleware (React/Vue compatible) that snapshots UI versions server-side and lets authenticated users pin a preferred version, with backend-aware API version negotiation — so product teams can ship redesigns without stranding power users on deadlines.
Market analysis
The user pain is genuine and every redesign cycle re-proves it (Snapchat's 578k-signature rollback petition, Chrome 71 backlash), but the buyer is the product team that shipped the redesign — the same team that wants everyone off the old UI. Technically this is a solved pattern (feature flags with per-user targeting); the unsolved part is that maintaining N parallel UI versions multiplies cost, which is exactly why vendors kill 'classic' UIs quickly.
Market · Product/engineering teams at SaaS companies with power-user bases (enterprise tools, productivity apps); demand signal comes from recurring redesign backlash rather than an expressed tooling budget.
Pricing · Feature-flag platforms are the comparable: LaunchDarkly ~$10/seat/month starter scaling with MAU ($8-10 per 1K client-side MAUs), Flagsmith free/open-source to ~$45/month, GrowthBook $40/seat Pro. A UI-pinning SDK would face this as the price ceiling.
Pros
- + Recurring, emotionally intense user pain with famous public episodes.
- + Enterprise SaaS with locked-in power users has real retention economics around redesign risk.
- + SDK + version negotiation is a coherent technical story for a solo builder.
Cons
- − Misaligned buyer: the team paying is the one that wants to retire old versions.
- − Feature-flag tools (LaunchDarkly, Flagsmith, GrowthBook) already do per-user version targeting.
- − Long-tail cost of maintaining multiple UI snapshots lands on the customer, killing adoption.
Existing / similar tools
Source
Hacker News (Ask HN)
The reason nobody sells this is not technical, it is incentive structure: Gmail’s “switch to classic” and Slack’s opt-in rollouts were transitional mercy, retired the moment usage data allowed it, because every week of dual UI is double the bug surface and half the analytics clarity. A viable version of this idea stops selling “let users pin forever” (a liability vendors will not buy) and sells time-boxed migration insurance instead: pinning with a countdown, telemetry on which workflows users have not re-learned yet, and a report telling the product team when it is safe to sunset the old UI. That aligns with the buyer’s actual job — shipping the redesign without a support-ticket spike.