Where did you get agent’s userpic from? :)
Don't be afraid to "think outside the database" — your UI doesn't need to map one-to-one with your data's fields and values.
Here are a few ideas you can use to present "field: value" data in a more interesting way:pic.twitter.com/NoL3wMtjLV
-
-
-
I mean in the universe of your example :) Agent’s photo doesn’t exist on the left. Other than that awesome example, and pretty close to the real world high-end thing.
-
LOL oops. Adding the agents photo allows users to see at a glance that there is user information there - sort of distinguishing it from the other values unlike the left example.
-
For sure. It’s just a bit more complicated under the hood than it looks on the surface. But yes, it’s the right way to go. :)
会話の終了
新しい会話 -
-
-
The font looks really nice. Would you mind telling me the font?
-
Proxima Nova
会話の終了
新しい会話 -
-
-
You’ve chosen the wrong industry to use for your example. Better to choose something not so arcane. Why not redesign an ebay entry?
-
No matter what I choose, people will find something wrong with it
It's best not to over think it for these examples 
-
Perhaps. I do think some industries and disciplines offer use cases that aren’t so very specific. In any case, your point was well illustrated. Many times though, non-designers only see the design, and not the use case, so … more context is always useful.
会話の終了
新しい会話 -
-
-
Steve, you gotta write a book that contains all these design nuggets. Great work as always.
-
Have one in the works
-
-
新しい会話 -
-
-
@pedro_brown olha que legal... -
ツイートがありません
-
Manda o link para mim... acho bem legal para passar para a galera
会話の終了
新しい会話 -
読み込みに時間がかかっているようです。
Twitterの処理能力の限界を超えているか、一時的な不具合が発生しています。やりなおすか、Twitterステータスで詳細をご確認ください。