Federico Viticci

10861 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.

iOS Stiffness: The Neglected Touch Down State

Max Rudberg:

I would love to see iOS 11 bringing subtle touch down animations to standard system elements, such as navbar buttons, table view cells etc. By doing it to the default components, third party apps would be affected by it as well. This would make for a consistent and more compelling experience when touching iOS. And that sense of stiffness would be replaced with a much more fluid experience.

I like this idea. Apple Music’s new play button has a great touch-down state – I wish more parts of iOS followed the same approach.

Permalink

Google Updating AMP Pages with Easier Way to View, Copy Source URLs

A few months ago, I decided to remove Google AMP support from MacStories due to the obfuscation of our permalinks by the AMP plugin. There was a good discussion about publishers’ AMP concerns, including a story on The New York Times.

Today, Google has announced that they’re introducing a new feature that makes it easier to see a publisher’s full URL and copy it. Here’s Alex Fischer, writing on the Google Developers Blog:

Today, we’re adding a feature to the AMP integration in Google Search that allows users to access, copy, and share the canonical URL of an AMP document. But before diving deeper into the news, let’s take a step back to elaborate more on URLs in the AMP world and how they relate to the speed benefits of AMP.

And:

In addition to the above, many users have requested a way to access, copy, and share the canonical URL of a document. Today, we’re adding support for this functionality in form of an anchor button in the AMP Viewer header on Google Search. This feature allows users to use their browser’s native share functionality by long-tapping on the link that is displayed.

Google is also hoping that browsers will add support for a new Web Share API (which sounds nice as long as it can only be manually activated by the user; I can imagine websites abusing programmatic activation of the system share sheet).

I’m still not going to re-enable AMP in the short term, but I’m glad to see Google is listening to publishers and iterating quickly.

Permalink

Déxter

A couple of weeks ago, I picked up Pokémon Sun again and started playing where I left off in early December. While most of my friends with iOS devices are obsessed with Pokémon GO, I prefer the series’ traditional games for Nintendo consoles, and I find the latest generation of Pokémon games to be...



Member Requests

Question: I just started using your Toggl workflows after listening to you as well as Myke and CGP Grey. I like them so far but there is a problem I’m encountering where projects that I have deleted still show up in Workflow. They don’t show up in the web version or the Timer app. Have...


Canvas, Episode 28: Read Later Services

This week Fraser and Federico change gears and focus on Read Later services.

A different episode of Canvas this week – we talked about the best apps and services to save articles for later, including Apple’s own Reading List and some alternative power-user methods. You can listen here.

Sponsored by:

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

Fantastical 2.8 Brings Rich Notifications, iMessage Stickers

Rich notifications and stickers in Fantastical 2.8.

Rich notifications and stickers in Fantastical 2.8.

With a new version released today on the App Store, Flexibits updated Fantastical – the popular calendar client with natural language input – to include deeper support for iOS 10 and the iPhone 7. Version 2.8, available on the iPhone and iPad, adds new iMessage stickers using the app’s icon as the main character in different expressions, haptic feedback on the iPhone 7, and, more importantly, rich notifications for calendar events and reminders.

Read more


AutoSleep 3.0

I first reviewed AutoSleep by David Walsh in December, noting how his idea of an automatic watchOS sleep tracker could bring one of the best Fitbit features to the Apple Watch. I’ve been wearing my Watch to bed every night, and AutoSleep has successfully logged sleep data with impressive accuracy.

As I wrote in my original review, however, AutoSleep needed an easier setup process and a cleaner design to help users understand and edit logged data. Walsh has been working hard on AutoSleep since launch, and version 3.0, released today on the App Store, addresses several of my complaints from the original app.

The setup wizard has been completely redesigned with a series of questions that make it easy to configure the app for your habits. Instead of cramming information on a single page, Sleep Quality and Day now have their own tabs in the app; the Day section is particularly handy to view a timeline of your day as logged by sensors on the iPhone and Apple Watch. Generally speaking, everything feels cleaner and better organized, and while some menus and symbols could still be explained differently, the overall app is more intuitive and accurate in its measurements.

Thanks to the fantastic battery life of the Apple Watch Series 2, wearing the Watch at night for sleep tracking isn’t a problem, and AutoSleep makes automatic tracking a reality with features I can’t find in any other app. If you tried the app and abandoned it at version 1.0, now’s a good time to check it out again.

AutoSleep 3.0 is available on the App Store.


iOS 10.3 Beta Re-Introduces Warning for Old 32-Bit Apps, Suggests Future Incompatibility

Andrew Cunningham, writing for Ars Technica on a new warning that appears when running old 32-bit apps on the first beta of iOS 10.3:

Beta builds of iOS 10.3, the first of which was issued last week, generate warning messages when you try to run older 32-bit apps. The message, originally discovered by PSPDFKit CEO and app developer Peter Steinberger, warns that the apps “will not work with future versions of iOS” and that the app must be updated by its developer in order to continue running. The apps still run in iOS 10.3, but it seems likely that iOS 11 will drop support for them entirely.

Though the error message doesn’t explicitly mention the app’s 32-bit or 64-bit support, it’s definitely only older 32-bit apps that trigger the warning. Similar messages that did explicitly mention 64-bit support were present in the betas of iOS 10.0, but they were removed in the final release of the software. Apple has required 64-bit support for all new app submissions since February of 2015 and all app update submissions since June 2015, so any apps that are still throwing this error haven’t been touched by their developer in at least a year and a half (developers could add 64-bit support as early as 2013, but most of them opted not to until it became a requirement).

Note how, unlike the warning that was reinstated with iOS 10.1, this alert clearly states that “this app will not work with future versions of iOS” as opposed to “may slow down your iPhone”.

In my review of iOS 10, I had a couple of paragraphs on the warning that iOS displayed when launching a 32-bit app for the first time. The warning didn’t make it to the final version of iOS 10, so I didn’t cover it. I did, however, note that iOS 10 was accelerating the transition to 64-bit across the board.

Requiring apps to be compiled for 64-bit is going to introduce problems for software that is no longer maintained (especially classic iOS games), but Apple is moving toward cleaning up the App Store’s back catalog anyway. Enforcing the 64-bit requirement in iOS 11 wouldn’t be a complete surprise.

Permalink