Designing a translation interface

The process of translation & localisation tends to be messy, often involving Excel spreadsheets, many rounds of email, and developers or managers copy-pasting chunks of language that they can’t read into databases.

One of the features of the CMS I’m working on is the ability to easily produce localised versions of a site or application making the process of translation more predictable.

An interface was needed.

From what we learned, in order to produce effective translation context is everything – if you can see how a page fits together, it’s easier to give meaning to the individual elements. Another reason why Excel sheets are not very effective.

To keep the task of Translation as clean as possible I wanted to get all the extraneous CMS controls as far in the background as I could.

Here’s my initial (and as it turns out naive) prototype.


Mockup: Newsweek with inline translation


Designing a translation interface

Pairing apps – two player games

I’m in the process of designing a ‘couples’ app at the moment – it’s called GoodBoy.

It’s a two player game, that works like a private chat channel with lots of fun enhancements.

Apart from the compelling gameplay the biggest interaction challenge seems to be pairing the two phones together. At the moment it’s a very long winded process with many possible outcomes.

Some of the things under consideration are:

  • How can we authenticate an invitation?
  • How do we receive an invitation before the app is installed? (SMS seems like a good choice)
  • How do we accept an invitation?
  • How does the game know we have an invitation waiting?
  • Can you start playing before your invitation is sent/accepted – is there a solo mode?
  • Can invitations be accepted from other people mid-game?

There are only a few apps in the couples app space so looking for best practice examples isn’t easy.

The invitation form seems relatively straightforward at the moment:


Pairing apps – two player games