So when we decided to do a twitter client, my objective was to take that bird illustration and draw him with the same rules we apply to all of our icons (yes I’m still sad that Pastebot lost his eyes). No more than the drawing of the nurse or robot with the megaphone becoming an app icon. At the time, there was no thought of ever doing a Twitter client.
Mark: The original Tweetbot was a drawing I did for the bottom of our website that linked to our Twitter account. Was it difficult to translate him out of the square or have you always thought of the bots as three dimensional objects that you translated into icons?
#TAPBOTS TWEETBOT FOR MAC#
TNW: I’ve seen a few iterations of the Tweetbot for Mac icon come and go, but you seemed set on the bird from the start. But it’s a 1.0 and we still have a lot of work ahead of us. Do I feel like we’ve succeeded in taking our brand and making it feel like a mac app? I’m not really sure. So as long as we keep making apps for this brand, I will continue to take on this challenge. But Tapbots apps have a heavily branded user interface. So yeah, I can see how it must be ironic that I designed Tweetbot for Mac the way it is. Macromedia apps were notoriously bad and Adobe apps follow right behind them. I always hated Firefox on the Mac because of this. I’m a pretty harsh critic when it comes to “feeling like a native Mac app”. It was to take our signature look and feel on iOS and apply it to the Mac while still feeling like a Mac app. Then, add the fact that I’m sitting here designing my first Mac app and you have a huge recipe for disaster. Designing a “custom” interface just makes things harder. It just feels like there’s an infinite amount of variables you have to account for. Mark: Designing for the Mac is definitely far more challenging than iOS. TNW: I know that with iOS you know point by point how the app will display for everyone, but that’s not true with the Mac. How did you find the experience of designing your first Mac app for Tapbots?
0 kommentar(er)
