4 ms·

This is great. For those here commenting "why? My iPhone is very different from my iMac", an example: I am writing an iPad app for a client that has a lot of cu

This is great. For those here commenting "why? My iPhone is very different from my iMac", an example: I am writing an iPad app for a client that has a lot of custom Metal compute code. It is great that I can basically run that code on my iMac Pro as well, for rapid prototyping, and because having a desktop companion app makes a lot of sense. Right now though I have to be very careful how to share code between the two apps, mainly because UIKit is not available on the Mac. Unification would solve that headache for me.

sjwright 8y ago
What people who haven't written Mac apps need to realise is that many of the UI APIs are not even remotely shared between macOS (AppKit) and iOS (UIKit). Even the most basic concepts like colour are not handled uniformly. Having UIKit available on macOS doesn't mean you port over your iPad GUI and call it a day; you would still write a desktop GUI. But by having the same API means that your business logic and glue code doesn't get infected with quite so much platform-specific crap like UIColor vs NSColor.