3 ms·

If it's a competitive advantage for your desktop product to use the native system frameworks with the platform preferred language (Cocoa/Swift or UWP/C#), I bel

If it's a competitive advantage for your desktop product to use the native system frameworks with the platform preferred language (Cocoa/Swift or UWP/C#), I believe its just as easy to justify the development time and cost to build your product today as it was 10 years ago. The main change I see is 2 things... 1. Companies now write all internal software using the web both for deployment and accessibility reasons and for storing things in the data center. 2. Consumers have mostly moved on to mobile devices. Honestly, if you need a desktop platform at home for anything other than hard core use cases (photo editing, software development, music production, etc.) those tools have largely been written and established.

zwieback 8y ago
> Honestly, if you need a desktop platform at home for anything other than hard core use cases (photo editing, software development, music production, etc.) those tools have largely been written and established. Yes, and many of them do not make a convincing case for "native=high performance"
foobarbazetc 8y ago
Our desktop app is an Electron app that adds features to our web app while “containing” it. The justification for pure native apps just isn’t there. Engineering effort + maintenance costs are too high. That, and NS* frameworks just kind of suck. Apple is trying to change that with the UIKit port to macOS but the apps that use it look and feel terrible (Home being one example) right now.