Posts in Linked

Touch ID and Error 53→

Christina Warren has a good roundup of Error 53 – an iOS system error that makes an iPhone unusable (bricked) if it detects a third-party Touch ID module when performing a software update:

Thousands of iPhone users have been left with bricked devices after having their home buttons repaired by non-Apple authorized technicians.

The Guardian on Friday reported on the issue, known as “Error 53” that apparently affects the iPhone 6, 6 Plus, 6S and 6S Plus.

The basic problem happens if you get your iPhone’s home button repaired anywhere other than an Apple Store or Apple-authorized repair center. If the home button — which includes the Touch ID sensor — is replaced, you run the risk of getting a dreaded “Error 53” on your phone.

What is Error 53? Well, it basically turns your iPhone into a brick. Why? Well it all ties into the Touch ID sensor on your phone.

As Apple notes in a support document (and in a statement provided to the press today), “iOS checks that the Touch ID sensor matches your device’s other components during an update or restore”, but the check could also fail because of an unauthorized or faulty screen replacement.

The problem isn’t Apple’s underlying reasoning, which makes sense from a security perspective, but the fact that a device gets bricked by an obscure error. Future versions of iOS should change this behavior and Apple should do a much better job at explaining what’s going on. A bricked device is an extreme measure (and a badly communicated one) when trying to save money by not going to an Apple retail store is so popular.

Permalink

Using Classic Mechanical Keyboards on Modern iPads→

Kevin MacLeod, following up on one of the geekiest photos I’ve seen on Twitter in a while:

You found a mechanical keyboard. An old Apple keyboard, or Dell, IBM, Focus, Acer, Cherry - doesn’t matter. It has good mechanical switches, and you want to use it with your iPad.

The good thing is, once you connect your keyboard to the iPad, iOS is fully capable of using it - the keys all work, you don’t need to install any drivers, jailbreak anything, or take any special steps. The tricky part is actually connecting these keyboards to your iPad.

I’ve never tried a mechanical keyboard myself (I probably should, given that I write at my desk quite a bit?), but I know this is going to be a fun weekend project for many.

Permalink

Pocket Adds New Typographic Controls for Premium Subscribers→

It’s nice to see Pocket is continuing to add new features exclusive to Premium subscribers. In the 6.2 update released today, Pocket has introduced 7 new fonts (including two of my favorites – Whitney and Ideal Sans), plus controls for line height and margin width. There’s also a new Auto Dark Mode setting (which could be a nice companion to Night Shift on iOS 9.3).

I’ve been trying Pocket again because of Recommendations (you can follow mine, too), and I had already bought a Premium subscription last year, but I haven’t found much utility in the permanent archival and auto-tagging functionalities. More typographic controls is something I deeply appreciate, and I hope we’ll see more Premium features this year.

Permalink

Connected: Dreaming Is Enough→

This week, Stephen and Federico talk about Stephen’s 20th Anniversary Mac, Airmail, Federico’s new NAS and the iPad Air 3.

If you didn’t catch my thoughts on the Synology NAS I bought in the latest Monthly Log for Club MacStories members, this week’s Connected elaborates on the subject quite a bit. You can listen here.

Sponsored by:

  • Braintree: Code for easy, online payments. Get your first $50,000 in transactions fee-free.
  • Squarespace: You should. Use code WORLD for 10% off.
Permalink

Nintendo’s Second Mobile Game to Feature “Familiar” Character→

Nintendo didn’t only announce details for Miitomo and My Nintendo this week. Here’s Takashi Mochizuki, reporting for The Wall Street Journal:

Videogame giant on Tuesday posted a sharp drop in quarterly net profit, but it stoked the hopes of fans by promising that its second smartphone game would feature one of the company’s best-known characters.

And:

“The second game won’t be another communication app, and we plan to adopt one of our characters that fans are very familiar with,” Nintendo CEO Tatsumi Kimishima said.

Mario is the obvious choice (as is Pikachu, also given this year’s 20th anniversary of the Pokémon franchise), but I’ve long argued that WarioWare mini-games would be great candidates for multitouch gameplay and, possibly, In-App Purchases. Still, Nintendo has plenty of options to choose from.

Permalink

Microsoft Acquires SwiftKey→

No productivity app seems to be safe with Microsoft. Following a Financial Times report from yesterday, the company has confirmed they have acquired SwiftKey, makers of the popular keyboard and predictive text engine for iOS and Android:

This acquisition is a great example of Microsoft’s commitment to bringing its software and services to all platforms. We’ll continue to develop SwiftKey’s market-leading keyboard apps for Android and iOS as well as explore scenarios for the integration of the core technology across the breadth of our product and services portfolio. Moreover, SwiftKey’s predictive technology aligns with Microsoft’s investments and ambition to develop intelligent systems that can work more on the user’s behalf and under their control.

In the coming months, we’ll have more to share about how we’ll integrate SwiftKey technology with our Guinness World Record Word Flow technology for Windows. In the interim, I’m extremely excited about the technology, talent and market position SwiftKey brings to us with this acquisition, and about how this further demonstrates Microsoft’s desire to bring key apps and technologies to platforms from Windows to Android to iOS.

SwiftKey is one of the most popular third-party keyboards on both mobile OSes; on iOS, it’s often relied upon by users who want a multilingual typing experience in a single keyboard. I’m interested to see how SwiftKey as a keyboard will continue on iOS – custom keyboards haven’t received much attention in the past two years, and they’re severely limited in how much they can integrate with the rest of the system.

Above all, SwiftKey is good tech for Microsoft. The acquisition gives them access to a large database of typing habits and patterns spanning 100 languages, and it’ll likely help them build text features on desktop and mobile. Long term, it’s hard to predict how Microsoft’s string of mobile app acquisitions will play out, but, right now, it’s clear that Microsoft is buying the best apps around.

Permalink

Activist Engineering→

Matthew Bischoff:

You’ve been there. You’re sitting in a meeting and your boss, a product manager, or an executive is talking about Q2 goals. They’re laying out a roadmap of the features that are going to be “coming down the pike”. All of a sudden you see it. An innocuous bullet that makes your blood boil: “Auto-invite friends”, “Re-engagement notifications”, or “Disable ATS”.

The particular feature isn’t important. What matters is that you’re the engineer that’s noticed this capital-B Bad Idea. You know why it’s a problem. This time it’s not just the technical debt or the time it’d take to implement. This idea is bad because it trades a worse product for a better “business”: revenue, eyeballs, impressions, you know the drill.

You have a choice in this moment.

Permalink

The Futility of Pleasing All Users→

Khoi Vinh made an interesting point in his consideration of a recent update to 1Password:

At this stage, having gone through at least six major revisions, the utility must accommodate many different usage styles—people who want strict separation among their vaults, people who want to see across all their vaults, and more. As with any software, as the number of use cases grows, it becomes harder and harder to reconcile them with a single coherent interface. That’s the unfortunate truth of creating great experiences; not all of your users are going to be happy all of the time.

I think there’s a middle ground here, though it isn’t often appreciated: settings.

As time goes on, I realize that apps that let me configure their behavior exactly like I want – 2Do, Fiery Feeds, and even the just-released Airmail – are what I prefer. An abundance of settings isn’t necessarily the best way to build an app (in some instances, it could be seen as a cop out from a developer who doesn’t know how to pick which features to ship, or as a case of feature creep), but after transitioning from OS X to iOS as my main computing platform, I tend to choose productivity apps that can scale, accomodating the needs of many users as possible.

Some people don’t like that, and there’s certainly a place for “opinionated” software that doesn’t overwhelm the user with dozens of settings, but it’s a trend I’ve noticed in the apps I’ve ended up using the most on iOS.

Permalink

Twitterrific Adds Redesigned Today View, watchOS 2 App, Refined Profile Pages→

Solid update to the Twitter client by The Iconfactory: version 5.14 of Twitterrific brings a redesigned and customizable Today screen to view an activity summary for the selected account (with a counter for quoted tweets, too), better support for 3D Touch to peek at events in the timeline, a watchOS 2 app, and the ability to preview recently shared media in profile pages.

I don’t use Twitterrific as my main client – I prefer Tweetbot – but choosing between the two is largely a matter of minor preferences at this point (one of mine: Tweetbot lets me see people who retweeted and faved one of my tweets from the tweet detail view). It’s great to see that The Iconfactory is getting rid of many of the old annoyances of Twitterrific: DMs are now excluded from the unified timeline (I criticized this here), the tab bar supports 5 buttons on iPad, where you can also choose to show it at the bottom in portrait (previously, the feature was iPhone-only). Great changes.

Twitterrific 5.14 is available on the App Store.

Permalink