3 ms·
I agree. I don't think the experience is great, if you just run a mobile app on a desktop machine, but the great points are, that a) it is possible at all, so i
by _ph_ 6y ago
I agree. I don't think the experience is great, if you just run a mobile app on a desktop machine, but the great points are, that a) it is possible at all, so if nothing else works, you can run the mobile app on your computer, for many purposes, that is enough, and b) this gives a big incentive to the app developers to offer a proper Mac version too, which probably requires less work than ever before.
- skohan 6y ago> this gives a big incentive to the app developers to offer a proper Mac version too Maybe but I'm not totally convinced it's enough. For small apps which are only currently on iOS this might be interesting, but for the large pool of applications which currently target web, iOS and Android, doing extra work to support a mac branch of the application is still that: extra. Those users are already supported by your web application, and even if it's relatively less work than creating a separate native mac application, adding a mac branch of your iOS app will still add effort and complexity to implement and maintain. And that would be to serve what's probably a tiny minority of your active users.
- zepto 6y agoIn the classic sense of an SCM ‘branch’ you would be correct, however with SwiftUI you don’t need a branch to support MacOS. At worst you need a few #ifdefs.
- skohan 6y agoI mean a branch in the sense of branch of execution (#ifdef would be one way to do this) not in the sense of a source control branch.