This Week's Sponsor:

Turbulence Forecast

Know before you go. Get detailed turbulence forecasts for your exact route, now available 5 days in advance.


Posts tagged with "iOS"

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

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







#MacStoriesDeals - Tuesday

Black Friday is getting close, expect the deals to get better everyday until Friday! Here are today’s @MacStoriesDeals on hardware, iOS, and Mac apps that are on sale for a limited time, so get them before they end!
Read more