Remembering Mark Coleran

August 2nd, 2024

It’s been seven weeks since Mark Coleran has passed away. That morning I opened my Facebook stream to check in on friends’ vacation updates and occasional neighborhood rants, only to be greeted with the short notice that Mark is gone. At the time, Mark was living in Sweden, traveling the country, taking photos of anything and everything that caught his inquisitive eye, and posting daily updates on Facebook and Instagram. He was also working on something secret for Volvo, but he never really talked about it. And now we’ll likely never know.

Back in 2011 when I started doing interviews on computer interfaces in movies, I did not know his name. And yet, almost every single interview I’ve done in those early years mentioned his name, either as a mentor, or as a source of inspiration. From 1999 until 2006 he worked on every single blockbuster action movie that you can think of, from Bourne to Mission Impossible, from Tomb Raider to The Island, and many more. He was the first to admit that he did not start this field, but he undoubtedly revolutionized its ascendance into what it is today.

As he moved on into the world of “real” design, first with Gridiron Software and his work on the unfortunately short-lived Flow, and then later freelancing on a variety of projects, and as his name kept on popping up in the interviews that I was doing, I finally reached out to him in 2016 to have an interview about his film work, and his transition to be outside of that industry. As fate would have it, we did not move on to fully review and publish it that time.

But I remained hopeful that we would have another chance, and it eventually happened in 2021. One of the best things about Mark is how unreservedly honest he was, even when he knew that it landed him in a good deal of trouble with some of the people he worked with. And the other brilliant thing about him was his pragmatism. Summing up more than two decades of being a professional designer at that point, Mark got straight to the point:

We care about what we do, and it’s easy for us to become obsessively caring about something. We think we own it.

People will hate me for this, but for me it boils down to this. If you’re doing art, you’re doing it for yourself. If you’re doing design, you’re doing it for somebody else. You don’t get to make those decisions. We really do care about this, but you do have to have a very high level of pragmatism, almost down to a cynical level of detaching yourself from it. Somebody’s paying me to do this job, so let’s get the job done. But it’s not mine.

You don’t have to be aloof. I care about what I do. I want it to be good, and I want it to work well and to do what it was meant to do. But I focus more on my craft now than on the individual objects themselves. Did I do this well? Have I learned something new by doing this? Did I save some time by trying a different approach? It’s the craft that I now get the pleasure out of, and not necessarily the end result. It becomes a hard lesson. When I left the work, it was because I did actually care about that. I was getting so annoyed by what I was doing and how it was looking like on screen. We do this work, and then it’s there for a couple of seconds on screen. It doesn’t feel like it’s worth it.

That’s why I went into the world of real software. In that world, every decision you make affects how that thing works. It affects the experience somebody has. It’s continuous as well, as you refine it, iterate on it, and build upon it. And my experience in real software is the same. Nobody cares. Nobody sees what you’ve done. They all complain about the stuff you did badly, but in the end it doesn’t really matter. It’s out there, and it’s being used, and you don’t own it. A hundred other people had their fingers on there, and you did your part, and it’s exactly the same as movies.

I’ve started my professional career as a software engineer back in 1999, right around the same time as Mark did. These days, I find myself in much the same place as Mark when I think about my work. I am given certain tasks to deliver, each task determined by the needs of the product. It is my job to deliver a high quality output that does what it’s supposed to, in service of the product.

I spend most of my time thinking. Contrary to how our field is portrayed in the movies, we don’t furiously type away at the keyboard for hours. We don’t have a grid of high resolution monitors, with multiple dashboard, text editors, terminals and other windows racing against each other with ever more information to be parsed. I think deeply about the task at hand. I spend my time constructing an abstract representation of it in my mind. I hold it, and I look at it from different angles. I think about how the final thing should look like. Not for myself, but for others that will be using it.

I care deeply about delivering a thing that works well. At this point in my career I can say that I know what I’m doing, and that I do it well. We are paid well for it, but it’s not just the money. Being able to hold a complex problem in your mind, to look at it from different angles, to consider possible solutions, and to choose the most promising initial approach is its own reward. Being able to put those ideas into hard code, and to see that code running and doing what you intended it to is its own reward. Taking pride in being good at what you do (removing the mandatory sense of self modesty from it for a second, if you don’t mind) is its own reward. Without all of these, you spend 50 hours a week, 50 weeks a year, a 45 year career – literally half a lifetime – following somebody’s orders to maximize the mythical shareholder revenue. It is absolutely soul crushing.

And at the same time, I used to have this undertone of something that was missing. It’s a bit selfish, but then, we are always at the center of our own world, from the moment we wake up until the moment we drift away into the nightly sleep. Validation and approval. To have others congratulate you on the job well done. To need it to come from the outside. To question yourself and your ideas, your ability to do this well, and the quality of your work – when all you see from others is indifference. I’ve lived with that for years, until about three years ago, when I talked with Mark. My last question for him was on what piece of advice he’d give to his own younger self, and this is what he said:

I would say that nobody else cares about the things that you care about. You like what you do, you love what you do, it’s important to you, but it may not be important to anybody else.

That difference can be the source of a lot of frustration for a lot of designers and creative people. We’re not necessarily doing what we think we’re doing. We’re always doing something for somebody else. And half the time, we’re just going to be doing the thing that they want and not having any input at all. Understand that you’re not as important as you think you are.

It’s a strange thing for me, because there’s this myth that has grown up around me [laughs]. I’m this mythical FUI beast that did that work, but I’m just a person. I’m just a designer. I was working with somebody recently, and they said that they though I’d be quicker and get this stuff done in a day. But it was two weeks worth of work. So the idea of who you are and what you are can be different to other people as well. Be clear about what you’re doing, who you are, and why you’re doing it.

Understand it’s all just a job. Everybody wants to treat design and creative work like it’s something special, and it is to you. But it is just a job as well. Do not forget that you are just doing something as a job. I’ve worked way too hard and way too long on stuff that nobody cares about it, because I forgot that. It didn’t matter if I done 8 hours a day or 16, but because I did 16, other things suffered. So don’t forget it’s just a job, and you’re not as important as you ever think you are. That’s the one thing I really wish I’d learned a long time ago.

It’s been almost three years. There’s not a week that goes by without me coming back to this passage. It changed the way I see my own work. It changed the way I see the work of others.

I never thought to thank Mark for that interview, beyond the usual appreciation email I sent to him after it was published. I never thought it would be the last time we spoke. I never thought that he would be gone so soon.

After Mark passed away, I found out that his portfolio site was taken over by some online scammers that are now hosting a casino cashgrab. It pains me that we don’t really have any good way to dispute such a takeover. It pains me that we don’t really have any good way to preserve somebody’s legacy online in the same place they had when they were alive. But I knew immediately that Mark’s legacy needed to be preserved.

I’ve spent these last seven weeks reconstructing Mark’s portfolio from the wonderful Web Archive, and extending it with more of his work that he has done in the last decade or so. Although it was his decision to put some of his later work on Behance and ArtStation, I feel that all of his legacy deserves to be celebrated and commemorated in one place. I can only hope that Mark would agree.

This is where you can find it. It is a reconstruction of his main portfolio, with the following additions:

  • All recent work from Behance, including his comeback to the world of fantasy user interfaces in season 4 of Westworld.
  • The work that he shared with me for our interview.
  • Articles, interviews and presentations going all the way back to 2007. I wish I could have done more here, but a big chunk of those have either been lost forever, or are locked behind conference paywalls. I have a lot more to say here, but this is not the right place for it.
  • Photos of Mark from his Facebook friends.

As long as my site is up and running, this tribute to Mark will be accessible online.

Mark, I can’t thank you enough for finding the time back in 2021 to do that interview. I wish I would have reached out after we did it and met you in person. And now that moment is gone forever. All I can feel is a deep appreciation for what you’ve achieved in the last 25 years, and a profound sadness about all the future things that could have been. Rest in peace.

Mark Coleran
14 September 1969 – 14 June 2024

 

Radiance 7.5.0

June 25th, 2024

Less than one year to go until it celebrates its 20th anniversary, it’s time for the next release of Radiance. It’s a minor one, focusing on stability and bug fixes. First, I’m going to use emojis to mark different parts of it like this:

💔 marks an incompatible API / binary change
🎁 marks new features
🔧 marks bug fixes and general improvements

Component

  • 💔 Revisit circular progress indicators
  • 💔 Do not force BIG_FIT_TO_ICON presentation state for command buttons configured with custom icon dimension
  • 🔧 Fix visuals of disabled command buttons under rollover state and never background appearance strategy
  • 🔧 Fix inconsistent font metrics of label texts during printing
  • 🔧 Fix crash on computing the resize sequence of flow ribbon bands with 2 components
  • 🔧 Fix ribbon band content disappearing after a certain combination of user interactions with the ribbon on Windows OS

Theming

Radiance focuses on helping you make elegant and high-performing desktop applications in Swing. If you’re in the business of writing just such apps, I’d love for you to take this Radiance release for a spin. Click here to get the instructions on how to add Radiance to your builds. And don’t forget that all of the modules require Java 9 to build and run.

Radiance 7.0.0

January 20th, 2024

It gives me great pleasure to announce the next major release of Radiance. Let’s get to what’s been fixed, and what’s been added. First, I’m going to use emojis to mark different parts of it like this:

💔 marks an incompatible API / binary change
🎁 marks new features
🔧 marks bug fixes and general improvements

Component

Theming

There’s still a long road ahead to continue exploring the ever-fascinating depths of what it takes to write elegant and high-performing desktop applications in Swing. If you’re in the business of writing just such apps, I’d love for you to take this Radiance release for a spin. Click here to get the instructions on how to add Radiance to your builds. And don’t forget that all of the modules require Java 9 to build and run.

Into 2023

December 31st, 2022

It’s been a busy year for my desktop-focused projects, and things are look bright going into 2023. Here’s the rough outline of what I’m planning to work on.

The first big chunk of work that will probably take at least another two or three months to complete is going to be bringing the full ribbon component to Aurora. This has started a few weeks ago, and I’m done with the first pass of prototyping the ribbon APIs. Those are not final yet, and they will get tweaked as I get to the implementation details of the many moving pieces underlying this component.

The second big chunk is going to be around defining and using colors. Code-named Chroma, this effort aims to bring more clarity and control over working with colors in core and custom skins, inspired by the ongoing evolution of design systems such as Material and others. Falling under the overall umbrella of the Ephemeral design system, the plan is to introduce it to both Aurora and Radiance, and replace the existing color scheme and their mappings.

And last but most definitely not the least, are the plans to explore the third twin to Radiance and Aurora, and bring the full breadth of Ephemeral, including its theming layer and all the components, to the world of Flutter. Much as Aurora, this is going to be a multi-year project.

Happy New Year and stay tuned for more details!