Archive for the ‘design’ Category

Map design in Modern Warfare 2

Friday, January 29th, 2010

It’s no surprise that Modern Warfare 2 has broken records. Notoriety sells after all, but fortunately the game lives up to the hype. For devoted fans the single-player storyline, cause of the controversy, isn’t the appeal – it’s the multiplayer mode that’s kept gamers coming back for more.

What makes MW2’s multiplayer experience so rewarding? The answer is of course that the developers Infinity Ward have designed the game meticulously, in particular the maps on which the action takes place. By deconstructing these maps, we can attempt to understand the underlying gameplay design principles.

The most obvious principle is that Infinity Ward have ensured there is no dominant position on any map. Advantageous positions of course make it easier for you to kill the enemy, and harder for them to kill you. Features of advantageous positions include:

• Elevation. This reduces your exposure, improves visibility and offers a better angle for headshots on the enemy
• Cover. A solid object to hide behind means you can pop up into firing position and quickly drop into safety to reload.
• Limited access. The fewer routes the enemy can approach from, the easier to spot attackers and quickly take aim.

and so on. To make the game fair and therefore enjoyable, game designers must use these features with caution. Omitting them would simply create extremely dull environments, so MW2’s maps make subtle use of these advantageous features, coupling strong positions with serious weaknesses.

This ledge on the Afghan map gives clear long-range lines of sight but is exceptionally vulnerable from the rear. At the far end of the map are reinforced bunkers, from which the screenshot below is taken. Cover and vantage are both good, and the low light leaves the shooter cloaked in darkness, making them hard to spot at distance.

However, since these bunkers are potentially very strong points, the map designer clusters two together, so that each poses a tactical threat to the other. To make these appealing spots even riskier, explosive barrels are placed in a particularly juicy spot, further deterring a player from camping there at least until the barrels have been destroyed.

For the few spots that offer clear tactical advantage without high vulnerability, Infinity Ward has wisely made reaching them a risky proposition. The Highrise map features a second-floor window (below) with excellent angles, low light and few weaknesses; however, it can only be reached by jumping around on dangerously high and sorely exposed crane beams. I’ve had many a profitable game repeatedly picking off beam-runners too stubborn to accept that I wasn’t going to let them reach their beloved camping spot.

Highrise also boasts a very unorthodox but effective position (‘A’ below), which allows a player to surprise anyone emerging from the southern building. Position A is suspended off the building on a platform and therefore hard to notice if you’re focusing on the more obvious threats near the helipad ahead. However, this excellent spot is awkward to reach and treacherous to leave. Your only exit route is to laboriously climb up over the side, leaving the player vulnerable for a few seconds – as such, once your cover is blown at A, you’re pretty much screwed.

By balancing the maps’ positions of strength, MW2 keeps players continually on the move as hiding spots become discovered and teams move to flank their opponents if repelled in a frontal attack. It doesn’t take an expert to see that movement makes for a more exciting game than static trench warfare; indeed, movement impetus and variable pacing is a well-known tactic of game design. By running around, players cover more ground and experience greater ranges of contact, from long range to hand-to-hand. In short, players are pushed into experiencing of much as the game as possible. Map scale also follows this principle. Although the maps are generally larger than MW2’s predecessors there is still ample variety, with both compact and sprawling maps encouraging bloody scrambles, patient stealth and all gameplay tactics in between.

Through prolonged play it becomes apparent that Infinity Ward also designed the multiplayer maps not to punish players for their choice of weapon and style of play.

For those who enjoy a sneaky ambush, the maps offer plenty of safe havens and cover from which to spring. Terminal, set in an airport, offers some novel cover spots including this flower bed.

That said, some levels are better suited to some loadouts and styles of play.

This sort of position is close to ideal for a sniper: sure, it’s open, but the lines of sight are immense. Given this much visibility, even a modest sniper can pick off an unprepared enemy with ease. Short range weapons here are far less useful; however, Modern Warfare 2 offers players multiple ways to use territory to their advantage. For those who don’t like the patient precision required of snipers but want to use this spot effectively, the map designers helpfully place a machine gun nearby.

In the right hands the machine gun can be just as effective as sniping, rewarding those who get their kicks by spraying bullets indiscriminately. For the sake of equality, there’s a gun at the other end too and the long grass can quickly give a well-camouflaged player cover from fire.

This interplay demonstrates that every strategy has a valid counter-strategy. If you’re facing a sniper, the maps give many opportunities to hide. To counter this, snipers can flush out hiding opponents by using thermal sights and heartbeat sensors. To counter that, players can employ perks that make them invisible to these devices. Rock beats scissors beats paper beats rock. And for those who’d like to avoid this long range battle altogether, Wasteland also features an intense and dark section of trenches. Here, I’ve planted a Claymore landmine by one of the trench entrances to trap anyone who comes this way.

These indoor areas also give vital cover from the game’s aerial attacks, earned by successful killstreaks, for example killing five players in a row. At the first warning of an incoming enemy helicopter or Harrier, there’s typically a mad panic to get indoors. Skilled opponents will of course follow, but again the game provides an alternative to the hunt. Brave players can switch to a loadout armed with anti-aircraft weapons and perks and shoot the air support down for the good of the team. Thus good play gets its reward (air support usually brings many more kills) but not to the extent that it leaves the opposition team entirely devoid of options.

Through careful design, and no doubt thousands of hours of playtesting, Modern Warfare 2’s maps reward some surprisingly different approaches: caution and risk, patience and aggression, short range and long range. Admittedly the balance will never be perfect, and Infinity Ward are continually tweaking the game to overcome new glitches and overpowered strategies. But I consider Modern Warfare 2 a great example of thoughtful design achieving some difficult goals, and being clearly rewarded by the sales figures.

Posted in design, games | 4 Comments »

I blame the designer

Tuesday, December 8th, 2009

[In which Cennydd has a downright sense of humour failure over a silly web comic.]

Here’s an excerpt of a comic that recently did the rounds in the web design community.

You know what? I’m tired of this attitude.

Clients From Hell is admittedly pretty funny. Sometimes clients say stupid things; but hey, so do designers. I’ve said lots of them myself. But this sort of thing is different. It’s not an amusingly misguided email. Rather, it epitomises a harmful arrogance and entitlement that pervades the design community. It carries a bitter subtext that clients are idiots with no design skill, and it’s a designer’s duty to disempower them by any means possible.

And I’m tired of it. Of course clients aren’t skilled designers; that’s why they had the foresight to hire us. But you know what? They know business. They’re as passionate, committed and talented as anyone. Many of them put their livelihoods on the line to make the web happen. And let’s be blunt: they also pay our salaries.

If a web design project goes to hell this way, I usually blame the designer. He wasn’t skillful enough to make the situation work. He didn’t provide the force of argument required, couldn’t handle the politics, or couldn’t convince the client of the value of good design. On the rare occasion when the relationship with a client goes entirely rotten, the designer should end the relationship gracefully rather than passive-aggressively working to rule.

Unconvinced? I suggest you read Scott McCloud’s excellent post about criticism and the equally insightful comment from Mike L:

“The most common misconception about criticism is that one has to be on a similar skill level as the creator in order to have a valid opinion. I read stuff from many different artists from many different disciplines who cannot abide ramblings of people that couldn’t compete with them in some way. If said person is not an artist, their opinion doesn’t matter. But isn’t art, all art about communication? And who is the artist generally trying to communicate with? … My #1 critic is someone who cannot draw at all. He tells me things I can’t see because I overthink them as an artist.”

(Oh, and here’s what ‘pop’ means.)

Posted in design, web | 16 Comments »

Statistical significance & other A/B test pitfalls

Monday, November 16th, 2009

Last week I tossed a coin a hundred times. 49 heads. Then I changed into a red t-shirt and tossed the same coin another hundred times. 51 heads. From this, I conclude that wearing a red shirt gives a 4.1% increase in conversion in throwing heads.

A ridiculous experiment (yes, I really did it) with a ridiculous conclusion, yet I sometimes see similarly unreliable analysis in A/B testing.

It’s logical and laudable that designers should seek data in our quest for verifiability and return on investment. But data must be handled with care, and mathematical rigour isn’t a common part of a designer’s repertoire.

Here’s an example from ABTests.com, a worthwhile project that I feel slightly bad to pick on.

The two versions are subtly different:

• Version A: Upload button bold, Convert button bold, Convert button has a right arrow
• Version B: All buttons regular weight, no right arrow on Convert button

Although minor changes can cause major surprises, I wouldn’t expect these small differences to improve the form’s usability. With the caveat that I don’t know the users or product, I’d even speculate that Version B could perform worse since it reduces the priority of the calls to action and removes the signifier of progression.

The designer claims that version B showed a 30.4% conversion improvement in an A/B test. Here’s why this isn’t quite accurate.

The role of chance

Any A/B test is a trial, so called because we’re observing evidence gained by trying something out. I can never truly know that there’s a 50% chance of a coin landing as a head or a tail – I can only run trials and observe the evidence. Similarly, we can never truly know that a design leads to higher conversion – we can only run trials and observe the evidence. If that empirical evidence is strong enough, we conclude that the design is an improvement. If not, we don’t.

To be valid, trials need to be sufficiently large. By tossing my coin 100 or 1000 times I reduce the influence of chance, but even then I’ll still get slightly different results with each trial. Similarly, a design may have 27.5% conversion on Monday, 31.3% on Tuesday and 26.0% on Wednesday. This random variation should always be the first cause considered of any change in observed results.

The null hypothesis

Statisticians use something called a null hypothesis to account for this possibility. The null hypothesis for the A/B test above might be something like this:

The difference in conversion between Version A and Version B is caused by random variation.

It’s then the job of the trial to disprove the null hypothesis. If it does, we can adopt the alternative explanation:

The difference in conversion between Version A and Version B is caused by the design differences between the two.

To determine whether we can reject the null hypothesis, we use certain mathematical equations to calculate the likelihood that the observed variation could be caused by chance. These equations are beyond the scope of this post but include Student’s t test, χ-squared and ANOVA (Wikipedia links given for the eager). Here’s a site that does the calculations for you, assuming a standard A/B conversion test with a clear Yes or No outcome.

Statistical significance

If the arithmetic shows that the likelihood of the result being random is very small (usually below 5%), we reject the null hypothesis. In effect we’re saying “it’s very unlikely that this result is down to chance. Instead, it’s probably caused by the change we introduced” – in which case we say the results are statistically significant. Note that we still can’t guarantee that this is the right interpretation – significance is about proof only beyond reasonable doubt.

Running the calculations on the above data shows that the results aren’t statistically significant: the evidence isn’t strong enough to reject the null hypothesis that the difference in conversion is simply down to luck. The main problem is the small sample size (128 and 108 users respectively), so I would advise the designer, Johann, to repeat the test with more users. Assuming the observed conversions seen didn’t change (a big assumption) a sample size of approximately 200 users per variant should be sufficient for significance. He could then either reject the null hypothesis or the results would remain inconclusive, in which case there’s no evidence the design has made a difference. In Johann’s defence, he recently posted that he takes the point about significance, and I’m looking forward to seeing more conclusive data for this intriguing test.

Percentage confusion

Significance isn’t the only slippery problem A/B tests face. For starters, quoting conversion improvements is always fraught with difficulty. Since conversion is usually measured in percentages (in this example, 31.3% and 40.7%) there are two ways to quote improvements. We can say that conversions increased by:

• 9.4% – the difference between the two
• 30.4% – the amount that 40.7% is bigger than 31.3%*

Any percentage improvement quoted in isolation should be challenged: which of these two calculations has been used? It’s dangerously easy to assume the wrong figure without sufficient context.

The A/B death spiral

A/B tests also suffer from a common quantitative problem, in that they tell us what but not why. I’ve written about this previously in What if the design gods forsake us. It’s wise to back up numerical tests with qualitative evaluation (eg. a guerrilla usability test) so we can make informed decisions if data suggests we need to rethink a design.

Even with backup, sometimes A/B tests are simply the wrong tool for the job. They can provide powerful insight in some cases, but in the wrong place they can be a blind alley or, worse, a weapon of disempowerment. Logical positivism and design don’t mix – not everything we do can be empirically verified – yet some businesses fall back on A/B testing in lieu of genuine design thinking. I call this the “A/B death spiral”, and it plays out something like this:

Designer: Here’s a new design for this screen. You’ll see it has a new navigation style, tweaked colour palette and I’ve moved the main interactions to a tabbed area.

Product owner: Wow, those are pretty big changes for such a high-risk screen. I tell you what: let’s test them individually to see which of these changes works and which doesn’t…

As the proverb suggests, sometimes you can’t jump a twenty foot chasm in two ten foot leaps. Cherry-picking only those design elements that are “proven” by an A/B test can be a route to fragmented, incoherent design. It may earn marginally more money in the short term, but it becomes hard to avoid a descent into poor UX and the long-term harm this causes.

Being faithful to data

Given the potential hazards, I’m concerned about the naïveté with which some designers approach quantitative testing. The world of statistics rewards an honest search for the truth, not dilettantism, and I’d advise any designer moving in statistical circles to pick up some basic stats theory, or at least partner with someone knowledgeable.

A flawed A/B test, be it statistically insignificant, misapplied or misquoted, is nothing more than anecdotal evidence. It’s the same crime as making a website red on the feedback of one user. Yet an impatient designer, seeing the example I quoted above, could quickly jump to a false conclusion: “I should remove arrows from continue buttons: it’s 30.4% better.” Perhaps this designer deserves what he gets. It’s likely he’s only really interested in shortcuts to good UX, and linkbait lists of “Twelve ways to make your site more usable.” Since he understands neither the mathematics nor the context of this trial (timescales, userbase, surrounding task) he will inevitably grab the wrong end of the stick. Nonetheless, he is out there.

Don’t let yourself be that designer.

Photo: snellgrove
* subject to rounding.

Posted in design, statistics, user experience | 25 Comments »

Q&A: getting into user experience

Tuesday, October 13th, 2009

For the past few years I’ve given an annual talk at UCL to students of the HCI with Ergonomics M.Sc. It’s always a pleasure to share my questionable world view with impressionable minds, and I look forward to the sessions in much the same way as one secretly enjoys a visit from a drunken uncle.

In an effort to make this year’s session a little more interactive, I pulled out an old Knowledge Management set piece:

1. Distribute post-its
2. Ask everyone to write one question they wish they knew the answer to (preferably about the topic at hand).
3. Stick the post-its on the walls. (It’s surprising how much people group them, despite your invitation to use any of the three free walls)
4. Ask everyone to read each post-it.
5. If they too want to find out the answer to a question, tell them to mark the post-it with a question mark. If they think they have an answer, mark it with a tick.

It’s not that surprising to find that a room of similarly qualified students share similar concerns. What’s more interesting is that many of them can also help to answer each other’s questions.

The purpose of this exercise is of course to show that networking and collaborating is valuable, and not just a case of awkward conversation and limp handshakes. However, having made this slightly facile point, I realised that most of the posted questions were damn smart and deserved to be shared more broadly. So here are a few that were particularly interesting, and some proposed answers from myself. I’ll throw a few more up later this week.

Please contribute in the comments if you have any opinions, particularly if they differ from my own.

Is the graphic design of a site more important than usability when initially attracting users to the site?
I say yes. Research shows users form an opinion on the credibility of a site within milliseconds of visiting it. To form a valid opinion on usability takes use, which may not happen if those impressions are negative. However, the line between the two is of course blurred, and a site can successfully convey usability through layout, visual design and information hierarchy. There are plenty of other factors that have an impact too: load times, content and proposition spring to mind.

How many hours do you work a week?
Define “work”. I’m paid for 37 hours, and most of that is spent on billable client work. But add in commuting, writing articles and conference talks, mentoring, and reading about my field and it would exceed 60. Yes, I’m aware that’s a little unhealthy. Good thing I enjoy it.

What’s the most useless skill you think we’ll learn from this course?
Probably rifling through academic papers to find an authoritative source that proves or disproves a detailed HCI argument. Truth is, not many people in industry will care. It’s more important to judge the the problem at hand and make the right design decisions based on context. HCI theory can give a strong advantage here, but you’ll need to state your case with something more real: usually how your client will make more money by following your advice.

How much do you get paid?
Not telling. But here are some approximate London figures: £25,000 is fair for a graduate-level position, rising to £35–40,000 with a couple of years of experience. Senior people should be looking at £60,000 and up (seven years and above, probably managerial responsibility). Freelance rates typically range between £275-£400/day.

What are the best design tools in HCI?
Thinking, conversation, sketching, software. In that order.

Can you be a good UX designer and a good programmer at the same time?
You can be good at both, yes. But who wants to be just good? Deep specialists tend to better than jacks-of-all-trades, and only extremely rare superheroes can be world class at both. I do, however, strongly recommend that all designers learn to code to a reasonable standard, and that all developers learn the fundamentals of design. Speaking each other’s language is the easiest way to ensure good designer-developer relationships, and one of the easiest ways to become substantially better at your job in a short time.

Do you need to draw well / be arty to be a user experience designer?
Some drawing talent helps, but sketching well is a skill that can be learned and that comes with practice. Its main value is when communicating with clients – a well-crafted sketch can simply convey more information than a poor one. However, it’s more important to develop a designer’s mindset. As Jason Santa Maria says, “sketchbooks are not about being a good artist, they’re about being a good thinker.”

To finish, two questions I don’t feel fully equipped to answer. How would you answer them?

• What’s the most interesting HCI related job out there?
• How do I get into the user’s head?

Posted in design, user experience | 5 Comments »

The behaviour you design for

Thursday, October 8th, 2009

I’m working on a site that’s grown from no deal to big deal. Earlier design oversights have created user coping strategies so ingrained that I mustn’t disrupt them with my new design work.

Another reminder that you get the behaviour you design for.

Photo: Tim Bradshaw

Posted in design, user experience | 2 Comments »

dConstruct 09 in review

Monday, September 7th, 2009

After you build forty or fifty websites there really isn’t any magic in it.

dConstruct’s comfortable niche as the thinking person’s web conference was quickly disrupted by Adam Greenfield’s early remarks. Decrying web and UX design is a risky strategy in a room made largely of web designers and developers, yet it was a thought entirely consistent with our theme of Designing For Tomorrow. The phrase wrapped topics that have been of recent interest to us Clearlefties: ubicomp, gestural interfaces, networked devices and what lies beyond our familiar digital horizons.

Adam led us into a world where information is omnipresent and persistent, where actions stick to identities and the presentation of self is a largely forgotten luxury. A world where objects become services, shared not owned, implies a post-capitalist swing perhaps alluded to by recent economic events. As a recent and voracious reader of Everyware, I was thrilled by Adam’s talk. I’m sure the imminent podcast will reward careful re-evaluation.

Mike Migurksi provided a practical counterpoint with a case history of Stamen’s information design work, with subsequent colour commentary by Ben Cerveny. Ben’s dense, rapid idea stream was perhaps a step too far after such an analytical opening; although Stamen’s work is undeniably excellent, many felt a gap between the metaphysics and the design output, and some of Ben’s more elaborate statements seemed hard to grasp.

Brian Fling explored the mobile field with characteristic flair and pace. Focusing on the future lives of the post-millenials native to the digital age, Brian proposed that history will judge the mobile (and the iPhone in particular) as the flying car we have been waiting for. We are living through a second industrial revolution, based on the portable, personal power of bringing people closer through technology.

Next up, an elaborate Gaia theory of sci-fi and interaction from Nathan Shedroff and Chris Noessel. In an entertaining presentation, the over-used Minority Report example was only (multi)touched upon once, and Jurassic Park’s ridiculous UNIX scene was rightly used for cheap laughs. Of particular interest was the pair’s evidence that anthropomorphism can exist at non-visual levels (consider R2D2’s bleeps and Amazon 1-click servant), although, like Ben before, some other claims seemed rather hazier.

Robin Hunicke, known for her work on “the Maslow’s Hierarchy game known as The Sims”, unfortunately alienated her audience with a spoiler (albeit well meaning) for a film still on general release, and struggled to recover favour. Her West Coast bubbliness sat awkwardly at odds with her academic subject matter, which was coincidentally recapped by August De Los Reyes. Any Microsoft speaker knows he has an uphill battle to win over a sceptical audience; fortunately August’s self-deprecating humour was an instant hit. We imbue objects with intelligence (slide rules, other technological tools), so why not emotion too? Heartbroken families insist on the repair, not replacement, of their Roombas – can we conjure similarly powerful dynamics in the systems we create? August closed with Office Labs’ concept video, a surprisingly rousing vision that raised hairs on necks across the Dome.

The stage was set for a wonderful denouement from Russell Davies, who produced a performance straight from the traditions of British music hall. Russell predicted that digital buildings will give us “Blade Runner brought to you by the makers of Cillit Bang”, and that as technology matures the only way we will escape cliché is to redomain, appropriating ideas from other fields. Russell provided a marvellous reminder that, despite the intelligent contributions of the day, as an industry we are prone to hubris. We’d be daft to disregard the marvellous infrastructure our media predecessors have created.

At its best, the fifth dConstruct was simply outstanding. In its rare low points, it disappointed. As such, it’s at a crossroads. The trend has certainly been cerebral, and this year’s theme certainly encouraged abstract exploration. Early feedback says our audience is happy with this, and that the differentiation from other conferences is an important part of dConstruct’s appeal. Yet there’s always a danger of vanishing into pretension, and the conference must of course appeal to 700+ attendees.

I’m sure Clearleft won’t be taking any snap decisions. dConstruct has become part of the fabric of our company and hopefully the annual schedule, and, in line with our chosen theme for the year, we’ll be thinking carefully about what happens next. I’d love to hear your thoughts on the day and your preferred direction for dConstruct 2010.

Photos: Matt Biddulph, FriiSpray, Tom Jenkins.

Posted in conferences, design, mobile | 5 Comments »

Sweating the small stuff

Thursday, August 27th, 2009

Outrage. Ikea recently switched corporate typeface, moving from Futura to Verdana across all their marketing, including their printed catalogue and ads.

To typography enthusiasts, this is like Mozart announcing a kazoo concerto. Futura is a type classic, skilfully designed by a master craftsman and demonstrating real artistry. It’s excellent for distinctive identity and brand work – so much so that Ikea had practically made it their own until now.

Verdana was created to act as body text on low resolution computer monitors. And it’s well designed for that purpose, but it doesn’t suit print work or any size above petite. At large sizes it looks plain fugly, with characters that appear juvenile at best. Use of Verdana in this way definitely constitutes bad typography.

The slight is all the greater coming from a company that has, to an extent, brought design into the lives of many people who previously believed it was the domain of turtlenecked pseuds.

Ikea’s reason was ostensibly to ensure consistent use of fonts across web and print platforms, and to ensure global compatibility across all languages. A strange choice, given that Verdana has notable deficiencies in its character set. However, it’s possible that Ikea isn’t as naive as we think. My colleague Paul Lloyd hypothesises that the switch is a deliberate ploy to make the company appear less expensive. It’s an old strategy: cheapen the aesthetic and the perception of price goes down. Plausible, at least.

By all means we can point, laugh and lament the lack of design skill at the company. However, some of the outrage has been ridiculous, particularly since we can never truly know the reasons behind the choice. Hell, there’s even a petition to reverse the change.

I believe that if companies make bad design choices that’s their prerogative. If I worked for Ikea, I would have fought tooth and nail to dissuade them from this choice – but no, I won’t sign a petition. Let them eat cake, and if design is as important as we say it is, the market will prove their mistake.

Herein lies my bemusement at the design community’s reaction. Behind the indignation, does any of us really believe that this typographic gaffe will affect Ikea’s sales? Is it really as egregious an error as we make out? Or are we merely acting out the stereotype designers fight so hard to shake off: the aforementioned turtlenecked pseud complaining that their soup isn’t hot enough?

Typography matters. Used well, it can elevate communication in astonishing ways. But, as Aegir points out, there are bigger design challenges facing Ikea and indeed the global manufacturing industry than choice of corporate typeface.

Design is about sweating the big stuff; hopefully even changing the world. Often that involves the small stuff too, but focus solely on the trivia and it’s hard to avoid becoming trivial yourself.

Posted in design, typography | 1 Comment »

Blank canvas

Wednesday, July 8th, 2009

We’ve been busy. Not only have we taken on ‘leftie number nine, but we’ve also moved into larger studio. Obviously this means higher overheads, which takes careful thought in the middle of a recession, but it also means (amongst other things) we finally have wall space.

A blank wall is an invitation to a designer. As soon as the paint dries, I’m sure we’ll drown in post it notes and poorly-taped flipchart sheets. Heated debates will be held at the sharp end of a marker pen. The war room of my most recent project featured 20′ of whiteboard, which became a great way to sketch and walk through design concepts before stepping into prototyping. Drawing on the walls has thus become a minor fetish. It’s highly visible, and thus brilliantly suited to critique. It keeps you moving and alert, rather than immobile in your chair. And it also has the marvellous appeal of finally being able to do something you never could as a kid.

I hope to to share some of our scribblings in due course.

Posted in creativity, design | No Comments »

• « Older Entries