Updates
-
@beckblack Hope all is well. Keep us posted.
-
@beckblack Everything going to be okay?
-
@beckblack !!!
-
@masande Burn him, he is a witch!
-
Hunkered down. Tonight is tornadstic!
-
@davidhamrick Hate it.
-
@mikeligon In the immortal words of Vader: NOOOOOOOOOOOO!!!!!!!!!!!!!!
-
Brook: This spaghetti isn't made from the neighbors. Right mom? Hanna: Dad was born without a brain. Sunny: ...
-
@mikeligon I was being serious. Sounds like you guys had a pain getting up there.
-
@mikeligon Finally! Reindexing and running a Time Machine backup now. Seems a bit peppier. Safe, speedy travels!
-
All day hard drive replacement = super fun thrills. (at Mercury Intermedia)
-
@BlakeAllen and a love for Botox? (sorry, happy birthday)
-
@beckblack Makes you think he probably isn't very good at choosing cars either.
-
Just found a snowball in my freezer. Kids...
-
@robbfladry haha
-
@robbfladry we could probably set up a trade for your Yanni collection.
-
@Mike_FTW Your best one yet! Might I suggest, "I hope you dance." for your next collaboration with West Elm?
-
@bradhaynes How can you improve on perfection?
-
@globalmoxie @cvilly Their "Up" button has a left facing arrow and is consistent with the location of the iOS back button. My head hurts.
-
No matter what the system says, it is never "unexpected" when an Adobe product crashes.
Photos
Posts
I asked him if he would come up with a few options. And he said, ‘No, I will solve your problem for you, and you will pay me. And you don’t have to use the solution — if you want options, go talk to other people. But I’ll solve your problem for you the best way I know how, and you use it or not, that’s up to you — you are the client — but you pay me.’
And there was a clarity about the relationship that was refreshing. Obviously, he had been thinking about that relationship for many years or decades. It was evident in several types of things that came up during the relationship.
Mark Potts decries the efforts of print media organizations for their initial attempts at bringing their content to the iPad:
And now comes a new digital medium, the iPad, and…yep, they’re doing it again.
Some of the biggest names in publishing have made a big splash with the introduction of Apple’s new tablet by releasing iPad apps for their publications. Alas, too many of them have fallen into that same old trap, trying to replicate a print experience on the iPad’s screen.
This is bullshit. The platform isn’t even a month old, and we’re already critiquing what’s not been done with it? Developers realistically had but a generous month to quickly build these applications (without the devices to run them on, even!), attempting to effectively translate their content and the experience. Consumers should be so lucky to even have these media on the device at launch, and I’ll personally say that I’m tremendously impressed by the applications that were available at launch. Yes, some floundered, but on the whole, the offerings were (and are still) quite impressive.
And while there is clearly room for improvement and additions to these apps, who’s to say he or she knows what approach will be best for this platform? I think a lot of ideas of what’s conceptually possible sound incredible on paper but stack up to be underwhelming or of little use once implemented. Marco Arment nailed it when discussing his approach to building his wonderful service, Instapaper:
If I let users steer product decisions, the result would be a massive codebase producing a bloated, cluttered product full of features that hardly anyone used at the expense of everyday usability and polish on the features that matter. Like Microsoft Word. Or Firefox.
By listening too much to outside suggestions, I’d destroy the very reason why I’m receiving them.
This is the problem the Popular Science app faces. They implemented what sounded like a great concept, one that’s been posited in science fiction film and literature, and is indeed an impressive technical achievement. But after repeated use, the interface gets tired and stale, and eventually, the app as a whole becomes a frustrating experience. It’s worth noting that users of the app are already expressing this very sentiment in reviews in the App Store.
If there’s one thing printing daily has taught publishers (or perhaps has invoked upon itself), it’s people’s desire for a routinely great, simple, and straightforward daily news experience. So, that would seem the logical place to start with this platform.
Potts also argues that the experience of the website counterparts of these media exceeds that of their native applications:
All of these publications’ Web sites are all far better than their apps—and on an iPad, hello, the Web is just a screen-touch away. Not surprisingly, these apps get fairly low user ratings in the iTunes app store. Customers know when they’re getting shoddy products.
I think this evaluation is rather subjective, but I personally find almost every native app to be a better experience than the website. Links and general interface elements on websites are designed to be interacted with a pixel-precise cursor, not a comparatively giant and clumsy fingertip. Text is rendered at a size and in a font that’s optimal for browsers, not at appropriate, comfortable reading sizes on a screen that you hold or in rich, native typefaces. Photos are smaller, and the majority of video on websites won’t play because they have to cater to the unwieldy universe of browsers with various capabilities. If you want to adjust these to fit the screen by constantly pinch-zooming to scale each story, photo, and video, be my guest, but I personally find the experience tiring and frustrating.
All said, Potts does go on to admit the time window for development was small:
We’re still very early in the game for publishing on the iPad, of course—the device has only been on the market for two weeks. It’ll be a while yet before software developers really get the hang of it and create apps that take full advantage of the new power and user experience the tablet computer (and its coming competitors) represents.
But this time concession effectively invalidates the entire argument. Even without acknowledging the time constraints, which is how this piece initially reads, I find it nauseatingly self-entitling to demand and expect something so groundbreaking without considering the real-world constraints of actually building the damned thing.
Perhaps we should re-examine Potts’ argument in a year or so, after adequate time’s been given for the platform to mature and we can see how those fare who build something “of” the platform instead of “on” it. Then we’ll see who can say “they’re doing it again.”
No matter how beautiful your interface, it would be more beautiful if there were less of it.
Amy Martin’s winning entry for Public Option Please’s art contest is really wonderful.
There is a period of learning where the interface is allowed to be a little overbearing. This stuff is training wheels. It makes the interface a little bulky and slower moving, in a way, and that’s okay for now, for the iPad.
Chiquita Banana Redesign, DJ Neff
This is so much fun. Especially love the skateboard graphic.
We need to get past this idea of saving, because the status quo is leaving the building, and quickly. Not just in print of course, but in your industry too.
This David Rawlings and Gillian Welch performance at NPR is absolutely stunning. If you haven’t heard their cover of Bright Eye’s Method Acting transitioning into Neil Young’s Cortez the Killer, this is the time to rectify that oversight. If you want to move directly to that performance, jump to the 7:42 mark.
Love their tag “Sometimes we get confused too”.
It’s like designing saddles for unicorns. Only worse.
Audio
Posts
Mercury Intermedia is proud to announce the launch of USA TODAY on the Android platform. This native application offers news, scores, photo galleries at a glance. In addition, users can get weather for their favorite cities or their current location as well as vote on the popular USA TODAY Snapshots, with instant poll results viewable by your state and city.
This application uses some of the best features of the Android OS, including a full-featured rich user interface, GPS, and others, while adhering to the standards of the Android device, making it a comfortable experience for the Android user.
Developing for Android was an interesting experience, as was the challenge of porting from iPhone to Android. We felt strongly that the app itself had to have the look and feel of an Android device, not just create iPhone-ish elements to show up on Android. Some things were easy decisions, such as moving from the bottom oriented TabBarController of the iPhone to the top oriented TabHost in Android. Others were more challenging, such as deciding how to use the physical elements of the G1 (menu button, trackball) vs solely relying on touch screen elements. But all in all, we’re proud of the product, and hope consumers find it easy to use.
We’ve immediately jumped into other projects, but if we can get our heads above water, we’ll post some more of our experiences/pain points/successes.
For more information, go to the Android marketplace on your handset, or go to http://www.usatoday.com/android/
In the comments of my previous post “iPhone UI Vector Elements”, one of our readers asked why we would bother going to the trouble to recreate vector versions of the iPhone user interface. It’s a great question which leads to the larger, more general question of why we would create application mockups in vector format at all.
Stick with what you know
First off, just to clarify, I am a designer. I leave Apple’s developer tools to our programmers and stick to the visual tools that I am most comfortable and familiar with. I am fortunate to be in an environment where quality UI and visual design is valued on the same level as rock solid performance, speed, and reliability. Getting my hands dirty with the developer tools has never really been an option. The developers at Mercury Intermedia handle all of the X-Code and Interface Builder work and do a tremendous job.
Be efficient
Next, I want UI objects that I can quickly and easily modify and manipulate. It is much easier for me to make adjustments to vector objects when I need modified color variations and custom UI elements for new applications. Although the argument could be made for Photoshop, and it certainly has it’s place for more complex or organic visuals such as EA’s Sudoku or Clif Bar’s Save Our Snow for example, the speed and ease of editing and duplicating vector files for standard UI elements in Adobe Illustrator tends to generally be more productive.
Be prepared for the unexpected
Beyond all of this, you never know when scalable graphics may meet unforeseen needs. For example, we had a prominent design publication recently request several print quality screenshots of the USA TODAY application for an upcoming issue. If we hadn’t built this project in vector format, it would have been much more difficult and time consuming to go back and recreate files that the publication could use. We would have likely ended up with less than ideal, tiny screenshots of our app or would have had to set up a photo shoot of the app on the device. Since we had already built all of our mockups in vector format, it made creating these print quality screens much less painful.
Click to view a high resolution example from the USA TODAY iPhone app
(This file is 1200×1800 and will scale to fit the height of your browser window.)
Plan for the future
Finally, it is almost imperative at this point to build applications with higher resolution devices in mind. As Sebastiaan de With recently hypothesized in his Cocoia Blog post “Not hosed (for now)”, “In the future, Apple will change to a better (not necessarily ‘bigger’) screen, and developers of iPhone apps will face a huge issue: how do we scale the interface?” There is no clear road map as to when this could happen, but I do agree that it is likely to be an issue at some point.
Arguably more pressing than the possibility of an iPhone screen resolution change is the possibility of a new Apple portable form factor altogether. What if Apple follows through as the rumors have recently suggested and releases a Kindle sized tablet device? What if that device has an App Store environment? We would like to be prepared if our clients come to us wanting their applications ported to such a device. Not that we would port an iPhone application as is over to a device that much larger, but we would certainly have a huge head start.
In conclusion
There are certainly talented developers out there who can handle the majority of their standard iPhone visuals directly in Interface Builder. Others out there who might turn to a graphics based application, have spent years in Photoshop and would find Illustrator so foreign as to greatly reduce some of the above mentioned advantages. However, for those of us comfortable and familiar with Illustrator, it is an excellent tool for user interface design and holds many advantages. If you have been considering exploring Illustrator further for UI work, I would highly recommend it.
Most of the visuals for our applications start out as vector mockups in Adobe Illustrator. So when we started working on the USA TODAY iPhone app, we went looking for vector UI elements. Although there are a few good Photoshop resources and even a nice OmniGraffle iPhone UI file or two out there, we couldn’t find anything in vector format.
Rather than cry over the lack of good vector elements, we took it upon ourselves to recreate a large portion of the iPhone’s UI elements so we would have them available for future projects. Obviously, we aren’t telling you all of this just to wave it in your face and tell you we have fancy tools that you don’t. Because we care so much about our fellow iPhone developers, we are making our vector files available to you today. (I think I just made myself throw up a little.)
So you are probably asking, “Billy Mays*, how much is this going to set me back?” If you act now, this priceless file can be yours absolutely free. You heard me correctly, absolutely FREE!
Click on the images below for a preview of the elements included. (Of course you’ll need to download the Illustrator file to see everything in its full vector glory.)
Download iPhone UI Vector Elements Now (2.6MB)
For Photoshop iPhone UI files check out Teehan+Lax’s iPhone GUI PSD. For OmniGraffle iPhone UI files, Patrick Crowley’s Ultimate iPhone Stencil is excellent.
* Mercury Intermedia’s free iPhone UI vector elements file is in no way endorsed by Billy Mays, though it would be awesome if it were.
Update: I posted a followup to this article addressing the advantages of using vector files for user interface projects. “Why build iPhone app mockups in vector format?”
Welcome to the Mercury Intermedia blog. We’re going to be posting here from time to time to announce new features and projects, share ideas, explore new topics in development, and share riveting tales about the questionable carpet choices building management made during building renovation.
So the first post here is of the announcement variety. We just pushed version 1.1 of USA TODAY for iPhone/iPod touch to the App Store today. This particular version expands upon the ways in which a user can share articles from the phone, including additional Twitter client support (Tweetie, Twittelator, TwitterFon now join Twitterrific on the supported Twitter client list), as well as integration with the new Facebook Connect for iPhone API.
Two other items of note:
1. Greatly improved LBS support: we had two LBS issues. First off, the app had a tendency to hold on to previous locations, which affected travelers who would be physically onto another location, but virtually stuck in their previous location according to our app. Secondly, the accuracy of our our location detection was in many cases just off, putting someone in neighboring cities. There will always be issues with iPod Touch LBS, and some issues with first gen iPhones, but in general, we’ve tightened up the Current Location process.
2. Sticky slider bar: we’re big fans of the slider bar as a method of navigation, immediately choosing to adopt it after seeing it’s effectiveness in the Facebook iPhone app. However, while our slider bar worked well for flick motions, it didn’t respond well to press and hold actions. That’s been taken care of as well - now you can take all the time you want, indecisive section navigator guy!
There were a handful of other fixes, but we’re pleased to offer the additional Twitter support as well as Facebook integration. We’ve got much more in store for the app in the coming months, and we’ll expound as we can.
Thanks for reading, and hope to see you ’round these parts again real soon.
Checkin history
-
4 months ago
-
4 months ago
-
4 months ago
-
4 months ago
-
4 months ago
-
4 months ago
-
4 months ago
-
4 months ago
-
4 months ago
-
4 months ago
-
4 months ago
-
5 months ago
-
5 months ago
-
5 months ago
-
5 months ago
-
5 months ago
-
5 months ago
-
5 months ago
-
5 months ago
-
5 months ago
