Build 1: Think Different.
Well, we always said that we would never 'port' Trillian to OS X. And now we're excited to announce that we haven't! Instead, after many support/feature-request tickets asking for an OS X port... we wrote a new Trillian UI from scratch.
Context & Ripple Effects
Cerulean Studios spent years telling users it would never bring Trillian to OS X, and the March 2007 reveal of Astra as a Flash application with Apollo-like functionality — including a web-based client — looked like the answer was 'wait for the browser.' The October announcement reframes that stance: rather than porting the Windows codebase, the team wrote an entirely new Mac UI from scratch, responding to accumulated feature-request tickets.
The pickup is notable for where it landed: a campus paper noting quadrupling on-campus Mac usage signals the audience shift Cerulean is chasing — students and Mac households adopting multi-protocol chat, a market the Windows-only Trillian had ceded.
First-order effects
- Mac users who filed the OS X feature requests get a purpose-built Trillian interface instead of a thin cross-platform port, and Cerulean gains a second native client alongside its Windows base.
- The 'never port' promise becomes a positioning asset: Cerulean argues a ground-up UI fits OS X conventions better than a translated Windows app would.
Second-order effects
- The rewrite splits Cerulean's engineering across two codebases just as Astra pushes toward a Flash/web client, forcing a choice between per-platform polish and the unified browser-delivered model Astra was built around.
- Established Mac chat clients now face a competitor arriving with a multi-protocol feature set and a fresh UI, pressuring them to match protocol coverage rather than rest on platform familiarity.
Third-order effects
- If the pattern holds, cross-platform messaging tools converge on a hybrid structure — native per-OS shells over shared services or web delivery — rather than single codebases stretched across operating systems.
- Vendors' willingness to abandon 'one codebase everywhere' tracks the growing economic weight of the Mac install base, making dedicated Mac clients table stakes for consumer software brands.
The trend: Consumer messaging software is shifting from porting a single Windows codebase to per-platform rewrites layered over web-delivered services, as the Mac audience grows large enough to justify native investment.