Apple Wireless Keyboard and Bluetooth profiles

Briefly

I read with great interest Shibel K. Mansour’s review of the Logitech K480 keyboard. That keyboard was an option I seriously considered when I was looking for a Bluetooth keyboard to use mainly with my iPad for longer writing sessions. I remember finding the design attractive and sturdy enough. But the most interesting feature was the multi-device support and the ability to retain three different Bluetooth profiles to easily switch between devices.

But since I was looking for something lighter and less bulky (the Logitech K480 weighs 820 grams, which is roughly 200 grams less than an 11-inch MacBook Air), I ended up with the Incase Origami Workstation, which actually was the first accessory I had considered, since I already own an Apple Wireless Keyboard.

I’m really satisfied with the Origami Workstation. My Apple Wireless Keyboard is, by default, paired with the Power Mac G4 Cube (I bought a USB Bluetooth adapter long ago and use the Cube with the Wireless Keyboard and a wireless Mighty Mouse); at first I feared that, every time I wanted to grab the keyboard to use it with the iPad and the Origami Workstation, I would need to pair the keyboard with the iPad and then re-pair it with the Cube when I was done with the iPad. Not a big deal, but a tedious added step nonetheless. 

It turns out that it’s not necessary. Perhaps it was well-known and I’m just stating the obvious, but in case you didn’t know this either, I found out that — after the initial pairing with the Mac and then with the iPad — the Apple Wireless Keyboard remembers the pairing with both devices. When I take it with me to use it with the iPad, I simply activate Bluetooth on the iPad, turn the keyboard on, press a key, and it’s connected. When I bring the keyboard back to the Cube, I just turn the keyboard on, press a key, and again it’s connected. Very handy.

Not a laptop for writers

Tech Life

I have already offered a few first impressions on the new 12-inch MacBook with Retina display. In brief: it’s a lovely machine, it’s light, it has a gorgeous screen, a long battery life, an interesting new trackpad, and it could very well be my next Mac — too bad its quirky keyboard is a deal-breaking feature for me.

Back in April I wrote: I type a lot every day, so keyboard performance in a computer is one of the most important features for me. So, for the better part of the time I spent with the new MacBook, I tried to type as much as I could. And, like Christina Warren, I too found that “extended periods typing on the new MacBook keyboard tired my wrists a bit more than a traditional keyboard.” I also found the short key travel discomforting for my fingertips after just 15 minutes of more-or-less uninterrupted typing. Two months ago, my conclusion on the MacBook (and its keyboard) was:

It’s maddening. What I kept thinking was This should be the perfect computer for a writer and at the same time I was thinking I just can’t write on this MacBook all day.

Meanwhile, thanks to a generous acquaintance, I’ve had the opportunity to try the 12-inch MacBook much more extensively. I was hoping that my initial negative impressions regarding the keyboard would attenuate by spending more time typing on the MacBook and familiarising with the new hardware, using it in generally more comfortable situations than standing at an Apple Store desk without being able to move the computer much. Instead the experience did nothing but confirm I just can’t type consistently, comfortably, and for long sessions on this machine. Which is really a pity.

So when a friend pointed me to Matt Gemmell’s recent piece, A Laptop for Writers, I was curious to read an assessment that certainly promised to be different from mine.

Gemmell writes:

Otherwise, I was fluent and back up to speed with the new keyboard within an hour of switching over. It’s just not as different in use as it at first seems. The only lasting effect of the switch for me is that the keyboards on the Air, and my wife’s MacBook Pro, now feel spongy – but still perfectly usable. The shallower action on the new model still has enough travel to let you know that you’re typing. My error rate after the first day or so wasn’t any higher than on the Air’s scissor-action keys.

I used my loaned MacBook intensely over a weekend (Friday included), and while the typing mistakes almost entirely disappeared after a couple of hours, the keyboard maintained its unfamiliarity under my fingers all the time. When I briefly returned to other Macs and keyboards I use (like my MacBook Pro and my G4 PowerBooks) — as Gemmell notes — their keys felt softer and spongy indeed, but my fingers also felt quite relieved.

I’ve been lucky to never seriously suffer from RSI, but I’ve also always been careful. I believe that shallower-action keys are probably easier on the wrist. Whilst the keypress force on the new MacBook is delivered over a shorter travel, making it feel harder, I suspect that overall there’s less actual muscle movement required to operate each key compared to the much higher travel on the scissor-style keys on Air and Pro models (and indeed the desktop Apple keyboards).

In my experience, the opposite is true. I think we should not consider ‘key travel’ and ‘force to apply when typing’ as always in direct proportion. The keys of the Apple Extended Keyboard II, for example, have way more key travel than all modern Apple keyboards, but their responsiveness didn’t require me to apply more force. They have a different, and probably better, feedback that makes up for the longer key travel. That, in turn (at least for me) makes typing on such a keyboard much less stressful for my fingers, hands and wrists than typing on any modern flat keyboard. The only exception being the keyboard of the aluminium PowerBooks, which may sound and feel mushy to some people, while I find it to be one of the most comfortable and easy-on-the-hands Apple laptop keyboards ever.

Other mechanical keyboards I’ve used in the past, while having more or less the same key travel than the Apple Extended Keyboard II, required more force — perhaps because the keys themselves felt less robust, more wiggly, or because the switch mechanism simply required more force for the key to register. 

Back to the MacBook keyboard, I ended up tiring my fingers and wrists much more than with any other keyboard (mechanical or otherwise) I’ve tried previously also because I could not find and retain the ‘right’ force to apply when typing. It’s like the keys always register slightly before the expected travel, and that kept my typing unbalanced and erratic. When you pass your fingers over the MacBook’s keyboard, you have the feeling you could simply touch type, applying very little force. In reality, you have to apply a bit more force, but each time I tapped on a key, I ended up with the feeling I was just hammering on it too much. The feeling I kept having while typing on the MacBook keyboard was: Too little force, and I risk not typing some of the characters; a bit more force and it feels like I’m bashing on the keys.

Perhaps the title I’ve chosen for this article is too harsh and just provocative for the sake of being provocative. Perhaps other writers out there may find the MacBook’s keyboard perfectly adequate for their needs and habits. But I’m really having a hard time believing such a keyboard can be comfortable in the long run for someone who writes for a living. After three days spent typing on the MacBook’s keyboard for very long sessions (e.g. five consecutive hours with brief pauses here and there), my hands and wrists were exhausted. I’m still convinced the new MacBook’s keyboard is for truly casual users, people who type URLs in the browser, write emails and the occasional note or document or blog post. Unlike Gemmell, I don’t think that “[a writer’s] work can happily masquerade as casual use”, nor that it’s comparable to what a blogger does. Writers may use less CPU-intensive tools, and that may give them an advantage in the choice of what computer to use, but their work and their computer usage is certainly not casual.

My only WWDC 2015 wish: a truly better OS X

Tech Life

In less than an hour the WWDC 2015 will begin. This time I haven’t been reading much about it, and I don’t know anything about related rumours. The only thing I’ve caught on Twitter about the next versions of OS X and iOS is that for both, the focus will probably be more on technical refinements than a superficial list of shiny new features. Oh, and that the San Francisco font will probably become the new system font for OS X 10.11. If these things turn out to be true, well, it’s good news to me.

I’ve nothing to complain about iOS 8, actually. It has been working very well on all of my and my wife’s iOS devices (iPhone 5, iPad 2, iPad 3), and I’ve enjoyed all the new features and improvements over iOS 7. Such improvements, I feel, have made sense, and have noticeably contributed to an overall better iOS experience.

Those who have been following me for a while now will already know what I think about OS X Yosemite. While iOS 8 has truly felt like an improvement over iOS 7 and a further step in the right direction, I can’t say the same about Yosemite. Full disclosure here: at the risk of sounding full of bullshit and unprofessional — no, my stance on OS X Yosemite doesn’t come from direct experience. I still haven’t installed it on my MacBook Pro, and I don’t intend to even if the Mac technically supports it. But I have had enough of it from indirect or ‘quasi-direct’ experience, meaning I’ve used other people’s Macs with Yosemite installed, usually to perform some troubleshooting session. 

So far, even without installing it on my Mac, I can say that Yosemite has largely been an unreliable experience, and has felt unnecessary for my Mac computing needs. Let me reiterate the point: the impression of unreliability and unpredictability is not merely derived from hearsay, or simply based on the (admittedly numerous) complaints people have voiced online. It’s something I’ve witnessed with my own eyes when assisting other users with Yosemite installed on their Mac. Most of these users, I should add, are rather tech-savvy people, not Mac novices at all.

As for considering Yosemite an unnecessary upgrade: last year, I was initially excited by this new version of OS X. Especially when it was confirmed it would run on my aging mid-2009 MacBook Pro. I couldn’t wait to take advantage of what I considered the best innovation in Yosemite: Continuity and Handoff. I was ready to forget about my utter dislike for Neue Helvetica as system font and the new design of the user interface. But when I realised that Continuity wasn’t supported by my MacBook Pro’s hardware, the initial enthusiasm rapidly faded away. Meanwhile, friends and acquaintances who had upgraded started asking for my help — their Macs felt more sluggish, they had all kinds of problems with Wi-Fi, and so on. 

So I began delaying the upgrade on my Mac. I waited for 10.10.1, then 10.10.2, then 10.10.3… But meanwhile I’ve also been asking myself, more and more frequently, what’s the point? Why should I install Yosemite on my Mac? Mavericks works fine. I don’t like Yosemite’s UI. I don’t have a retina display nor have I good eyesight, so Neue Helvetica is a definite step back compared to Lucida Grande. The only aspect of Yosemite that could be truly useful to me — Handoff — is not supported on my Mac (and my iOS devices are too old anyway). Photos for Mac alone is not compelling enough. Why lose time to install, and then surely troubleshoot, OS X Yosemite, when I can stay on Mavericks, keep working in an environment that’s stable and doesn’t give me surprises or show unexpected behaviour, and whose user interface I actually like better?

So here we are. The WWDC 2015 is about to start, and I really want to know what are the plans for OS X 10.11. I do hope Apple’s focus will be on offering a sort of ‘stable version of Yosemite’ kind of update, like Snow Leopard was to Leopard a few years back. I have come to a point in my computing experience where I’m more interested in stability rather than new features for the sake of adding features. How innovation is implemented is more important to me than innovation ‘just because,’ if you know what I mean. Therefore, my only wish for OS X 10.11 is that it doesn’t feel as ‘beta’ as Yosemite still feels after a few minor updates.

The hiatus

Briefly

It’s been over a month since I last updated this place. The other day I tweeted a hint as to why:

Still, since I have received a few concerned messages about my silence, I figured I could give a quick update regarding this hiatus. The short answer is, I’m fine, I’ve just been busy doing other things. The more articulate answer is, There are a few reasons behind my not publishing anything since the end of April.

  1. Vantage Point magazine takes up a fair amount of my time. Working on two issues per month is hard. I knew it when I self-imposed this periodicity at the start, and although I’ve been a bit behind with the schedule, I’m confident my (few) readers will understand that I always try to put quality before anything else and I don’t want to rush an issue just for calendar reasons. Each issue has a theme, and sometimes finding one can be surprisingly difficult. Lately I’ve practically scrapped an entire issue because I was not satisfied with the chosen theme and the articles written about it. I’ve also had to rewrite an episode of Low Fidelity, the sci-fi serialised novel that’s a recurrent feature of the magazine. By the way, if you’re a subscriber and you’re enjoying Vantage Point, please spread the word, help me expand my readership and make this endeavour worthwhile since I’m still operating at a loss and the magazine is still basically at the labour-of-love stage. Thank you.
  2. The (film) photography bug has bitten me once again, and hard. I’ve been shooting more, reading more about photography, spending more time on photography sites (damn you, Japan Camera Hunter), looking for new old gear, even discovering interesting YouTube channels on the subject (gasp!). I also managed to restore both a camera and a lens to a functional state, and that took time as well: 

    Canon A-1

    Canon A‑1 with 50mm f1.4 lens

  3. I’ve been trying out Textshot+, an interesting app by Lionheart Software — the creators of Pushpin, my favourite iOS client for Pinboard.
  4. Speaking of Pushpin, I’ve also been working on updating the Italian localisation (something long overdue, I know).
  5. Perhaps this will sound strange, but another reason I haven’t published anything tech-related here lately is that I haven’t found anything in tech worth being enthusiastic over. New stuff is introduced all the time, and maybe it’s just that I’m having difficulties with keeping up with the pace, or maybe it’s the maddening pace of the debate surrounding whatever’s being introduced that I find more alienating than ever. Since nobody seems interested in slowing the hell down, well, I did. There is less and less time to process information today — the tech world online is perpetuating this breakneck pace, where, say, a product is announced or introduced, and before you can even take a look at it yourself, a dozen sources are already throwing their opinions in your face. Sometimes the noise of all these opinions and speculations flying around is just too overwhelming and one needs to tune out.

The new sharing interface in Unread 1.5

Software

Supertop’s Unread (originally created by Jared Sinclair) is my favourite RSS reader on iOS. It’s thanks to Unread that I went back to actively reading RSS feeds on my iPhone. The interface is that good. (Here’s the brief review I wrote in early 2014 when the app first came out.)

The latest 1.5 update is really packed with bug fixes and assorted improvements. When an application has a great, well-designed, user interface, I like to see underlying improvements that make it more versatile and powerful without drastic changes and major disruptions to what truly works. In this regard, I commend the efforts of Supertop’s developers and I think they’re doing a great job.

But I also like to nitpick when an app I love is involved, and in this case my nitpicking is about the changes in the sharing interface.

A few days ago, when Supertop announced the new 1.5 version of Unread on their blog, they wrote this about the improved Readability View (emphasis mine):

This has been, by far, the most common feature request we’ve received for Unread.

Articles that are truncated in RSS feeds or linked from sites like Daring Fireball are now much easier to read. On the article screen, swipe from right to left to bring in the options menu then tap Readability View to load the full text of the article into Unread’s native interface.

This feature is particularly nice when reading at night since Readability View respects your chosen theme and won’t shock your eyes by opening a bright webpage.

The problem is that with the ‘improved’ sharing interface, they kind of went in the opposite direction. I often read RSS feeds at night, so I stick to dark themes for Unread. ‘Dusk’ and ‘Blue Train’ are my favourites, and ‘Halloween’ is truly an eye-saver late at night. It’s like having f.lux on the iPhone, in a way. Here’s an example of how Unread’s sharing interface worked before, taken from Unread 1.4.2 under iOS 7.1.2 on my iPhone 4. Let’s say I want to share an article via Twitter:

Share UI in Unread 1.4.2 - 1

Fig. 1

Share UI in Unread 1.4.2 - 2

Fig. 2

Share UI in Unread 1.4.2 - 3

Fig. 3

 

Notice how in Fig. 2 the UI of the list of available services perfectly matches the rest of the app’s UI, and also how beautifully integrated the interface for writing the tweet is. It retains the chosen theme’s colour scheme, and offers a dark iOS keyboard.

And here’s the same procedure when I want to share the same article using Unread 1.5 under iOS 8.3 on my iPhone 5:

Share UI in Unread 1.5 - 1

Fig. 4

Share UI in Unread 1.5 - 2

Fig. 5

Share UI in Unread 1.5 - 3

Fig. 6

 

When iOS share sheet comes up (Fig. 5) and I’m reading articles on my iPhone at night using the Halloween theme, all that white, light grey and bright colours are really a punch in my tired eyes, and the UI feels completely alien, not integrated with the app’s UI. I’m not a developer: I guess this change makes sense from a coding standpoint and in the grand scheme of things behind the scenes. Visually, however, it feels like a step back. Same goes for the (iOS default) Twitter sharing interface in Fig. 6., which is pretty ugly compared with Fig. 3. And this time the light iOS keyboard comes up: again, the effect is rather jarring when you’re using dark themes and reading at night.

About the sharing interface, Supertop wrote:

Unread was originally built before iOS 8 was released and Jared went to extraordinary lengths to integrate the app with services like Facebook, Twitter, Instapaper & Pocket. In iOS 8, Apple opened up integration between apps and services using the share sheet and we have fully embraced that in Unread 1.5.

It is now easier than ever to send links, article snippets and images to any other app on your device, whether to save articles for reading later or publish on your social network of choice.

When I started writing the draft of this article, I initially pointed out that, actually, the services listed in the new, native sharing interface are fewer than what was available before (see Fig. 2), and that I was truly missing sharing to App.Net and Pinboard (the service I use most). But in a following blog update, Supertop wrote:

Instapaper and Pinner (and probably others) currently don’t accept images, so when you try to share a post that has images, they don’t appear as share options. Brian Donohue, the developer of Instapaper tweeted that it’ll be fixed in the next release.

In the mean time, here’s a handy work around: Tap and hold on the article title and a share sheet will appear that is targeted solely for sharing URLs and Instapaper and Pinner will appear here.

It works, and I can share to Pinboard now, but I still think the previous interface — albeit probably more difficult to maintain from a technical standpoint and less flexible overall — felt more integrated with the app and more pleasant to use.