3 ms·
The real head scratcher is that it's not really that big a deal to port your iOS app to the Mac, development-wise. You're probably using objective C or Swift al
by ryandrake 8y ago
The real head scratcher is that it's not really that big a deal to port your iOS app to the Mac, development-wise. You're probably using objective C or Swift already, so no need to switch language or libraries. If you've properly separated your ViewControllers from your business logic, then you can share a huge portion of your existing code base. If you have an iOS app, you're already between 50-75% of the way to having a great Mac app.
The most important problem to solve is envisioning the UI of your app in a world of mouse/keyboard input, arbitrarily resizable windows, context menus, and how to properly move from iOS UI conventions to Mac UI conventions. This is critical in order for the app to look like it belongs on the platform.
My beef with Marzipan is they're basically saying, "LOL don't bother with that," so yea, I agree the most likely scenario is my future Mac desktop full of Marzipan apps is going to look like a desktop full of little phone windows with neanderthal phone-oriented interfaces because developers can't be bothered to re-think their UI a little.
- adamnemecek 8y agoI agree for the most part but up until recently (2016?) I remember that the ViewController life-cycles were actually pretty different. The problem with AppKit vs UIKit is that most of the things seem to be the same until they are not. At that point, you try to hack AppKit to behave like UIKit (probably cause you have some code already written for UIKit) which generally turns out to be a fools errand. For example, I hate the usage of the Flyweight pattern in AppKit. UIKit doesn't suffer from this.