This is the second in a series of examinations of social content sites. Previous: flickr.

The second site I want to look at is Artsonia. Artsonia has a very specific audience: elementary art teachers. Their business model is pretty simple: parents like to exhibit their children’s art. However, parents typically don’t work with their children to help them produce that art, so targeting the parents is the wrong way to go. Instead, Artsonia has targeted teachers, and encourages them to upload their students’ artworks. Then, parents can come and purchase children’s artwork on mousepads, coffee mugs, t-shirts… the list goes on and on.

In return for the photographing/scanning of student work, and uploading those images to the site, Artsonia pays a portion of their proceeds to the teacher’s school for the teacher to use on anything they desire. No doubt this works out well from a tax perspective. (Schools are typically 501(c)(3) organizations in the USA, meaning that all of Artsonia’s “payments” to the schools probably look like tax-deductable donations… very smart.) From the teacher’s perspective, it gives them a budget they can spend on materials or, really, anything they want—as usually, art teachers are severely constrained in what they can purchase, and have to spend a significant part of each day worrying that their program is going to be cut to support the construction of, say, a new set of bleachers for the football field.

(I have opinions on this matter.)

So, lets look at Artsonia.

Artsonia: Not for casual browsers

070530-artsonia-main01
Artsonia homepage. Click to zoom.

The first page of the Artsonia site is dominated by a large image. This image does not aid the user in any way, and does not get them (immediately) into the content of the site. This is a massive waste of space (35% of the front-page real-estate), and does nothing to help the user learn the site in the best way possible: browsing.

Schematics-Front-Page

In fact, a minimal amount of space on the front page of Artsonia is given over to browsing. If we count the three entry points for “Parents & Family”, “Teachers,” and “Just Visiting…” as “browsing”, that represents 10% of the user’s experience. We might also consider the sales advert on the right, which I assume is typically customized depending on the time of year (another 8% of the screen). In truth, only one of these clickable options (”Just visiting…”) actually lets you jump into browsing the site. All of the other options present the user with large amounts of documentation, forms, and choices to make.

070530-artsonia-parents02
The page parents and family are presented with
when navigating from the main page.
Documentation heavy and navigation/browsing-poor.

070530-artsonia-visitors04
The “museum” homepage. Also browse-poor.

A critical difference between Artsonia and Flickr is that the Artsonia was created, first-and-foremost, as a profit-making venture. While it is true that it is a social-content site, and it is intended for teachers and families to use in publishing (and then printing/buying) their children’s artwork… it was not created strictly for the specialized sharing/publishing of content. In this regard, we might use the absence of an open API for uploading/managing content on the site as a measure, along with the lack of a browsing focus and the strong commercial bent of the site.

Summary

Considering what we’re trying to do with MyGame (support a growing community of users, provide a place to showcase content, provide infrastructure for students/teachers and other groups with specific (pedagogic) goals), Artsonia does not provide a great deal of insight. In our case, if someone is a Greenfoot user, we’ll want them to be able to get into finding interesting scenarios quickly and (possibly) downloading the source for those scenarios. If they aren’t a user, we’ll want them to be able to easily see what others have done, and perhaps play/interact with those scenarios. In either case, we aren’t currently planning on merchandizing anything submitted to the site… although, being able to order a t-shirt with the splash-screen of your scenario could be cool… ;)

Today, I got up at 3AM, caught a cab to Stanstead airport, flew to Bratislava, took a bus to Vienna, and then spent the day walking around the city. Admittedly, I took a 1-hour nap in the park… but it was such a beautiful day, one just made for napping in the sun. It was glorious.

We had a wonderful dinner of salad, bread, and cheese with an excellent friend and former housemate, enjoyed a few pints of Budvar, and we’re about to head to bed. But… while relaxing in the park this afternoon, I put together the most recent edition of Greenfoot Adventures.

Why? Because I knew that some things Simply Must Be Done.

So, here it is: Day Two of Greenfoot Adventures: Das Toys.

Page 1-4

You can download the most recent version here, or catch all three:

  1. Greenfoot Adventures Day Zero: In Search of the Perfect Scenario (17MB PDF)
  2. Greenfoot Adventures Day One: The Search Continues (13MB PDF)
  3. Greenfoot Adventures Day Two: Das Toys (31MB PDF)

We have two scenarios up on the MyGame site that I’d thought I’d point to.

First, we have Herder by lazyeye.

Lazyeye-Herder

This seems to be a cross between Poul’s boids example and … an experiment in sheep diffusion. Ewe decide. (Baad, baad pun.)

Second is Tetris, by Dibos:

Dibos-Tetris

What’s this?! It isn’t there! I don’t know what the problem is, but there doesn’t seem to be an applet there. Hm. However, it’s already received on 5-star rating… from the author! The cheek!

Well, at least we know that the author thinks it’s cool. I hope that gets worked out, so that I can play Greenfoot Tetris from now on, and claim that I’m “product testing.”

I’ll try and keep up on posts over the next few days, but I’m off to Vienna to see a friend and the city, having never been. But I certainly want to keep up on Greenfoot Adventures, so hopefully Poul will keep sending me pictures.

We think we’d like to build a social content (SoCo) site for Greenfoot. Social content sites (digg, flickr, YouTube, Artsonia, and others) allow users from all over the world to share (and, in some cases, remix) their creations with other users all over the world. MyGame is a first cut at such a site for Greenfoot, and it is powering the Greenfoot competition at JavaOne. However, MyGame (as it stands) most likely does not meet the needs of Greenfoot’s current (and future) users.

So what makes a SoCo site? Instead of writing up my notes offline, I decided I might as well put them here. The local group can see the notes, and there’s room for people Not Geographically Co-located to comment. Today, I want to take a cursory look at flickr, a widely used photo sharing site recently purchased by Yahoo!. My first look at these sites will largely have to do with the interface; I’ll circle back around later to look at other aspects of the site (tagging, search, etc.) later.

SoCo Site: flickr

I want to work my way through a few pages of the flickr site. I’m partially interested in the kinds of functionality that the pages expose, as well as how that functionality is presented to the user. I would like to say, up front, that I am not, by trade, a UI designer. I’m just a guy who got his PhD studying novice programmers who happens to write virtual machines for concurrent programming languages for fun. So, feedback appreciated.

The flickr homepage

Flickr-Frontpage
The flickr homepage.

The flickr homepage is almost entirely given over to a random photograph and various ways for the inexperienced user to browse content on the site. After the random photo, the user’s eye is immediately drawn to the opportunity to tour the site. The bottom half of the page is given over to interfaces for searching and browsing the content on the site. Even the random quote placed in the middle of the page serves as browsing interface; keywords within the quote are actually links into flickr’s tag browser. Experienced users who find their way to this page don’t need any of these features, and therefore, the login option for returning users takes up a tiny percentage of the page.

Flickr-Frontpage-Schematic
Schematic view of the flickr homepage.

The flickr launch page

The flickr homepage is very different from the page that a logged-in user interacts with. This ‘launchpad’ is far less focused on providing access to the content of the site, but, oddly enough, dedicates a remarkably small amount of screen real estate to supporting the user in manipulating content.

Flickr-Login
A user’s ‘homepage’ in flickr.

I’m surprised by how small the “control surfaces” are on this page. A significant amount of space is given over to “Upload Photos” (4% of the screen), which makes sense, as that is probably the most common action a user might undertake. Recent photos posted by myself and others take up serious real estate (30%), as do news and alerts (another 30% or more). There is a lot of non-functional space given over to my name and icon (the middle of the page, 20%). The most exciting part of this part of the screen—a full fifth of the page!—is that it sometimes says “Hello” or “Good day” to me in languages other than English. Unfortunately, the menu (top), which has over 30 options (in the form of small-target Javascript drop-down arrows) takes up only 15% of the screen… less, perhaps, as I’m being generous in my measurements.

Flickr-Login-Schematic
The flickr start page for logged in users.

The contrast between these two pages is that the homepage is for visitors that do not know why they are there, and need guidance to get into the site and (hopefully) become paying members. Site members, however, are assumed to have “bought in,” and can handle a more complex interface. That said, I still think that more space should be given over to letting the user easily do the top three or four most common tasks, as opposed to providing (what I consider to be) a relatively painful set of drop-down Javascript menus.

What I like

I like flickr’s main page. It is simple, and gets a visitor into the content quickly through several different mechanisms. Fully 60% of the first page a new (potential) flickr user sees is given over to one or more forms of browsing the content on the site. This strikes me as an absolutely critical design decision if you are creating a SoCo site: new users are best attracted by the content that others created.

What I don’t like

I don’t like the fact that, as a logged-in user, I have so little space given over to interacting with the site. Only 20% of a logged-in user’s launch page is given over to controls; one control is given 4% of the screen real-estate, while another 30+ controls are hidden in a drop-down menu. As an inexperienced user, I don’t even know what those options are, and worse, have no idea what they are unless I go exploring. Given that Greenfoot has… 17 menu options total (where the “Help” menu has the most options of any of the menus), I can’t imagine creating an associated SoCo site that is harder to use than Greenfoot itself. That strikes me as wrong.

I think too much space is given over to news (30%) and the browsing of content (30%) from this interface. Then again, perhaps the authors of flickr have discovered that it is important to use this much space to communicate with their users, and perhaps those thumbnail browsers are useful. I cannot say. But, for me, the biggest problem I see with the flickr site, once I’m logged in, is the lack of actionable space.

Summary

flickr represents a mature web app, with many users and many third-party clients that leverage it’s API. The web interface gets hit heavily by thousands upon thousands of users, and will warrant some revisiting. I’m particularly interested in the content manipulation options that exist in the menus (once logged in), as well as the mechanisms by which search through the content and tags is handled. This last point, I think, is important, as it represents a kind of website usability that I want to dwell on for a moment.

This URL is clean and simple:

http://www.flickr.com/photos/tags/wombat/

It actually represents a search into the flickr database: it is a query over the tag ‘wombat’. The user does not see it as a query, it can be easily shared, and is easily mailed/etc. without it getting mangled due to a bunch of ugly in the query string. It is, in short, a human-readable, human-writable query.

A simple and easy-to-use tagging system seems to be at the heart of many successful SoCo sites. Letting users develop their own “folksonomy” is not only important, but perhaps one of the most important things that can emerge from such sites. I’ll look at tagging in SoCo sites in a single post that considers how it is done across a range of web apps; no doubt, there’s a good pool of scholarly and usability work in this space as well.

I thought I’d take a second to see what Technorati had to say about Greenfoot. Surely, the entire world must be talking about Greenfoot by now, right?

Well, not exactly.

However, I did find some cool things.

Masood Mortazavi was hanging out in the .org zone, and saw the Greenfoot team. Now, I didn’t know there was a .org zone (Poul just sends pictures, not, you know, information), so that’s kinda cool. I had a chance to hang out with some of the Derby and OpenJDK peeps at SIGCSE recently—good projects if you’re keen on JavaDB and the open-sourcing of the Java stack.

Je ne parle pas beaucoup de Francais, mais Greenfoot, c’est internationale! (Really, I had three years of French over a decade ago. That’s about as good as it gets.)

And I’m guessing this is a University of Kent student; they’ve apparently revamped their weblog, and have been tackling the creation of a microworld in Greenfoot. All I can say is that I hope they keep at it, and if they have any questions, to hit us via email (or some other medium).

Greenfoot recently was mentioned on ZeroNave.it. My Italian is worse than my French, so I won’t be writing anything in that language. I do like the comment “Greenfoot (piede verde?) !”, however. Yes, yes, it is called “foot green.”

Interesting. I’d call it navel-gazing, but I don’t think feet have navels… not even green ones.

In the first episode of Greenfoot Adventures, we left our colleagues lost in San Francisco, trying to find the ultimate Greenfoot Scenario. They rode all over this hilly city, and found nothing more than a big bridge. Silly Greenfooters! There are no Golden Gate Bridges in Greenfoot Scenarios!

So, I present to you, the second edition of Greenfoot Adventures, where the team is presented with a 2007 Duke’s Choice Award at JavaOne, yet are still unsuccessful in finding the Ultimate Scenario. In part, this is because no scenarios have (yet) been submitted to the MyGame site, and as a result, noone is in danger of winning the competition.

So, I present to you Greenfoot Adventures: The Search Continues. In case you missed the first edition, they’re all linked in here.

  1. Greenfoot Adventures Day Zero: In Search of the Perfect Scenario (17MB PDF)
  2. Greenfoot Adventures Day One: The Search Continues (13MB PDF)

Page 1-1

2007_awards

Greenfoot was selected as one of the 2007 Duke’s Choice award winners, which was presented on May 8th at JavaOne. This is a very, very big deal. I’ve already seen some companies doing big, nifty press releases; those press releases are boring compared to what I do, so you should be glad you’re reading this instead of those press releases.

What is Greenfoot, and how did it win this award? Ah! Well, Greenfoot is a very exciting microworld where you can program all kinds of exciting environments in Java, and watch your creations interact in ways that you (possibly) never expected. You can check out the Greenfoot site for tutorials, examples, screenshots and the like.

So, in the next post, I’ll continue my series of press releases surrounding this very exciting event: Greenfoot Adventures! That’s right, in celebration of this award, I’ve developed an entire web comic chronicling the adventures of Poul, Michael, Cecilia, Ian, and Bruce in San Francisco, as they search for the ultimate Greenfoot Scenario!

Yeah, it’s definitely that cool.

For posterior’s sake, I’ve kept the old version of my first edition of the web comic. I want to be clear—I really don’t think my friends should go play in the street. Playing in the street is dangerous. When I was younger, I played Frogger, and I know what happens when you run around on a busy highway. And as Michael, Poul, Cecilia, and Bruce are all traveling as internationals, crossing the street can be very dangerous. Had they been caught BlueJ-walking, or looked the wrong way while crossing the street… well, lets just say that Davin and I would have rushed over to San Francisco to make sure they were OK. Because we care. About being in San Francisco. In spring.

This new edition of the web comic is great awesome. I mean, I now have a story line—an arc, if you will—that I can use to motivate all of my web comics. Obviously, the group must be… on a quest for the perfect scenario! You might wonder how I missed such an obvious play last night while watching the snooker: it baffles me as well.

So, I’ll leave the previous comic for you to enjoy, but this new one is really supersuper.

Page 1-3

Grab it here.

Poul was kind enough (*cough*) to send some pictures of their first day in San Francisco. Now, JavaOne hasn’t started just yet, so they’re apparently having a rough time of it around the Bay area.

Poul only had this to report:

Don’t worry too much that you are not here. San Francisco really sucks -
Canterbury is a lot more interesting. Nothing to do here and it is
almost freezing outside. :-P

Poul lies like a sick dog.

Given that he had little else to say, I was obligated to figure out what was going on from the pictures he sent and fill in the gaps given my knowledge of Poul, Cecilia, Michael, and Bruce. Given that I know them all as well as I know my towel, I’ve put together (just for you!) the first edition of the most amazing and excellent web comic… Greenfoot Adventures!

Page 1-2

You can download the first edition (PDF, 17MB) of this limited run, truly remarkable web comic, and then proceed to Share and Enjoy(tm). Fortunately, it’s only 11 pages of Vogon-quality comic!

Yes, that’s right—the BlueJ/Greenfoot team is off to JavaOne, and who do they leave behind? Who I ask! That’s right. They leave their blogger and star developer, Davin. (Davin, being in Australia, doesn’t actually count, but I feel obligated to mention him here anyway.) Now, what they apparently don’t know is that the blog is mightier than the sword, and given that Davin maintains greenfoot.org, and I write the blog, they’ve left the two most dangerous people in the world behind—bitter, lonely, and ready to do something about it.

While Bruce, Ceclia, Ian, Michael, and Poul are off having fun in San Francisco, Davin and I (get this) will be reporting to you on JavaOne. I want you to pay attention here, because this is important: the two guys left in Canterbury, England, and MmumblemumbleSumbuleumble, Australia will be reporting to you on the exciting things taking place at JavaOne. Honest. Really.

In fact, look at this cheeky email Michael sent the night before they all took off for beautiful San Francisco:

Matt,

Would you like to write a running commentary of the JavaOne
competition (a short post or two a day) on walkabout while that’s
going on? If you did, we would advertise it at the conference…

(You would mainly look at the submissions on mygame, but if anything
interesting happens in the “Real World”, we might let you know…)

mik

If I may borrow from Marvin: “Here I am, the brain the size of a planet, and they ask me to blog about JavaOne.”

So watch this space. Davin and I have some things to say!

Next Page »