I think this is one of the biggest issues with SaaS. I appreciate that a stable revenue source is necessary for ongoing development, but UX decisions are much h

I think this is one of the biggest issues with SaaS. I appreciate that a stable revenue source is necessary for ongoing development, but UX decisions are much harder to evaluate. If I purchase a desktop application and opt not to upgrade, that's useful data to have. If you jam a UX update down my throat and I don't cancel my subscription, that doesn't mean you made a fantastic UX decision. It generally means the cost of changing is too expensive or, more likely, you've locked my data up in a format not easily exportable. I think it'd be nice if our tooling made it easier to support multiple "versions" of a deployed application. As it stands, it's far too expensive and error-prone to let customers opt into UI upgrades. As a product consumer, I can't stand continuous deployment. It just means my workflow can break at any time.