iOS 5.1.1 Released for iPhone, iPad, and iPod touch

An update to iOS is now available via iTunes or, more preferably, the Software Update feature on your device, found within the Settings app.

Here’s the changelog:

This update contains improvements and bug fixes, including:

  • Improves reliability of using HDR option for photos taken using the Lock Screen shortcut
  • Addresses bugs that could prevent the new iPad from switching between 2G and 3G networks
  • Fixes bugs that affected AirPlay video playback in some circumstances
  • Improved reliability for syncing Safari bookmarks and Reading List
  • Fixes an issue where ‘Unable to purchase’ alert could be displayed after successful purchase

For information on the security content of this update, please visit this website:

http://support.apple.com/kb/HT1222

I know I experienced the camera locking up with HDR on when using the lock screen shortcut, and I’ve had run-ins with AirPlay video and the ‘Unable to Purchase’ dialog. So I am pretty pleased with this update. It weighs in around 43-55 MB, depending on your device.

¶ The 7-inch Apple "Tablet"

There has been a lot of buzz lately about a 7-inch Apple tablet — specifically a 7.85-inch tablet — supposedly in the works in Cupertino.

I’ve been thinking about such a tablet for a while now, and wondered whether such a thing, if brought to market, would be labeled as part of the iPad family. To me, it makes far more sense to move the iPod touch product line up to this mid-range screen size.

Odi Kosmatos crunched some numbers and discovered that the difference between 7-inches and 7.85-inches is everything:

Perhaps you’ve read these Steve Jobs quotes before, they go something like this:

“The 7-inch form factor is not a good size for tablet applications” and “7-inch tablets should come with sandpaper, so that users can file down their fingers so they can use them.“

Note the words in bold.

Every rumor and theory about a smaller iPad I have seen seems to claim it will be 7.85″ with a 1024×768 screen. If that were the case, Steve Jobs would be right on the money with the above quotes. A 7.85″ 1024×768 display would be appropriate if the smaller tablet were designed to run iPad applications, because these applications could run unscaled on the device, at a 1:1 pixel ratio. However, the PPI of that 7.85″ screen would be 163. But the size of the user interface elements on iPad applications are tailored for a 132 PPI screen. If squeezed into 163 PPI, every button and control would become smaller, harder to accurately touch. Hence the need for sandpaper.

The same argument applies if the 7.85″ tablet had a retina display with the same resolution as the new iPad’s 2048×1536. It would have 326 PPI, but the UI elements of retina iPad applications are designed for 264 PPI. Sandpaper required.

But consider if the new tablet had a 7″ screen. What’s so special about 7″? A couple of very interesting things.

A 7″ diagonal screen (7.08″ to be exact) just happens to be the exact size of two by two iPod touch retina displays. That’s a 4″ x 6″ display surface. An iPod touch screen has 326 PPI. The 7″ screen would also have 326 PPI just like iPhones and iPods. This would yield a resolution of 1920 x 1280. This resolution would be able to run current retina iPhone applications pixel perfect using the traditional 4:1 pixel scaling, like retina displays do with non-retina apps.

What’s so special about that? By running iPhone applications on a larger screen, as opposed to running iPad applications on a smaller screen, you don’t need the sandpaper anymore. Heck, if you have fat fingers, you’ll rejoice. Larger touch targets are just easier to hit, but still look amazing, especially text, which will be drawn using the full 1920 x 1280 resolution. Anyone that finds the iPod touch or iPhone screen slightly cramped would love it, and could continue to enjoy amazing apps like iMovie, iPhoto, and other apps designed for iPhone.

I have no doubt a 7.85-inch tablet-like device exists in Apple’s labs. I also have no doubt a 7.08-inch device exists. Of course Apple plays around with different approaches to products. I’m sure Apple has both a larger iPod and a smaller iPad, and they are testing which is best.

Everyone has focused on the smaller iPad because the iPad is the new hotness. I am much more interested in what a larger iPod would bring to the mid-range.

Here’s how I see it:

  • The iPhone needs to fit in your hand and your pocket comfortably, hence its 3.5-inch screen.
  • The iPod touch, to date, has been modeled after the iPhone. This is mainly due to transitioning from the old iPod classic size and to simplify software design. Apps made for the iPhone work on the iPod touch. Simple.
  • The iPad is great, and its large screen, while not as portable as some would like, is comparable to a glossy magazine in both size and quality. Its keyboard is very comfortable in landscape, and in portrait, if you split the keyboard.
  • There seems to be plenty of people that want something larger than an iPhone but not as large as an iPad.

That last bullet point is where I see the opportunity for the iPod to move to. I think iPad apps would feel cramped. But if iPhone/iPod interfaces could be scaled up at retina resolution to a 7-inch screen, I think that would satisfy most people desiring a mid-range screen. Thumb-typing would still be comfortable. Text and pictures would be sharp. Developers wouldn’t need to rewrite the book again. And, most of all, the iPod line would be given new life.

When the first iPad was announced, it was derided by many as being “just a big iPod touch”. That clearly has not been the case, because software differentiated it. But does that mean there isn’t a market for an actual “big iPod touch”? I think a 7-inch retina display iPod would grab the corner of the market that Amazon is currently aiming at with the Kindle Fire. It isn’t a full-featured tablet, like an iPad. It isn’t a full telecommunication device, like an iPhone. But it is the best of both worlds for certain people — the people who want a little more screen than an iPhone but want more pocketability than an iPad.

For instance, my three-year-old son uses a second-generation iPod touch filled with kid games, educational apps, children’s books, and Pixar movies. He usually uses it for an hour or two after his nap, and he loves it. But, boy, does he look at my iPad with envious eyes. He loves the larger screen. I do not love him toting around an iPad that is as big as his entire torso.

A 7-inch iPod would be fantastic for him. It’s the perfect size for a young child. I imagine there are many adults who would enjoy it as well.

All-in-all, if Apple is planning to bring a device with a screen in the 7-inch ballpark to market, I think I’d rather see the iPod touch grow up a little, rather than the iPad get squeezed into a smaller screen.

The Other Side of the Coin

Shawn Blanc:

It strikes me that the Retina display is the other side of the coin to iOS. Meaning, iOS is the software and the screen is the hardware and that’s it. Those are the two sides to this coin. On a laptop or desktop computer you have three user interface components: the keyboard, the mouse, and the screen where you watch the user interface. On the iPad you have one user interface: the screen. And you touch and manipulate what is on the screen.

¶ Byword for iOS | Review

If there is one genre of app that I have more than my fair share of, it’s text editors. Since launching techēse, I have been seeking the perfect writing environment that gives me the least resistance to getting words written. I started with OS X’s TextEdit, and eventually found myself doing my long form writing in TextMate after I began writing in Markdown.

TextMate worked for a time. It is very much a coding environment. And even though Markdown is a syntax that relates to code, it is very much a writer’s syntax versus a coder’s syntax. TextMate is great for coding. But it has never satiated the writer in me.

I started using Byword just about a year ago on my Mac, when it added Markdown syntax highlighting and declared its focus to be the best Markdown editor for writers — which it most definitely is. In fact, nearly every article here has been written in Byword.

Byword is great on the Mac. But often I want to write on my iPad, and even sometimes, though rarely, on my iPhone. I’ve used Dropbox to sync and either Elements or iA Writer, which are both fine writing apps. But I have long wished for Byword on my iOS devices.

Today, the wait is over. Byword for iOS is here.

I’ve been beta testing Byword for iOS since early December last year. It’s a universal app with iCloud and Dropbox support.

Byword for iOS also has a handy keyboard accessory which shows word and character counts (tap it to switch between the two or show both simultaneously). The accessory can also. Be swiped to show quick cursor arrows and common syntax used when writing in Markdown. There are two different parts of the accessory for Markdown, pictured below.

Byword Keyboard Accessory
Byword Keyboard Accessory

Byword also allows you to preview Markdown, export as HTML, send as an email, and print. It also includes TextExpander support.

Byword for iOS doesn’t yet have the dark theme like the Mac version, but it is coming in a future update.

I’d be remiss if I didn’t mention the update to the Mac version, which now has iCloud integration. iCloud on the Mac is still pretty clunky when it comes to setting up files to be synced. That’s definitely a limitation of OS X Lion, which should be alleviated this summer by OS X Mountain Lion’s revamp of the Open/Save dialog.

First, on the Mac, you have to save the file locally. Then, while the file is open in Byword, you click the File menu and then click Move to iCloud. Once the file is in iCloud, everything becomes pretty seamless. Setting up a file within iCloud on iOS is straightforward. Just click the + button from the file list and give it a name.

In fact, you can have the same iCloud file open on your Mac, iPhone, and iPad, then type on one device and watch it appear on the other two a moment later. It really feels like magic.

Byword for iOS is a fantastic, well-designed app that gets out of your way and let’s you write. It also has the best Markdown-optimized keyboard accessory I have seen on iOS yet, making it hands-down the best tool for a writer using Markdown.

If you are a serious writer, you need Byword.

Byword for iOS is being introduced at $2.99 $4.99 on the iOS App Store, and Byword for Mac is $9.99 on the Mac App Store.

P.S. This entire review was mainly written on the iPad, with a little bit on the iPhone and Mac, kept in sync the entire time with iCloud.

iOS 5.1

I expected iOS 5.1 to be announced at the iPad event the other day, since it had been in beta for developers for quite some time. I also expected it would be released about a week later, in order to give developers some time to update their apps for it.

However, it came out just a couple hours after the keynote, and I downloaded and installed the update on both my iPhone and iPad over-the-air, without iTunes’ involvement at all. It was a quick and easy upgrade, and improves a number of things.

Camera

I was greatly pleased to see the revamped lock screen camera shortcut on the iPhone. When iOS 5 debuted, you could double tap the home button from the lock screen to reveal a quick camera access button. Now that is always visible, and you just slide the lock screen up.

Related to that, the camera itself loads faster than I remember it ever loading before.

Also, iCloud’s Photo Stream now allows you to delete photos from it, which is handy for getting rid of screenshots and poorly composed photos.

Finally, on the iPad, Apple redesigned the camera app, moving the shutter release closer to where your thumb is likely to be. I don’t take photos from the iPad often, but this will be nicer for the rare times I do.

Battery Life & Performance

Apple says it fixed bugs affecting battery life. Battery life hasn’t been shabby on my nearly two year old iPhone 4 at all, but I have noticed over the past couple of days that it is better.

As far as performance goes, everything feels a little snappier, especially with the built-in apps.

AT&T “4G”

Apple made the odd decision to change the cellular label to 4G on the iPhone 4S when in an AT&T HSPA+ network area. As an iPhone 4, owner, this doesn’t apply to me. Now, do not think that a software upgrade magically unlocked 4G access. No, this is just some marketing crap AT&T has been doing to say they have “4G” speeds. So, AT&T has 4G and 4G LTE. The latter is what every other carrier calls 4G.

Ben Brooks has a great article about why this move feels like a crap move from Apple.


All in all, iOS 5.1 is a top-notch upgrade for performance, battery, and usability. I’m sure there are many more tiny refinements to discover. If you haven’t upgraded yet, go to Settings > General > Software Update on your iOS device and get it.

¶ A Big Day for Tweetbot

Tweetbot 2.0

Tapbots released Tweetbot 2.0 for iPhone and iPod touch today. What was already a really well polished Twitter client is now at a high gloss. My biggest pet peeve has been fixed in the timeline. You used to need to tap twice on an account name or link to activate it, and now it is a single tap.

I also really enjoy how Tapbots has relocated the retweeted by icon and text. Direct messages have been overhauled and display much like the Messages app in iOS 5, but with Tapbots’ signature style.

The coolest little touch is the redesigned notification of how many new tweets have loaded. It sticks to the top of the tweet list, and as you scroll it counts down the number of remaining new tweets. Like I said, it’s a nice touch.

Tweetbot for iPad

But that wasn’t all Tapbots was up to today. They also released Tweetbot for iPad, which is a separate app from its smaller-screened sibling.

Tweetbot for iPad is really impressive. Tapbots has paid a lot of attention to detail in the interface and interaction. The layout and flow of the app was designed brilliantly.

If you miss what once was Tweetie, and abhor what Twitter has done with it since acquiring it, you should give Tweetbot a shot. It’s the kind of “everything and the kitchen sink” client that Tweetie was. The iPad experience is fantastic. Most of all, Tweetbot’s polish on both devices makes it feel like a precision instrument.

For $2.99 each, you can buy Tweetbot for iPhone/iPod touch and iPad on the App Store.


I am a huge Twitterrific advocate. Not only is Twitterrific a universal app, it has a Mac version, and offers the same experience across the board. However, in recent months, Twitterrific has tended to fall behind on the feature list when compared to the competition. I still love Twitterrific and it is my go-to app, mainly because the mindset of its design gels with me. And, after years of using it, I have found that when it starts to lag behind in comparison, it means it is on the verge of a giant update to lap the competition.

¶ App Within an App

I always try to use a stock app that comes with my iPhone, iPad, or Mac if it can do what I need it to satisfactorily. Hence for quick notes I use the built in Notes app on my iPhone quite a bit, especially since I know, thanks to iCloud, that the note will be on my iPad and Mac if I need it. And when Reminders arrived in iOS 5, I eschewed the other app I was using in favor of Apple’s solution, because Apple’s app performed the same function that I needed. Heck, it provided a little more with location-based reminders, which are awesome.

I do, however, have one little annoyance about Notes and Reminders — the way they are integrated into the Mac. On iOS, Notes and Reminders get their own apps. On the Mac, they are relegated to being apps within an app. Notes and Reminders are shoehorned into Mail and iCal, respectively.

I would much rather Notes and Reminders have their own apps on the Mac, with similar interfaces to their iOS counterparts. Notes, on its own, could effectively replace the Stickies app on the Mac.

My problem with Notes and Reminders being integrated into other apps is consistency. A great example of consistency between the Mac, iPhone, and iPad is Twitterrific. The app offers the same experience across all three devices. The user never has to question how to do anything on each device. Learn once, apply everywhere.

Take a new user, give them an iPhone for a bit. Sit them in front of a Mac, and tell them to find their reminders. I bet they’d hunt for a Reminders app. In fact, they’d probably be confused to learn that Reminders is part of iCal. It doesn’t really make sense.

One of the greatest things Apple did when releasing the iPad was to keep the experience familiar and consistent. Lately, the experience on the Mac has started to feel like a neglected ugly duckling.

¶ Notifications

I have been thinking a lot lately about notifications on my devices — both Mac & iOS. Today, after a conversation with some friends on Path, I finally tied it all together in my mind to share with you.

Let’s start with the Mac.

Mac

The Mac’s notifications are all over the place. In the Dock, you can have badge notifications, and apps can bounce up and down like a Jack Russell Terrier for your attention. Badge notifications have also crept into Launchpad, which isn’t easily discoverable. One last place for badge notifications is the apps residing in the menu bar.

Then there are modal notifications that pop up over whatever you are currently working on.

This is the same sort of mess that we had in iOS until banner notifications and the Notification Center came into play in iOS 5.

On top of the frenzy of notification placement, some of these just look plain outdated. For instance, iCal notifications look like this:

iCal Notification
iCal Notification

What era is that clock from? It even annoyingly shakes. It is an eyesore on the beauty of the rest of OS X.

OS X Lion was billed as being the best of iOS being brought back to the Mac. And in many ways, it is. Take full-screen apps, for instance. I use them all the time (like right now, as I write this in Byword). I keep Safari, Mail, iCal, iTunes, & Reeder in full-screen almost all the time.

Notification center and banner notifications would be awesome, especially in full-screen apps. Give me a keyboard shortcut or trackpad gesture to quickly see all my notifications on my Mac, and subtly show me reminders and alerts without demanding an interruption to my workflow.

iOS

I have very little to complain about regarding iOS notifications since iOS 5’s revamp of the system. But there is one.

I do not always have my MacBook Pro with me. And when I am on the go, and at night, it is closed, making notifications impossible. This is not the case with my iPhone. It is always with me, always on, and charges in a little tray on my nightstand. It serves as my alarm clock.

But emails and app notifications roll in throughout the night, making noise and briefly turning on the screen.

There are only two types of notifications I want while I am asleep: the alarm that I set and phone calls (in case of an emergency). Everything else needs to shut up.

Here is what I propose: a global Do Not Disturb setting for iOS notifications. This would prohibit notifications from turning on the display or activating the speaker during hours that I set (like when I am sleeping). There would be a list of exceptions that I could set, such as alarms or phone calls. For everything else, it can stack its notifications in the Notification Center for my review in the morning.

The ring/silent switch works great for things like meetings, where you can be alerted to something via vibration if need be. You’re still active in that situation. It doesn’t work that well for sleeping at night, though.

Being able to tell our apps that we do not wish to see or hear them right now would be great.

Update

on 2011-12-30 21:01 by Chris De Jabet

Just a quick addition to note that Airplane Mode isn’t enough to solve this problem. Some apps, like games, will use local notifications that do not require a network connection. My wife likes to play Tiny Tower, which will use local notifications to update her on when something needs restocking or a new level of her tower is ready (it’s simply using time calculations for all this).

Also, Airplane Mode would disrupt the ability to receive calls. And we all know the moment you disable calls is when the crap will hit the fan.

Speaking of Android Software Updates

Vlad Savov:

Samsung has just distributed the worst news of this Ice Cream Sandwich upgrade cycle: the popular Galaxy S smartphone that sold 10 million units last year and the 7-inch Galaxy Tab tablet won't be upgraded to Android 4.0. The company's argument is that they lack sufficient RAM and ROM to run the new OS alongside TouchWiz and other "experience-enhancing" software. This will come as a massive blow to the great many users of the Galaxy S, who would have rightly expected the 1GHz Hummingbird processor and accompanying memory to be able to handle ICS — it's the same hardware as you'll find inside the Nexus S, and that phone is receiving Android 4.0 over the air right now.

The difference is the Nexus S runs pure Android, and the Galaxy S runs Samsung's own TouchWiz skin. Samsung (and other manufacturers who skin Android) always claim these skins enhance the experience. Those must be some wicked enhancements to forego the next generation of the OS.

A Good Smartphone Comes But Once a Year

Chris Ziegler writes an amazing editorial at The Verge about the effect of dozens of Android phones released each year compared to one great iPhone.

One of the greatest detriments is not being able to update those seemingly countless devices in a timely fashion (if ever).

This one’s just simple math: more SKUs means more firmwares, and more versions of those firmwares. Each of those versions needs the care and feeding of an engineering team, and there are only so many engineers to go around. If a particular model is unpopular — which is more likely when you’re releasing a countless array of them — long-term support becomes an even greater risk.

Compare that to the iPhone 3GS, 4, & 4S, which are all capable of running iOS 5. The 3GS was released two and a half years ago. Can any Android phone make that same claim?