4 ms·
I'm not sure whether native look and feel is ever important point. At the moment I cannot think of any enterpise-ish application that does not ignore native pla
by dfox 12y ago
I'm not sure whether native look and feel is ever important point. At the moment I cannot think of any enterpise-ish application that does not ignore native platform look and feel.
And for both Delphi and now .NET, there is significant market for third party components that look purposefully non-native.
- jbergens 12y agoI think Java was almost killed by not having native look and feel in Swing. There is probably still a lot more desktop applications written with native Windows look and feel than with Qt or Java. It is still a problem with mobile apps that users can feel confused over some gui's that are made with html+css (or something else) and does not follow the native look and feel for the platform in question. It will probably get better over time but it has been an obstacle for many, many years.
- protomyth 12y agoI think the native look and feel is important because the emulated interface always seem to have flaws and added to the training cost of users. Each new version of Windows would bring problems for the emulated interfaces where the tools using the native widgets didn't have the same problem. Worse, something like Squeak which is basically running a foreign OS in a window with garish colors. I know a lot of enterprise apps go off into the weeds, but their success is driven by external factors. Successful tools really need to appeal to a broad group of developers. I really think a native widget version of Smalltalk that included the database access could have done a fine job, but it always seemed with Smalltalk that the NIH syndrome was so high and they could build their own things better. Its like they didn't respect any platform they were running on.