3 ms·

Oh, do not worry... it's coming. M1 > SwiftUI > MacCatalyst = Write once, run anywhere. Watching the iPadOS and MacCatalyst APIs mature says different form fa

Oh, do not worry... it's coming. M1 > SwiftUI > MacCatalyst = Write once, run anywhere. Watching the iPadOS and MacCatalyst APIs mature says different form factors will emphasize certain workflows over others, but overall, feature parity is and will be a priority across the device lineup, iPhone included... Though it makes me sad... soon after their unified OS is realized, Sherman's coming by with his hammer. It'll be beautiful while it lasts.

arecurrence 6y ago
I don't know if you've tried going from a universal app to Catalyst but it feels very subpar compared to the Mac app variant. EG: Catalyst does not have the proper sidebar support that a Universal App with a Mac target has. Also there's no 'click' in Catalyst (at least not in the way that those components work on the Mac... they feel quite different). The experience is definitely "iPad" with Catalyst instead of "Mac". I believe Apple is going all in on the Universal App model. You can already get most of the way there today with some limitations (many libraries don't support Mac yet). Making different targets for each hardware with a 99% Shared code base is really excellent.