Ahh, yes.
That's why I always think about UI. I probably spend 90% of my time making decisions on how I want UI to work.
You already saw how Apple have a concise UI by generally having only one thing in one place, resistance against hidden contextual menus, and some more.
So for myself at least, I make decisions on what a particular screen is supposed to do, then wrap UI around that particular goal. The order shouldn't really affect how it will behave; only that certain conditions be satisfied before allowing one to moving on/returning to the starting point.
I looked at my old post and thought that my analogy was weak. I will try and post a flowchart of what I usually do when working on the database.
HTH.
|