After years and years of hype, expectations, referrals, closed beta, has finally come to the much-vaunted Flow priori. FTP client, it was said, intended to give an alarm to the niche market.
The reactions of people were immediately divided between those who immediately fell in love, singing the praises of the GUI and its minute details, and those who, instead, have begun to show the direction of its numerous bugs and marketing hype around the application going to pose pseudo-geek empty glorification of mere functionality at the expense of the graphic details of the GUI.
We must say that it is not ipso facto lead to hype bad if this follows a product worthy of the hype. I do not agree, never agree with those who, in a spirit of elitism illusory, tend to denigrate without a foundation product, any product based only on evidence of marketing.
is not bad at all considering an application from the point of view of mere attention to visual detail. It 's a key element in the User Experience and should never be left out (as I often do, especially on Windows).
The problem here is that all this hype and attention to detail no doubt a product does not match up to it. This is well understood, not for the many bugs that plague the application (we are now accustomed to paying to be beta testers), but for a precise choice of Interface Design that, pretending to innovate, thrown in the trash usability.
single-window approach Flow pursues that does not fit the task for which it is proposed that is not the simple exploration and manipulation of folders in the remote but interaction between the local copy and one of these files remotely.
Historically this approach has a parent who can see it in action in any software is designed for operation diff / merge on files.
FileMerge Apple, for example.
Here the file is compared line by line with its antecedent or consequent seeking changes that will be appropriate to incorporate into the final version that we will consider.
task that is associated with an FTP client is just like the synchronized navigation, a first version control between local and remote upload and download files to and from remote locations. In other words, the interaction between local and remote. For this simple reason, Flow fails its task as it forces the user to have another application external open and active to carry out successfully what should be its primary purpose .
should in fact have a Finder window in support otherwise the user will be unable to do anything but operations on the remote folder from the folder in the remote, so closed and exclusive. The user is then
trapped in the application and to find a way out of the impasse must be used effectively to external lifeline.
Interface Design This is bad because it is one thing to look for support in specific applications for specific tasks beyond the primary task of the application (open a text file for editing from the same FTP client, for example), another is used to aid external to accomplish the primary task for which there is an ftp client.
I write this after taking over the entire test flow in the probationary period and that immediately jumps to the eye and confirmed in daily use.
nell'Interface Design Innovation is not 'famolo strange' or take, as in this case, a paradigm from an application (in this case, the Finder itself, the iApps, etc.) and carry no residue on a task different.
contamination, when can be filtered and take out only what can be useful in rejecting what, in terms of usability, creates dysfunction in effectiveness of the UI. Ben is
So the attention to detail of the UI but that comes after a careful study of the behavioral pattern user of your application and the tasks and sub-task that needs to be completed.
Much ado about less than nothing, so to speak.
0 comments:
Post a Comment