Why our User Interfaces must be come Model Driven?

I referred to “Model Driven “ navigation last week, and got some reaction that we are already there with ArchestrA Graphics. This made me step and re read what I in the last blog, and realise that I had assumed some understanding.

Yes today ArchestrA Graphics are built into the model in the objects etc, this is a significant step from the classic InTouch like window which the graphics are independent of the model, just linked, but many applications do not build in navigation to the model. My actually intention was not just these graphics in the model but take the whole operational experience to  level, that the model and views into this model for operational control etc, can be independent of the device and layout. Also, the model must be able to change freely and not a characteristic of what device or who will engage with it.

Navigation needs to be a Natural Act!!!!

Last week I visited some sites and engineering houses as they developed new systems. What struck me was the amount of time, and effort we put into designing a forced navigation between screens and windows. Even though, I knew this in my mind, I asked Why?.

In designing navigational buttons,  thereby enforcing a method of navigating through the application, which then now needs to trained to the people. Why cannot the system has Natural navigation built from the application model.

So what is this about?