Apps and GUI
So far, there are two broad approaches to app GUI. The approach adopted by Apple is to produce two different apps oriented toward cursor and touch, respectively. The approach adopted by Microsoft is to produce a single app.
From the perspective of usability, Apple clearly triumphs over Microsoft. The fundamental characteristic difference between mouse and finger calls for distinct sets of GUI considerations. Mouse may perform double click that's awkward for fingers. Imprecise fingers often justify big buttons that appear dumb for mice. Although Microsoft Surface might cost less than a MacBook plus a iPad, the user experience simply isn't right.
From the perspective of app programming, there is a case for Microsoft's universal approach that a single app is easier to maintain than two apps. Apple partially addressed the issue with the introduction of M1 that may run iOS apps on macOS, at the cost of clumsy GUI.
There is a possible third approach that separates app logic and GUI. Single app logic may be bundled with different GUI's to produce apps oriented specifically toward cursor and touch, while reducing maintenance costs. Whether it's a polymorph universal app or distinct binaries, the third approach is clearly desirable. However, it requires good software engineering to separate app logic and GUI, even without the help from Apple or Microsoft. Will the third approach ever become popular? Will Apple and Microsoft provide production support?
Comments
Post a Comment