3 ms·
“These apps might have the same overall feel as their mobile counterparts but key user interactions will have to be updated for the desktop environment” Hm see
by sgillen 8y ago
“These apps might have the same overall feel as their mobile counterparts but key user interactions will have to be updated for the desktop environment”
Hm seems like this mitigates some of the advantage of porting over to macOS this way. If you have to make nontrivial changes to your code anyway to have it work right.
This just feels like something no one was asking for, but I guess there must be a community waiting for this or some reason for Apple to put the time in.
- jonhendry18 8y agoI think mostly it'd consist of changing the code to use mouse or trackpad events, which may be different from how the app would use touch events on mobile. Maybe adding support for a menu bar.
- esturk 8y agoFor porting maybe, but after the initial framework is released, new apps will just be built with both platforms in mind. Newer versions of UI Kit will probably shift people in the Apple Kit direction and then slowly deprecate all no compatible features. So unless app developers don't upgrade their app, sort of like moving to 64 bit, then yes everything would be a non trivial effort.
- veidr 8y agoThere are a lot of apps where you want to be on the desktop and mobile (with your data in Le Nuage, say). I've done a fair it of that kind of Mac/iOS development (although not in the last couple years). It was always super annoying to have to isolate your data and business logic in the shared code part, and then do you UI and platform code in two totally different ways. I think a.) every Mac/iOS developer doing that kind of "phone and desktop" type of app wants this, and b.) this way makes it easier to do "mobile first" which seems to be what most people want to do these days.