that's an incredibly expensive and complex way to avoid some friction for some users. What about breaking changes to APIs? Do you end up with two completely sep

that's an incredibly expensive and complex way to avoid some friction for some users. What about breaking changes to APIs? Do you end up with two completely separate backends and DBs to maintain as well? Do you just completely clone your entire product every time a big change happens -- and do you hire enough new people to handle that work? Probably not, you probably just stretch existing engineers too far to maintain old stuff. Seems better to only introduce breaking behavior changes when they're really necessary, and move the entire product to the new design. And if a new feature or a change in nav is enough to lose you customers, then your product might not be that compelling in the first place.