[robertlagrant]

Course you can. Just have an opt-in new UI. Confluence has done that really well, for example. CircleCI have been doing it.

Sometimes I'd love to work at Google to really understand how it works. I'm sure change is hard, but I can't understand why from the outside.

[mosfets]

Once you have worked with a product doing these kind of things, you'll understand you'll need to double or even triple the efforts to be able to support two branches of the same feature. Of course this doesn't apply to simple applications.

[robertlagrant]

Yes, I know.

If you're implying Google can't afford it but CircleCI can, then while I understand your logic, I disagree with your understanding of reality.

If you're not, then I disagree with your understanding of logic.

[oblio]

Confluence removed quite a few features from the new UI.

I don't know Circle CI but they probably have 2 orders of magnitude fewer users. Also in my experience with CI tools, few users actually manage them for many people and those people are either experienced or quickly become experienced with the UIs. They are usually not the average user getting confused by UI changes.

[robertlagrant]

> Also in my experience with CI tools, few users actually manage them for many people and those people are either experienced or quickly become experienced with the UIs. They are usually not the average user getting confused by UI changes.

Well regardless, they still pulled off the harder technique.

[bigtones]

That Atlassian Confluence model you gave had some serious issues, they they are going to turn off the option to keep the old UI as well, and it is an enormous strain on Engineering resources to keep two different versions of an entire application UI up to date.

One company that had done this a bit better was Salesforce with the old UI / Lightening UI switch.

[robertlagrant]

Yeah but it's necessary. The old UI would cause people to leave; the new one is actually really good.