This Week's Sponsor:

Textastic

The Powerful Code Editor for iPad and iPhone — Now Free to Try

Tim Cook Speaks With Businessweek In A Wide-Ranging Interview→

Tim Cook Speaks With Businessweek In A Wide-Ranging Interview

Josh Tyrangiel of Bloomberg’s Businessweek has a terrific and in-depth interview with Apple CEO Tim Cook. In it, Cook is asked a whole swathe of questions from transparency, to the recent executive changes, Apple’s competition, US manufacturing and a lot more. The whole article is available online and in the latest edition of Businessweek. NBC will also air an interview with Tim Cook today on it’s Rock Center program at 10pm/9c in the US.

Talking of Apple Maps, Cook is asked whether Apple took on an approach of doing something for strategic company purposes, rather than something that would make the product better. Cook rebuffs this suggestion and suggests that they wanted to enable certain features such as directions and voice integration and set upon accomplishing them.

 We set on a course some years ago and began to do that. So it wasn’t a matter of saying, “Strategically it’s important that we not work with company X.” We set out to give the customer something to provide a better experience. And the truth is it didn’t live up to our expectations. We screwed up.

Asked about manufacturing and whether Apple might bring back some manufacturing efforts back to the US, Cook responds that they will begin to do so in 2013 for certain Mac products. It lines up with recent reports of the new iMacs arriving with “Assembled in USA” engravings. You can also see an excerpt of the Rock Center interview here in which he discusses this transition back to the US.

And next year we are going to bring some production to the U.S. on the Mac. We’ve been working on this for a long time, and we were getting closer to it. It will happen in 2013. We’re really proud of it. We could have quickly maybe done just assembly, but it’s broader because we wanted to do something more substantial. So we’ll literally invest over $100 million. This doesn’t mean that Apple will do it ourselves, but we’ll be working with people, and we’ll be investing our money

These are just a few snippets of the interview, be sure to read the entire interview over at Bloomberg Businessweek, it’s a must read.

Permalink

Twitterrific 5 Review

Twitterrific 5. It’s been fun to watch Twitter’s reaction to an app that I, and other writers, wanted to surprise the world with. Alas, it was bound to leak, unsurprisingly by Apple’s Japanese App Store. The Iconfactory’s latest iteration of their famed Twitter client is shockingly different isn’t it? The same gut reactions I watched unfold on Twitter could not better describe the same gut reactions I had when I first saw just how striking the new interface is.

Sharing the first pic of Twitterrific 5 with my coworkers resulted in an immediate, “Wow.” After a few more screenshots, “That looks like a Windows 8 app. Like Track 8.” It’s an absolutely fair assessment. And it’s one I’ve seen echoed on Twitter as I watched the tweets scroll by. Thankfully, Twitterrific 5 is as much of an iOS app as it ever was. No text hangs off the screen — no “CTURES” as Federico and I will joke.

Twitterrific 5 presents itself dressed in black with Helvetica accents and familiar shades of orange and blue for mentions and messages. It’s both instantly recognizable and obviously different. In contrast to colored entries and standard rectangular iOS elements, it is typography, floating buttons, and rounded corners that are pervasive in the new Twitterrific.

Read more

Reverse Engineering Penultimate→

Reverse Engineering Penultimate

Fascinating analysis by Alex Caithness of CCL-Forensics about Penultimate (thanks, Clark), a digital note-taking app that was acquired by Evernote earlier this year. Penultimate allows users to draw on screen, simulating virtual ink with smooth lines and curves drawn upon a notebook-like background. That’s what CCL-Forensics tried to reverse-engineer.

Opening one of the “page” files we find another “NSKeyedArchiver” property list. After unravelling the structure of the file we find a top-level object containing further metadata (including a “blankDate” which appears to match the “created” timestamp reported in the “notebookList” and the dimensions of the note) along with a list of “layers”. Each of the “layer” objects (again represented by dictionaries) have keys for the layer’s colour (more on that later) the layer’s dimensions and a list of “layerRects” – sections of the layer where the user has drawn their notes; and that’s where we finally find the image itself.

Sort of.

The description of how Alex got around understanding how Penultimate stores information inside its library is highly technical, but easy to follow with screenshots and Alex’s clear explanation. Essentially, Alex ended up using Python and XML to retrieve the user’s drawings, stored as coordinates – not as “images of the ink”, as one would initially assume.

If anything, it’s a great reminder that our data can usually be retrieved in a variety of ways using forensic tools (and intuition).

Permalink

Disable Auto-Correct In Tweetbot for Mac→

Disable Auto-Correct In Tweetbot for Mac

I write in English, but I live in Italy. Some of my Twitter followers are Italian, too, and I like to talk to them in my native language. In the past weeks, I noticed an annoying bug: Tweetbot for Mac, my Twitter client of choice, couldn’t disable auto-correct (Edit > Spelling and Grammar > Correct Spelling Automatically) permanently. The option is there, but it appears it “doesn’t stick” after you enable it to send a tweet without auto-correct. This led to an increasing number of misspelled Italian tweets with English words mixed in (as per my Mac’s system language).

Fortunately, I’ve found the solution here. With a simple Terminal command, you can override Tweetbot’s default setting and disable auto-correct (but not spell checking) automatically.

This is exactly what I was looking for, so make sure to hit the source link to check out the full command.

Permalink

Pages For iOS and Change Tracking→

Pages For iOS and Change Tracking

Yesterday, Apple released an update for iWork on iOS that added, among changes to Numbers and Keynote, support for change tracking in Pages. I’m not a frequent user of this particular feature, but it could have come in handy when we edited my Mountain Lion review earlier this year. However, last night I noted how the way Apple implemented Change Tracking on iOS felt outdated and convoluted.

Jeff Richardson does use Pages on a regular basis and posted his thoughts on the new version (via David Sparks):

Track changes support has long been the Holy Grail for many litigators using an iPad or iPhone. For the most part, I really like the way that Apple implemented this feature in the latest version of Pages. I wish that the update included a better way to review each edit, but for the most part I suspect that I’ll just scroll through a document and look at the redline edits in the context of the document as a whole so this omission is not critical for me. The lack of support for Comments will sometimes be a problem (depending upon how often you work with people who use that feature), but as long as you know about it and have an app like Documents to Go, Office2 or Quickoffice Pro, you can work around the Comments omission when it becomes an issue.

I can see how lack of Comments and Review mode can be an issue for some users. Mostly though, I believe that the interaction of Change Tracking needs to be redesigned entirely. On Pages for Mac, you can simply click on a change to review it and accept it from a sidebar on the left; in fact, if you click on the blue boxes in the sidebar you can see the blue line connecting the change to the actual text being highlighted in real time. It’s a subtle visual hint, but it’s there.

I’m not sure why Apple decided to go with this simpler interface rather than cooking up a completely new one, but I have a couple of theories. My first thought is that text rendering and manipulation on iOS still doesn’t allow for fairly complex on-screen drawings such as the aforementioned blue lines; a second reason may be scrolling performances, especially on older devices (Pages still supports the iPhone 3GS). But I think that, overall, Apple decided to use this approach because is consistent with the current iOS text selection and because a major new version of iWork for iOS (possibly requiring iOS 6 or later, not iOS 5.1) could be on track for next year.

Apple has long touted iOS devices as heralds of the post-PC era, but iWork has been far behind its desktop counterpart (originally launched in 2009) for months. I expect iWork 2.0 for iOS to level the field in every area.

Permalink

Mapping The Entertainment Ecosystems: A Brief Revisit

In mid-October, we published a story on the entertainment ecosystems of Apple, Microsoft, Google and Amazon - looking at to what degree their music, movie, TV, eBook and app stores were available in international markets. Apple on the whole seemed to have the best average availability - slightly losing to Microsoft for the app stores and Amazon dominating everyone in the eBook store.

I’ve decided to briefly revisit the topic today because the original post garnered quite a lot of discussion and feedback and because of two “events” that have since happened. Firstly, Apple yesterday announced an expansion of the iTunes Music Store into dozens of new countries (and Movie store in a few additional countries). Secondly, I have since found two pieces of data on which countries Xbox Music is available in (for some odd reason I cannot find any official Microsoft document detailing the countries it is available in). So below is an update to the Music and Movie diagrams and graphs.

 

Note: Read the original ‘Mapping the Entertainment Ecosystems’ post which includes diagrams for eBooks, TV and App Stores.
Read more

Improving The iOS Keyboard→

Improving The iOS Keyboard

Chris Bowler, writing about possible improvements for the iOS keyboard:

The negative with writing on the iPad is typing. It’s a bit of a mixed bag experience — the iOS autocorrection is (at times) brilliant and I can fly along with confidence, knowing the OS is going to correct my typos. But when mistakes are made and are either not autocorrected, or autocorrected incorrectly, then the iPad becomes a less comfortable environment.

Remember when, ahead of the original iPad’s announcement in January 2010, rumors tended to focus on what the “tablet keyboard” would be like? Here are a few examples. In spite of the iPhone having shown that Apple simply wanted a regular keyboard’s appearance translated to multitouch, several people wondered whether Apple should do something different for the bigger screen. The answer was that they simply designed a “full-screen” keyboard.

As Chris notes, over the years third-party developers have extended the iOS keyboard with additional bars. Look at Writing Kit, Pythonista, Textastic, and iA Writer for examples of these modifications.

I think the discussion on the iOS keyboard often mixes writing with editing. Personally, I believe the iOS keyboard is great for writing, because it’s just a normal keyboard, but iOS text selection is in serious need of an update, because it feels outdated. I’m not sure the average user cares about better text selection, but for the sake of the argument, I will say that a better solution should be explored.

If you read those old pre-2010 posts on the “iSlate keyboard”, you’ll notice a common thread: that Apple must build something revolutionary for text entry. I recall some people guessed a split keyboard could be a possible implementation, and, in fact, that one came true in 2011. But what about text selection? I don’t think keeping on adding bars above the keyboard is feasible. Especially on the landscape iPad, a single bar alone sensibly diminishes the space available for writing – space being one of the most commonly cited advantages of the iPad against 16:9 and 16:10 tablets. On the iPhone 5, it’s an acceptable solution thanks to the taller screen, but, then again, the bar is too narrow to be a meaningful improvement.

Rather, I would say entirely new ideas for text selection and manipulation are the future. It’s the reason everyone got excited for the Hooper Selection: once you saw it, it just made perfect sense. Too, I wouldn’t completely forget about features that Apple put on the shelf, as they tend to come back.

So here’s my hope for the future of iOS for writing: the same keyboard, but also new, fresh ideas for text selection and editing.

Permalink

YouTube for iOS Gets iPhone 5 and AirPlay Support, iPad Version

Following a major update to Gmail for iOS, Google has today also released a new version of its YouTube app, which includes AirPlay and iPhone 5 support, as well as an iPad version that makes the app Universal.

One of the new features is the Guide of channels that you can access by tapping on the YouTube logo in the title bar; tap it, and you’ll go back to the app’s main sidebar, listing your account’s options and Channels. On the iPhone 5, YouTube is now optimized for the taller screen – a glaring omission that has annoyed several iPhone 5 users since the device’s release. Among other improvements – including clickable links in video descriptions and ability to add or remove a video from your playlists – a notable addition is AirPlay support: you can now natively stream videos to any AirPlay-compatible device such as the Apple TV or a Mac running Reflection (which is what I tested).

The iPad version of the app is rather obvious, but still welcome: it packs a sidebar on the left side, and main content on the right side of the screen. When you tap on a video, the right portion becomes the main view hiding the sidebar and displaying suggested videos on the right. Interestingly, you can’t browse and watch videos at the same time, as the sidebar will always be hidden after you click a video’s thumbnail.

For everything else, both the updated iPhone app and iPad version share the same features that I covered in my original review of the app, and today’s changes are definitely improvements worth checking out – it’s especially good to see Google supporting AirPlay right after the 1.0 release. Both on the iPhone and iPad, Google offers a feature in the Settings to open links in Chrome, also available for both platforms on the App Store.

The updated YouTube app is available on the App Store. More screenshots of the iPad app are available below. Read more

Gmail 2.0: A Year Later

Despite Google’s persistence on adopting web views in an iOS frame, Gmail’s iOS app has been consistently improved since its inception. For the amount of ridicule Gmail for iOS has received, whether it be for its mobile web disguise or a lack of support for multiple accounts, it’d be a shame not to recognize some of the substantial improvements that have been made to the app. While I didn’t think Gmail was a great app, I didn’t think of it as a bad app, offering a native Gmail experience for account holders who want to take advantage of Google’s quick search capabilities, labels, and importance markers. On iOS, the main benefit is near instant notifications, something that Apple’s native Mail app can’t take advantage of unless Gmail is set up as an Exchange account. (And that notification sound? One of the best.)

Read more