It’s been about 6 weeks since we started working on our first product; TweetMag. We thought we’d lift our heads from its design and development just long enough to share a screenshot with you.

For those who didn’t catch the first post, or who haven’t seen the tweets, TweetMag is an iPad and iPhone app that takes twitter feeds and turns them into wonderfully simple magazines. It works by finding links in a twitter user, list or search – then grabs their headlines, abstracts and media to create a TweetMag. Articles then become prioritized by what’s being tweeted about most.

The shot below shows what my TweetMag would look like:

If you want to stay up-to-date it’s best to follow TweetMag or leave your email address on the TweetMag site.

Since its announcement and subsequent release, the general consensus appears to be a) the battery life / speed & industrial design is unparalleled, and b) the software is somewhat limiting. I’ll definitely echo these observations, however I’ve noticed much of the criticism has been focused on issues which will undoubtable be addressed in future OS updates. Everyone is busy looking at their feet, complaining about the immediate and obvious shortcomings, when they should be focused on where Apple is going with the iPad. Make no mistake about it, the iPad really is Apple’s reconception of personal computing, however they’ve only taken the first of many steps in that direction.

“It’s just a big iPod Touch”

When Apple first announced the iPad, an audible groan echoed across the Internet. It’s just a big iPod Touch appears to be the most common reaction upon seeing the iPad for the first time, and while there is definitely some validity to that observation, it’s not exactly true. Yes, the iPad looks and feels very similar to an iPod Touch, and yes they share the same operating system (which really makes them fraternal twins). However, the iPad currently sits uncomfortably between the iPod Touch and the MacBook; Born from a smartphone and wanting to be laptop replacement, but unable to reach its full stride. It wants to run—and starts to pickup pace— but then trips over it’s own feet.

Coming from an iPod Touch or iPhone, you’ll feel right at home. Sure, the screen is roughly 4x the size, but it looks and functions more or less the same. You’ve got the singular home button on the face, the same dock along the bottom, and the same lock screen (now with 4x the unused space) . However, once you start using iPad-optimized Apps, it becomes clear that this is a different ballgame. The larger screen affords a completely unique experience, and the developer community is taking full advantage of this. It’s actually quite amazing how quickly the operating system disappears once you launch an App. The App fills the entire screen and you immediately feel like you’re holding an entirely different device. But then you try to delete something and a tiny blue dialog window appears, drowning in a sea of pixels. It feels odd and out of place, like a relic from a different era. There are all sorts of little details like this that reflect the iPads smaller-screen lineage.

You get the same feeling when you turn the iPad on for the first time, and you’re forced to tether with your computer and authorize via iTunes. Arguably, you shouldn’t have to do this with an iPhone/iPod either, but it feels even worse with the iPad. This isn’t a device that should require a separate computer. You should be able to give it your Apple ID and have everything automatically sync. Apps, email contacts, calendars… files. And this is where the iPad begins to move towards the MacBook and then stumbles. I want to save & edit files on the go, but there’s no meaningful way of managing them. While I believe Dropbox is vastly superior, Apple’s iDisk should really be the “exposed” filesystem on the iPad. It shouldn’t be an App like it is on the iPod, but a home directory that’s accessible by all Apps and sync’d across all your devices. But what happens if you’re sharing the iPad with other family members?

“The First Real Family Computer”

I’ve seen a number of people describe the iPad as the first real family computer, and I would agree that this is an apt description. My iPad will live in the kitchen and will be shared by my wife and I. However, when I started setting up my email and calendars and contacts, I realized that this wasn’t really going to work. We may want to share the device itself, however we don’t want to share applications. The iPad really needs unique user accounts, complete with independent setups. Of course, this adds a magnitude of complexity and I’m unsure if the platform can really support it. Fundamentally, the iPhone and iPod Touch were designed as single-user devices, but the iPad clearly has multi-user intentions. Being that the share the same OS underpinnings, I can see how the iPad could be weighed down by it’s resolution-deprived siblings.

I’m incredibly excited about how much potential the iPad has. I’m sure Apple will address the multitasking issues that plague it and the iPhone. I’m sure they’ll correct the odd interface holdovers its smaller siblings. And I’m hopeful they’ll introduce some sort of cloud-based solution for the file management issues. The only question is if Apple will allow for multiple users per iPad, or if they’re expecting 1 iPad per person. I have a feeling it’s the latter.

It seems the screens we shared of an alternative home screen for the iPhone created some buzz. We had no intention of taking it any further than a blog post but we figured this was something worth seeing through.

We got in touch with Jay Freeman a.k.a saurik. He’s the guy behind Cydia, an application for jailbroken iPhones that allows you to browse and download apps outside of actual app store. He’s crazy smart, passionate and geeky – three things we love here at T+L. Jay is going to be instrumental in making this happen.

If you haven’t already figured it out, getting this on your phone will require you to jailbreak it. That may not be an appealing option for many, but for the 2 million plus out there who have already done it and for those that are comfortable with doing it, this can be a reality.

The app and the underlying technology to make it happen are still in development so what comes out the other side will differ from what we originally proposed. The biggest change will initially be that it will render only on the lock screen. We went down this road for a number of reasons, primarily because of its relative ease of implementation, though there’s nothing easy about it. Jay is creating a framework to write custom lock screens called Cydget. Our concept will act as the guinea pig.

No word on an actual release date yet due to a last minute crash bug, but from what we hear it’s not far off. We’ll make an official announcement once it’s available. You can follow @teehanlax,
@gteehan and @saurik if you’re looking for more detail since we tend to tweet about this stuff more frequently than we blog about it.

Had the opportunity to attend this month’s Torchi event, featuring two guests from Microsoft. Lisa Anderson, MS Surface User Experience Director, talked about the fundamental shift from command line interfaces to GUIs, to what she called Natural User Interfaces (NUIs, I guess). Some really cool theoretical thinking in her presentation but it would have also been nice to get into a more concrete discussion about where they’re headed with Surface. I guess we’ll just have to wait for the SDK and interface guidelines spec. Lisa talked about how they’re trying to make the interface “disappear” by leveraging intuition and allowing interaction through direct manipulation. But there must be at least some standardized interface elements built into the Surface and I’m really keen to learn what these are and how they work.

Jansen Harris’ discussion about his work heading up the Office User Experience Team was also really interesting and much more concrete. No matter how you feel about Microsoft’s past performance when it comes to innovating the user experience, it’s hard to deny that they did a great job with the latest Office suite (and this has been borne out both critically and in terms of revenues generated). 3 things Jansen mentioned that stuck with me:

1. Early-on they established a set of design tenets to guide decisions at a high level over the course of the project. One that really stood out to me was “Straight-forward is better than clever.” I know I’ve often been guilty of breaking that rule :)
2. Developers took the first couple of months basically rebuilding the programatic foundations for Office specifically so that the UX team could afford to make mistakes and revise as they progressed along.
3. The Office 2007 team was comprised entirely of people who passionately believed in the project. If your heart wasn’t in it (and there were apparently those who fundamentally disagreed with the idea that MS could or should re-engineer the UX for Office), they found something else in the company for you to work on.

In general, I was impressed by how much grunt-work the team put into validation and evaluation throughout the design process. Rather than testing for testing’s sake or gathering data just to justify pre-ordained decisions, they used evidence to answer very focused, well-defined questions.

Quick plug: ToRCHI events happen monthly and are usually worth coming out to. Great guests and good discussion.

Available for pre-order today the new Adobe Creative Suite boasts a ton of new features across all platforms, however in this post I’ll only highlight a couple…

Now when you zoom the canvas it’s as smooth as butter and when you get close enough you can see the pixel grid. Useless to designers who work outside of the realm of screen res, but now digital designers can be accurate right down to the pixel. And lord knows, love is in the details.

But I think the more interesting of these new functions is what Photoshop is calling Content Aware Scaling. Normally when you scale an image horizontally or vertically, each pixel is literally stretched so that the final image is distorted. This relatively new technology, which Adobe actually bought from another development, does something completely different. Something that actually makes the scale tool useful. When stretching an image, a very complex algorithm carefully selects which pixels to stretch and which not to stretch. Meaning, that you can stretch a photo without it actually looking distorted. See below.

As smart as this tool is, it’s still not perfect. But I’m sure we can find some humor in applying it to such images like close cropped portraits. Below is a very informative video published by the software company that originally developed it.

- Greg Washington