One of Saturday's key features is the map view of your network. (so valuable is this map view that we actually had to fix a UX flow which wasn't allowing map discovery, because users wouldn't find it, but once they were shown it, their eyes lit up with joy)
Now that their eyes have lit up from the map view, we must ensure that the map view is all that it could be.
One issue about the map view is that it quickly becomes cluttered. This isn't an inherent thing, it's a UI thing. High density networks can always be visualized in a more simplified manner.
We began with many different versions and explorations, and I took the core of each and tried to simplify it as much as I could.
Let's take a closer look at some of these.
While I hope these designs speak for themselves, allow me to explain some reasoning behind my decisions. In both designs I removed the unnecessary purple stroke, especially since it cognitively collided with users' expectations about color meaning, since color-coding is used elsewhere in the app.
I also removed names, given the hypothesis that people will recognize avatars, and are one tap away from finding details on that cluster, where names can be found. The same is true for the status icons, those can be seen in the details view as well.
In the circular redesign, I used one less avatar ( 7 instead of 8) but in the linear design I was able to comfortably fit 11 (4 more than the original 7)
The point here is that you ought to be exposed to familiarity, if you're familiar with someone's avatar and you've interacted with them in the past, you're more likely to click on that neighborhood cluster.
One of Saturday's key features is the map view of your network. (so valuable is this map view that we actually had to fix a UX flow which wasn't allowing map discovery, because users wouldn't find it, but once they were shown it, their eyes lit up with joy)
Now that their eyes have lit up from the map view, we must ensure that the map view is all that it could be.
One issue about the map view is that it quickly becomes cluttered. This isn't an inherent thing, it's a UI thing. High density networks can always be visualized in a more simplified manner.
We began with many different versions and explorations, and I took the core of each and tried to simplify it as much as I could.
Let's take a closer look at some of these.
While I hope these designs speak for themselves, allow me to explain some reasoning behind my decisions. In both designs I removed the unnecessary purple stroke, especially since it cognitively collided with users' expectations about color meaning, since color-coding is used elsewhere in the app.
I also removed names, given the hypothesis that people will recognize avatars, and are one tap away from finding details on that cluster, where names can be found. The same is true for the status icons, those can be seen in the details view as well.
In the circular redesign, I used one less avatar ( 7 instead of 8) but in the linear design I was able to comfortably fit 11 (4 more than the original 7)
The point here is that you ought to be exposed to familiarity, if you're familiar with someone's avatar and you've interacted with them in the past, you're more likely to click on that neighborhood cluster.
One of Saturday's key features is the map view of your network. (so valuable is this map view that we actually had to fix a UX flow which wasn't allowing map discovery, because users wouldn't find it, but once they were shown it, their eyes lit up with joy)
Now that their eyes have lit up from the map view, we must ensure that the map view is all that it could be.
One issue about the map view is that it quickly becomes cluttered. This isn't an inherent thing, it's a UI thing. High density networks can always be visualized in a more simplified manner.
We began with many different versions and explorations, and I took the core of each and tried to simplify it as much as I could.
Let's take a closer look at some of these.
While I hope these designs speak for themselves, allow me to explain some reasoning behind my decisions. In both designs I removed the unnecessary purple stroke, especially since it cognitively collided with users' expectations about color meaning, since color-coding is used elsewhere in the app.
I also removed names, given the hypothesis that people will recognize avatars, and are one tap away from finding details on that cluster, where names can be found. The same is true for the status icons, those can be seen in the details view as well.
In the circular redesign, I used one less avatar ( 7 instead of 8) but in the linear design I was able to comfortably fit 11 (4 more than the original 7)
The point here is that you ought to be exposed to familiarity, if you're familiar with someone's avatar and you've interacted with them in the past, you're more likely to click on that neighborhood cluster.
More articles about
Saturday
More articles in
Work Experience
