> The problem is coordination cost. If you want to launch new features and experiments here, there and everywhere, then the coordination complexity increases nonlinearly with the number of platforms.

Why not use a common library, where platform teams can update what features they use from it at their own pace?

Or why not use some other tech that allows multi-platform native shipping? The company I just started at, RemObjects, builds software for Mac and Windows (and iOS etc) from a common codebase. They just keep the UI separate, and all that is done when there's a new feature is _only_ UI layer coordination.

So an app has a C# (say) or Go codebase, and a UI layer in WPF and Cocoa.

I feel like coordination cost goes way down with both of these:

a) Library approach: central functionality, platform teams not tied to specifics

b) Shared codebase where all logic lives: platform teams do only UI

Edit: forgot to add, all this is can be across languages, ie maybe you have a Go shared library and write your Cocoa UI layer in C#, that's fine, their tech makes it all interop.