With the release of the alpha of Trillian Astra for Mac, there are lots of comments and controversies stirred up by the new design of the software. In the following 3-part series, I will attempt to explain the reasoning behind the design and open myself to critiques and comments.
iTunes: a straight port
Apple’s Mac OS X is the Mecca of desktop user interface design. Despite how many times Apple itself breaks its own interface guidelines with iTunes, Time Machine or Dashboard, such new experiences are justified by good logic and craftsmanship, no matter how they deviate from the norm.
As we move along in the future of software, I envision that the distinction between downloaded desktop software and web software. And this is how the design challenge began.
Designing between Platforms
Microsoft Office: a culture-specific port
We first saw software from OS X coming to Windows (e.g. iTunes, QuickTime), and software from Windows coming to OS X (e.g. Office), when their user bases were distinct, i.e. Mac users always stay in Mac, Windows users always stay in Windows. That was relatively easy. Windows and Mac OS X could be a metaphor of two different nations with different culture. One could simply translate the software directly into another and call it done, or one could also design the software to be culture-specific. The latter means that, Office for Windows have a Windows layout and Windows features, while Office for Mac have a Mac layout and Mac features.
Adobe Photoshop: an in-between port
And then we also had software that are designed to work on both platforms (e.g. Photoshop). Back in the days, they were mostly professional software. Such software exists as its own entity; their users will be unhappy to relearn the software if they switch OS. Therefore, it is always interesting to look at Adobe and Macromedia products, in the way how they designed the UI to make users of both OS-es happy. In my observation, Adobe is getting more aggressive these days introducing its own UI elements, while still respecting the fonts and metrics of the OS.
And now we have the third type of software: Software that is always connected, across operating systems and across platforms of desktop, web and device.
So here’s the challenge: Design a unified interface across all OS platforms, desktop and web, while retaining an identity. This is Trillian Astra.
Admittedly, Trillian Astra is one of the few first software out there that attempts such triumvirate. Here at Trillian, a lot of users use IM across OS-es and devices. For example, one would have a Mac at home, while a Windows PC in the office, and also an iPhone on the run at the same time. There would also be users who have a Windows PC at home, and always on the run in libraries and Internet cafes. The user does not stay at the same platform all the time in these cases, as we encourage them to use Trillian across the board. In this point of view, coherence is not simply between the software and the operating system, but also between the software in these different incarnations.
I would like to start a conversation with any UX designers out there, and I hope we will have a better reach to do this with the release of the Mac edition. Please feel free to drop your comments in.
Next up, I will talk about how Trillian is designed to be coherent with Mac OS X.
Proceed to Part 2…



I think another important element to keep in mind is not just the visual look-and-feel, but how things behave. And this is I think the biggest pitfall of porting a program among multiple platforms.
For instance, Thunderbird on Mac OS X still doesn’t talk to the system address book and system spellchecker (without third-party plugins, anyway), being off in Mozilla-land. This is why even though Thunderbird is a great mail app, you end up with something that feels ‘out of place’ on OS X, even when they have modified the UI to fit in.
People expect that the address book is just the address book and should be available in mail-related programs, etc.