An Interview with Harry Nesbitt and Ryan Cash About Alto’s Odyssey 
Federico and John interview two members of Team Alto, Harry Nesbitt and Ryan Cash, about Alto’s Adventure, the challenges they faced in following it up with Alto’s Odyssey, the creative process of making games, and the mobile game industry.
iPads Around the World For the second installment of our iPads Around the World section, we’ve talked to Alexander Drechsel and Josh Goldsmith, two interpreters who, besides interpreting for the European Parliament and other large institutions, also train their colleagues on how to use iPads while interpreting. Alex and Josh were among the first Club members to get...
One of the Todoist features I miss the most as a Things user is the service’s natural language parser. Available in the Quick Add field of Todoist for iOS, web, and macOS, this feature is, effectively, Fantastical for tasks. Instead of having to manually select task fields such as projects, tags, or dates, you can take advantage of an easy-to-remember syntax and quickly type them out. As you do that, Todoist will highlight the parts it understands in red, indicating that it knows how to parse them. I entered hundreds of tasks in Todoist using this system, and I think it’s an aspect of task creation that every other task manager should implement as well. It makes perfect sense, and it saves a lot of time.
Aside from a half-baked attempt at supporting natural language entry in its date assignment UI, Things doesn’t unfortunately offer a quick entry feature comparable to Todoist’s. So, of course, I set out to make my own using the app’s latest automation features.
Well, kind of. For starters, as much as I’d love to, automation doesn’t mean I can make my own interfaces in Things, supplementing the app with my custom UI to more easily create tasks. Things’ new URL scheme only lets us send data from other apps such as Workflow or Drafts. More importantly though, the workflow I’m sharing today isn’t based on a complex natural language engine such as the one used by Todoist or, say, the Chrono JS parser; I’m just using some special characters sprinkled with some delicious regex to make sure Workflow knows what constitutes a task title, a project, or a due date. Thus the quoted “natural language” in the headline of this story: it’s only natural as long as you don’t forego the special syntax required to make the workflow run.
That said, I’m quite happy with how this workflow lets me add multiple tasks to Things at once. I’ve been finding it especially useful at the end of the work day or during my weekly review, when I make a list of all the things I’m supposed to do next and want an easy way to add them all to Things. For this reason, rather than restricting this workflow to Club MacStories members, I thought every MacStories reader could benefit from it and modify it to their needs.
If you’re a Club member, you can still look forward to advanced Things workflows over the next few issues of MacStories Weekly; this one, however, has been too useful for me not to share with everyone.
Federico and Myke slander Stephen’s good name before talking about iPhone and headphone rumors and Amazon’s acquisition of Ring.
Also on this week’s episode of Connected: a discussion about the long-term impact of Apple’s Beats acquisition and the company’s approach to an increasingly growing ecosystem of smart devices. You can listen here.
Sponsored by:
Marco Arment (who’s been struggling with Watch app development for a while now) makes the case for WatchKit to be either discontinued or substantially expanded as, in its current form, it hinders the creation of more powerful apps.
Developing Apple Watch apps is extremely frustrating and limited for one big reason: unlike on iOS, Apple doesn’t give app developers access to the same watchOS frameworks that they use on Apple Watch.
Instead, we’re only allowed to use WatchKit, a baby UI framework that would’ve seemed rudimentary to developers even in the 1990s. But unlike the iPhone’s web apps, WatchKit doesn’t appear to be a stopgap — it seems to be Apple’s long-term solution to third-party app development on the Apple Watch.
When I first read his post, I thought that asking Apple to discontinue and replace WatchKit was perhaps too much. But after spending some time reorganizing my Watch favorites and complications last night and this morning, I agree with Marco. My favorite apps on the Watch are all made by Apple and are not based on WatchKit. The only exception is Workouts++ (which, as a workout app, has specific privileges). The only third-party Watch apps I regularly use besides Smith’s app are Things and Shazam (which is somewhat ironic) and they’re both accessed via complications; they’re okay, but I don’t love them because they’re often slow to sync data with their iPhone counterparts or take too long to launch and be in a usable state. When I’m out and about, I still don’t trust Watch apps to be as reliable as iPhone apps.
Despite three years of watchOS updates and more powerful hardware (I use a Series 3), the Apple Watch still doesn’t feel like the rich, diverse, and vibrant app platform that the iPhone is. Some might say that’s precisely the point – it doesn’t have to be because the Watch works best through notifications and complications. However, I often ask myself if such argument is the wearable equivalent of Aesop’s sour grapes – real Watch apps wouldn’t make sense anyway. Like Marco, I wonder what would happen if only Apple exposed real watchOS development tools to app makers.
App Culture: Mindfulness and Meditation Apps
A Richer Save Menu for Things Earlier this week, I published my in-depth look at Things’ new automation features, which revolve around a powerful URL scheme that now allows you to integrate Things with other iOS apps. As I mentioned in the story, I wanted to provide Club members with more advanced examples to showcase what can be built once...
iMore’s Serenity Caldwell and Luke Filipowicz put together a great Q&A with Team Alto to discuss the making of Alto’s Odyssey.
Here’s my favorite bit, which only adds to my love for this game:
One of the big breaks in the new game’s theming came from the lives of Team Alto’s members themselves. “Things really clicked when we reflected as a group on how much our lives had changed since the release of Alto’s Adventure,” wrote Cymet. “The team had grown, some of us had moved away from the homes we knew to live in other places, and we had all experienced big personal upheaval in different ways.
“What we arrived at was a desire to capture the feeling of going outside your comfort zone, exploring the unfamiliar, and accepting that the concept of ‘home’ is related to the people close to you, not any one place. In many ways, this is what led us to the grandeur of Alto’s Odyssey’s setting. This idea of a fantastical place far from what you know as home, where you learn to see the beauty in embracing the unknown.”
Federico has a surprise for the group, then goes on to teach about Things 3 before Stephen complains about its repeating task support. In a shocking turn of events, Myke has the need for a Mac app.
I had a lot of fun on this week’s episode of Connected. You don’t want to miss the surprise I’d been keeping from the group. You can listen here.
Sponsored by:
John