Skip to main content

R.I.P. WYSIWYG - Results-Oriented UI Coming (Jakob Nielsen's Alertbox)

Saw this on ProFox (thanks AGAIN , Malcolm)

It's interesting that Neilsen jumps over the new "results-oriented user interface", as noted by Office 12's interface. His big statement: "We know from user testing that users often demand that other user interfaces work like Office"

It will be interesting to see how this plays out - but keep the key poitns in mind from the new Office 12 interface - it's still all about the document-centric vision.

What do I mean by that? The O/S used to be application-centric - that is you choose the application to do the job you need done. Windows (and the web for that matter) has always tried to be more
document-centric - you work in a document and choose the right tools to do the job.

This new results-centric approach says you choose the tools based on the results you want and it's the job of the interface to make it easier to show what the results are - in short, you don't have to deduce or figure out what the tools mean, the interface should make it plainly obvious to you.

MS has been doing this for a few years now -still it's very telling that Jakob Neilsen is noting the big change in Office 12 as the telling signpost for the next generation user interface.

His comment: "But Microsoft Word 2003 has 1,500 commands, and users typically have no clue where to find most of them." Well the question really should be - do you NEED 1500 commands? (ask that to any Fox developer who knows all about dBloat) - maybe the real solution is the 37signals approach of less is more.

Most people who are starting with word processing (and there are a lot of them) don't get the difference between spaces and tabs or tables or columns so having 20 different commands for each of them essentially creates the UI conundrum.

It's a good article to read though - whether or not you agree or disagree with his conclusion that the Office 12 interface is going to be the defacto standard.


Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…