I understand the theoretical upsides to one platform&#x2F;language to rule them all, absolutely.<p>I am saying that trying to re-write the layout engine, data layer and all the rest to make it work the same on both platforms is not only a massive undertaking - it is ignoring the reason the platforms diverge to begin with.<p>iOS has features Android doesn&#x27;t and vice versa. Something that works on both platforms is always going to be a second-class citizen - it&#x27;s the lowest common denominator.<p>I don&#x27;t want the lowest common denominator because it&#x27;s &#x27;easier for developers&#x27;. I want the best stuff.<p>The theoretical technical debt due to writing on different platforms is why we have software architects and senior developers.<p>Really, I&#x27;ve been part of a dev shop that does ios&#x2F;android - the biggest hurdle is people problems, not code. People who don&#x27;t know what a good app is or have any taste so they say first show me, then I will start asking for changes at random while insisting on a tight deadline.<p>As for web&#x2F;ios&#x2F;android&#x2F;desktop - this is a rare bird, if you need to support that many platforms, you can afford an architect and some smart people.