I was researching on new technology and media for RIA and found Live Mesh. I found that it seamlessly connects your data through Windows PC, Mac, Mobile Phone, and other devices. It is an interesting concept and would we not want all our work to be seamlessly, updated wherever we are on the go?
Telstra is one of the iconic Australians. Today we are a company that
looks to the world of tomorrow. We're on the forefront of the
communications revolution. It's an exciting place to be. Working in
a multi-disciplinary team of human factors specialists, technology
specialists and software developers in our Chief Technology Office
(CTO) you will contribute to creating prototypes of emerging
The main purpose of this exciting role is provide interaction flows,
information architecture and user interface design to tangible
software and device prototypes.
What are the opinions here about what comes first, the Design or the
I am currently designing a web application from an existing windows
application. No decision had been made at the time as far as the technology
to be used, only that it would be a web application. So I designed like I
normally do, I composite/mock up designs in Fireworks, and then build the
our prototypes to users and have received a lot of great feedback and
Development has now decided to use Adobe Flex for the front end.
What about the data model or database design? Should we be considering that
separate from the technology?
Sometimes I think the data model should be made before the interface because
an interface that strongly reflects the data model is easier to use. That
is, users can more easily create a mental model of the data. Even a
task-based interface should account for that.
However, I've also run across many projects where the data gets modeled
based on how the user wants to approach the problem. This seems to be more
of a case in search and taxonomy however.