Oh good, another was to half-ass port things to Mac. Lovely. There's a reason people like native interfaces.
"No it's not like Java this time!" "It's not like Carbon!" "It's not Flash!" "Don't worry, it's no X11!"
If you care about the platform, go native. Learn the rules and look and feel. If you don't care that much? Maybe you should reconsider the port. You can't "click this checkbox for OS X", it doesn't feel right.
It doesn't really look like that's what this is, it's just a different way to wire up native UI components. You're still writing Objective C and using Cocoa.
I don't think you understand what React Native is.
It's just a way to use the underlying native UI. It's not a bunch of emulated components with a pluggable "look and feel". They're the real thing, just wrapped in a JS API.
No, I understand it generates native components. But if you're writing generic UI code and deploying it on a Mac without following platform conventions (about the menus, ways of doing things, etc) it will still feel 'wrong'.
"No it's not like Java this time!" "It's not like Carbon!" "It's not Flash!" "Don't worry, it's no X11!"
If you care about the platform, go native. Learn the rules and look and feel. If you don't care that much? Maybe you should reconsider the port. You can't "click this checkbox for OS X", it doesn't feel right.