Federico Viticci

10804 posts on MacStories since April 2009

Federico is the founder and Editor-in-Chief of MacStories, where he writes about Apple with a focus on apps, developers, iPad, and iOS productivity. He founded MacStories in April 2009 and has been writing about Apple since. Federico is also the co-host of AppStories, a weekly podcast exploring the world of apps, Unwind, a fun exploration of media and more, and NPC: Next Portable Console, a show about portable gaming and the handheld revolution.

Annotable Adds Wide Color Support and Haptic Feedback on iPhone 7

Nice update to Annotable, my favorite image annotation tool for iOS: the latest version has brought support for wide color (pictures you edit will be saved in wide color without changing their color profile back to sRGB) as well as haptic feedback on the iPhone 7.

The latter is one of the most interesting third-party implementations to date: both in the app and the Photos editing extension, Annotable will give you feedback when you snap to the edges of a picture, when an oval becomes perfectly circle or a line perfectly vertical/horizontal, or when you’ve zoomed an image to fit. That’s a clever way to augment the user experience without cluttering the interface with visual messages, and it’s line with Apple’s adoption of the Taptic Engine for system haptics as well.

Permalink


How the Touch Bar Works

Good overview of the Touch Bar and its developer API by Benjamin Mayo:

Developers can display pretty much whatever they want whilst their app is in the foreground; this includes swapping out views and buttons depending on the current window of their app (a compose window necessitates different Touch Bar accessory views than the inbox window). However, the Touch Bar does not allow persistent widgets, status items or similar features like always-visible news tickers. These constraints are unlikely to be lifted either; Apple is imposing the restriction so that the UI under the user’s finger isn’t constantly changing due to spurious notifications or text messages.

Apple wants the bar to display peaceful relatively-static UI based on the current task. Major changes to the Bar should only happen when the application state drastically changes, such as opening a new tab or beginning a new modal activity. To repeat: once an app’s window is not active, it loses its control to influence what is shown on the Bar. The system Control Strip sits to the right in a collapsed state by default, but can be disabled entirely in System Preferences if desired.

This makes sense to me: the Touch Bar is intended to be an extension of the keyboard that deals with input – it’s not a smaller Dashboard or a widget container. This means that apps like PCalc won’t be able to persistently display their controls in the Touch Bar unless they’re the frontmost (active) app.

The more I think about it, the more the Touch Bar feels like the natural evolution of QuickType and the Shortcut Bar from iOS – to the point where I wonder if we’ll ever get this kind of evolution on the iPad Pro as well (where the current app is always the frontmost one and system controls could use a faster way to be engaged than Control Center). Perhaps with a new external keyboard with its own embedded Touch Bar and T1 chip?

Permalink

Canvas, Episode 22: Workflow – The Basics

This week Fraser and Federico begin a multi-part series on the iOS automation app Workflow.

For the next several weeks on Canvas, we’re going to focus on Workflow with a series of episodes aimed at covering the basics of the app, its automation features, as well as its more advanced aspects. In the first episode, we explain what Workflow is and its key principles. We have lots more to come, so stay tuned. You can listen here.

Sponsored by:

  • Pingdom: Start monitoring your websites and servers today. Use offer CANVAS for 20% off.
Permalink

The TV App as a Supporting Actor

Joe Steel makes a good point in his look at this week’s Apple TV announcements:

Why is TV the app an app and not the Home screen on the device? It’s obviously modeled after the same ideas that go into other streaming devices that expose content rather than app icons, so why is this a siloed launcher I have to navigate into and out of? Why is this bolted on to the bizarre springboard-like interface of tvOS when it reproduces so much of it?

You could argue that people want to have access to apps that are not for movies or TV shows, but I would suggest that that probably occurs less often and would be satisfied by a button in the TV app that showed you the inane grid of application tiles if you wanted to get at something else.

As I argued yesterday on Connected, I think the new TV app should be the main interface of tvOS – the first thing you see when you turn on the Apple TV. Not a grid of app icons (a vestige of the iPhone), but a collection of content you can watch next.

It’s safe to assume that the majority of Apple TV owners turn on the device to watch something. But instead of being presented with a launch interface that highlights video content, tvOS focuses on icons. As someone who loves the simplicity of his Chromecast, and after having seen what Amazon is doing with the Fire TV’s Home screen, the tvOS Home screen looks genuinely dated and not built for a modern TV experience.

I think Apple has almost figured this out – the TV app looks like the kind of simplification and content-first approach tvOS needs. But by keeping it a separate app, and by restricting it to US-only at launch, Apple is continuing to enforce the iPhone’s Home screen model on every device they make (except the Mac).

That’s something the iPad, the Watch1, and the Apple TV all have in common – Home screen UIs lazily adapted from the iPhone. I wish Apple spent more time optimizing the Home screens of their devices for their different experiences.


  1. The Watch is doing slightly better than the other ones thanks to watchOS 3 and its Dock, but the odd honeycomb Home screen is still around, and it doesn’t make much sense on the device’s tiny screen. 

Perpendicular Philosophy

Jason Snell:

Apple, in contrast, believes that touchscreen interfaces are great and computers are great and they’re not the same thing. Apple has steadfastly resisted adding touchscreens to the Mac, and when you ask the company’s executives why, they have been remarkably consistent on this point for the past few years.

What defines a computer, they’ll say, is that it’s made up of two perpendicular surfaces. There’s a vertical display surface, more or less up and down, right in front of you. And there’s a horizontal control surface—a table or desk or the base of a laptop—that you use for input and control. If you want a Mac, that’s what you get. If you want a touch-based device, get an iPad.

Seen through this philosophy, the new MacBook Pro and its Touch Bar interface fit perfectly. The Touch Bar brings the things Apple loves about touchscreen interfaces—customizability and support for multitouch—and adds it to the control surface of the Mac, right above the keyboard. It doesn’t break Apple’s definition of a computer at all, because it’s a new sort of touchscreen, and it’s part of the keyboard area, not the display area.

I don’t use a Mac as my daily computer anymore, and I don’t plan to switch from my iPad Pro, but the Touch Bar is the first change to the Mac line to pique my curiosity in years. Probably because it borrows from what makes iOS great.

Permalink

Ars Technica on the T1 Chip in the New MacBook Pro

Andrew Cunningham, writing for Ars Technica, got Apple on the record about the T1 chip and what it does for security and the Touch Bar:

At any rate, the T1 is an interesting chip that does much more than support Touch ID and Apple Pay. Apple tells us that it has a built-in image signal processor (ISP) related to the ones Apple uses in iPhone and iPad SoCs, something which Troughton-Smith suggests could protect the camera from malware hijacking. And its Secure Enclave handles the encryption and storage of fingerprint data and protects it from the rest of the operating system and its apps, much as it does in iOS.

When you interact with the Touch Bar, Apple tells us that the majority of the processing is being done by the Intel CPU, although the T1 also appears to do some processing in specific situations for security’s sake, as when Apple Pay is used. But to keep the Touch Bar from counting toward the number of external monitors you can use (Intel’s GPUs support a total of three separate displays, AMD’s support six), the T1 is used to drive the Touch Bar’s screen. From what Apple told me, it sounds like the image you’re seeing is actually being drawn by the main system GPU but is being output to the display by T1, not unlike the way other hybrid graphics implementations work.

Between A-series chips, the W1, and the T1, Apple’s most fascinating work is happening in the custom silicon space. The whole T1-Touch Bar deal is extremely intriguing.

Permalink

New MacBook Pro Touch Bar, T1 Chip Run on a Variant of watchOS

Interesting findings by Steve Troughton-Smith: the Touch Bar on the new MacBook Pro appears to be running on a variant of watchOS under the hood, with the T1 SoC handling security (primarily) for Touch ID as well as the bridge between macOS and the Touch Bar (over a USB connection).

This lines up with what I heard ahead of the event – that Apple would embed a SoC reminiscent of the Apple Watch S1 in the new MacBook Pros – but the implications of what Apple did with the T1 chip and the Touch Bar run deeper than I expected.

For one, macOS can now leverage years of security that went into honing the Secure Enclave and Touch ID on iOS – all while working with an ARM architecture inside the MacBook Pro instead of x86. And it even seems like the T1 is driving the iSight camera (for security purposes) and that it may render certain UI elements on the Touch Bar directly instead of delegating that to macOS (again, for security). And when macOS isn’t running, watchOS alone can render UI on the Touch Bar (likely for Boot Camp).

It’s fascinating to think that part of watchOS (which has been optimized for low power consumption and lightweight touch UIs) is being used to power a marquee hardware feature of the new MacBook Pros. And even more intriguing is the idea of watchOS and years of investment in iOS security helping make Macs more secure – it’s not too absurd to imagine that future T-series chips may drive security of other Mac input methods.

I collected some of the most interesting tweets about this below, so you can read the technical bits for yourself.

Read more