#user-flow

[peacefulstranger-blog]

The wireframe should be detailed showing what each element does, however simple enough to have a narrative and follow.

[peacefulstranger-blog]

Here is a good example of a thorough wireframe and concept screen write up.

[peacefulstranger-blog]

Here is a simple example that someone has created to allow people to work from. There are also many softwares that allow people to do this effectively and quickly. Although they might not be the best looking they serve a purpose.

[peacefulstranger-blog]

Obviously applications can be very complicated and It’s important to look at how the user will use the application and interact with it in the easiest possible way.

[ciaranhan]

Part II: Less Steps more Sign Ups - Visible.vc

In the last 2 months we started to revisit the first experience you get when you land on Visible. It led to a lot of great conversations and we learned…

[monikahalim-blog]

Too often when people design experiences, they start from the screen. They think “oh, people need to do x” and they start laying out a screen that will support that task. The problem is that not enough designers think through what that “task” really entails. Tasks don’t live in a vacuum. People come to them from somewhere. They go somewhere afterward. They perform them in different environments with different levels of attention and varying amounts of time. An interaction on a screen represents a single moment in time. The user interaction encompasses that moment and everything that surrounds that moment. Good interfaces take these differences into account. They support most of the likely behaviors and environments and prevent the truly undesirable ones. Good design doesn’t lose data or state just because a user has performed an action in a surprising way. Good designers need to think through all possible flows and take user context into consideration before even thinking about screen interactions.

“Mobile First? Not So Fast.” by Laura Klein https://medium.com/p/728dd6a6c5fd