Might seem like the implementation deadline is not a long way away now for us to be rethinking things at the ground level of wire-frames and final features for inclusion, but I think this is precisely the point where we shouldn’t be relying on our old vision of what Lemontree should be and using the experience and discussions of the concept so far to inform an implementation that is inline with the first batch of early adopters and users expectations of the system. 

So to this end, Sam (now a married man!) and myself, independently did some wireframes for the key pages and functions which we then checked and discussed together! One of the benefits of being in a small agile team is stuff gets decided on quickly, and no one works independently for weeks at a time without sharing things. I especially think things have a propensity to go fubar when the creatives and tech’s don’t spec things together.  At RITH we’ve never made that distinction of coder/tech vs creative, they are one and the same. 

Consequently, through this process we were able to distil and discuss the functions of lemontree and its shiny new interface in the context of what’s essential and what can come later. 

So our new interface directions informed by our wire-framing action strip away unnecessary fluff where possible. They focus on the tasks users will perform. Simple modal windows will allow you to interact on items in the general activity view. There is a larger emphasis on showing personal progress.

We look forward to sharing sneak peeks of the final production wireframes very soon, but my word, they’re very different from the stuff we Presented at Mashed Liverpool.