Skip to main content

Two Hex and a User

I wanted to post two related hex graphs that give us some good mind food to munch on while we work. The first is more general and tells us seven points of User Experience Design. Take a step back and ask yourself:
  • Useful - Is the software even useful?
  • Usable - What it does is useful, but is it usable?
  • Findable - Can the user find what they need to use?
  • Accessible - Can all the users access it?
  • Desirable - Do the users want your 1 software?
  • Valuable - Is your software valuable enough for the user to retain?
  • Credible - Does the software look fake or are you trusted?

Up second, adapted from the original for social software purposes. We're beginning to see more and more social software, and the seven elements given here fit nicely into all the services I use.
  • Twitter - Presence and sharing (of presence) and conversations (about presence).
  • Blogger - Conversations, reputation (comment count), sharing (ideas), groups and relationships (informal; by linking).
  • MySpace - I hate MySpace, but I use it anyway. Relationships and groups are obviously the focus.
I take this in and consider how we break up these elements into different services, and the focus of each service on one or a few elements benefits us. Twitter does great at what it does, etc. But the separation also harms us. The little widgets we can put on different places to connect the services together only go so far. I have too many feeds, but obviously I can't send all my "tweets" through this feed, as is. So we're getting good at breaking things up, but I'm really waiting for how we'll bring it all back together.



1: Two separate emphasis given.


Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operat...

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally! I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you don't know a lot about software development, and probably don't even know a lot about computers in general. Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year: Python needs LÖVE . LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build ...

My Software Job Transition Strategies?

I’ve been spending a good deal of the last two days preparing mentally for starting a whole new challenge as a developer. New things aren’t new to me, but this is different and big enough really call for some Deep Thoughts ™. For one thing, I’ve made a big move from the world of Python web development to totally other Python work and while web development has never been the only thing I do, it has been the only work that paid the bills. That transition isn’t one that bothers me or daunts me, though. Instead, I’m thinking about transitioning to the scope of the work I’m getting into. For a long time, I juggled multiple clients and client projects every day, so no single project usually took up most of my time. Every developer juggles time through the day, but exactly how that works in each company and on each project varies a lot. I was looking for a place that I could really focus in a way that I haven’t for a long time. I think I found that, but now I have to deal with the consequen...