This week's sponsor

iPhone Backup Extractor

Recover Lost or Deleted Messages, Photos & More


Search results for "workflow"

My Markdown Writing and Collaboration Workflow, Powered by Working Copy 3.6, iCloud Drive, and GitHub

For the past couple of years, I (and the rest of the MacStories team) have used Working Copy to store and collaborate on Markdown drafts for our articles. As I explained in a story from late 2016, even though Working Copy is a Git client primarily designed for programmers, it is possible to leverage the app's capabilities to perform version control for plain text too. Each MacStories team member has a private GitHub repository where we store Markdown files of our articles; in the same repository, other writers can make edits to drafts and commit them to GitHub; this way, the author can then pull back the edited file and use Working Copy's built-in diff tool to see what's changed from the last version of the file and read comments left by whoever edited the draft.1

As I mentioned two years ago, this system takes a while to get used to: GitHub has a bit of overhead in terms of understanding the correct terminology for different aspects of its file management workflow, but Working Copy makes it easier by abstracting much of the complexity involved with committing files, pushing them, and comparing them. This system has never failed us in over two years, and it has saved us dozens of hours we would have otherwise spent exchanging revised versions of our drafts and finding changes in them. With Working Copy, we can use the text editors we each prefer and, as long as we overwrite the original copies of our drafts and keep track of commits, the app will take care of merging everything and displaying differences between versions. From a collaboration standpoint, using Working Copy and GitHub for file storage and version control has been one of the best decisions I made in recent years.

Read more


The Mac Pro Is Coming in 2019, Shaped by Apple’s New Pro Workflow Team

In a follow up of sorts to last year's Mac roundtable, Matthew Panazarino of TechCrunch was invited back to Apple HQ for an update on the long-awaited Mac Pro, which Apple shared will not launch until 2019:

“We want to be transparent and communicate openly with our pro community so we want them to know that the Mac Pro is a 2019 product. It’s not something for this year.”

Other than the 2019 date, the lone detail about the new Mac Pro was confirmation that it will be a modular system. Though what exactly that means, we still don't know.

The other main interesting note from Panzarino's report is that Apple has assembled a new internal Pro Workflow Team (not to be confused with the iOS app Workflow) which aims to guide and improve Apple's pro-targeted products. The team is under the oversight of John Ternus, Apple's VP of Hardware Engineering, and a great deal of its focus is learning the workflows of real pro users so it can optimize its hardware and software to make those workflows better. Panzarino writes:

To do that, Ternus says, they want their architects sitting with real customers to understand their actual flow and to see what they’re doing in real time. The challenge with that, unfortunately, is that though customers are typically very responsive when Apple comes calling, it’s not always easy to get what they want because they may be using proprietary content. John Powell, for instance, is a long-time logic user and he’s doing the new Star Wars Han Solo standalone flick. As you can imagine, taking those unreleased and highly secret compositions to Apple to play with them on their machines can be a sticking point.

So Apple decided to go a step further and just begin hiring these creatives directly into Apple. Some of them on a contract basis but many full time as well. These are award-winning artists and technicians that are brought in to shoot real projects (I saw a bunch of them walking by in Apple park toting kit for an outdoor shoot on premises while walking). They then put the hardware and software through their paces and point out sticking points that could cause frustration and friction among pro users.

This work has started in the specific areas of visual effects, video editing, 3D animation, and music production, and Apple plans to expand it out from there.

The efforts of the Pro Workflow Team serve to benefit all of Apple's pro-related hardware and software, and even popular third-party software as well. It's one way Apple is showing its commitment to serving professional users.

In the last year, Apple's output for pro users seems to have made a complete turnaround. Back then we were wondering if the company had become content focusing on the average consumer and letting pros leave for other platforms. That's certainly not the story anymore. With the iMac Pro, continued updates to Apple's pro software, and now the forthcoming Mac Pro and the ongoing investment of the Pro Workflow Team, Apple is positioning itself again as a company committed to serving the pro market.

Permalink

How to Adjust iOS’ Volume via Workflow When Streaming Audio to HomePod

One of Workflow's least known functionalities is its ability to get details about the hardware it's running on and control some system features. Among these, Workflow can both retrieve an iOS device's current volume level and set the volume. A few days ago, I realized I could make a workflow to quickly adjust my iPhone's volume when streaming music to one of our HomePods. Unlike other automations I've crafted over the years, this workflow was quite a success in our household and I felt like it was worth sharing with the wider MacStories audience.

Read more


Workflow 1.7.8 Adds ‘Mask Image’ Action, Things Automation Support, PDF Text Extraction, and More

In the first update since November 2017, Apple today released version 1.7.8 of Workflow, the powerful iOS automation app they acquired last year. The latest version, which is now available on the App Store, introduces a brand new Mask Image action, adds support for Things' automation features, and improves the ability to extract text from PDFs using the company's PDFKit framework, launched in iOS 11. While the unassuming version number may suggest a relatively minor update, Workflow 1.7.8 actually comes with a variety of noteworthy changes for heavy users of the app.

Read more


Things Automation: Building a “Natural Language” Parser in Workflow

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.

Read more




Workflow Update Restores Google Chrome and Pocket Actions, Extends Apple Music Integration

In the first update following Apple's acquisition in late March – and despite rumors that claimed the app would no longer be supported – Workflow has today restored some of the features that were removed in version 1.7.3 of the app (which was released when Apple confirmed the acquisition) and has brought a variety of changes and improvements, including new Apple Music actions.

Read more


The Future of Workflow

I've loved Workflow since the first beta I was sent in August 2014. Workflow is my most-used iOS app of all time, and, in many ways, it is the reason my iPad Pro can be my primary computer. I've written thousands of words on the app and have created hundreds of workflows for myself and others over the course of two years.

I referred to Workflow as Minecraft for iOS productivity and the modern bicycle for the mind in the past. I stand by those analogies. There's nothing else on iOS like Workflow, which deftly walked the fine line between absurd innovation and Apple rejections with a bold vision and technical prowess. Workflow embraced the limitations of iOS and turned them into strengths, resulting in a power-user app with no competition. After two years, no app gets remotely close to the automation features shipped by the Workflow team.

And now Workflow and its creators are going to be part of Apple and the company's bigger (and more secretive) plans.

Somewhere in the back of my mind, I had always kept the possibility that Workflow could eventually be discontinued or acquired. In a somewhat prescient move, Stephen quizzed me on this problem a few weeks ago on Connected. My "worst-case scenario" of Workflow going away became the new reality of iOS automation last week.

Workflow as an app is an incredibly good acquisition for Apple, but there's a deeper subtext here. Workflow represents a movement from a large number of users who enjoy working from iOS devices so much, they want to optimize the experience as much as possible. Workflow's goal wasn't to merely provide a capable alternative to the Mac's AppleScript and Automator; Workflow wanted to eclipse legacy scripting environments and usher iOS users into a new era of mobile automation. There's the Workflow app and team – technically impressive and absolutely talented – and there's the bigger theme behind Workflow.

But what has Apple acquired, exactly? Under Apple's control, can Workflow continue on its mission to make automation accessible for everyone? If Apple sees a future in iOS automation powered by Workflow, what else can be done with a virtually infinite budget and stronger ties to the platform? And what does this acquisition mean for Apple's commitment to pro users on iOS?

I've been mulling over these questions for the past week. I don't have any absolute answers at this point, but, after building workflows and following the app's development for two years, I have some ideas on where Workflow can go next.

Below, you'll find two possible scenarios for Workflow as an Apple app, as well as some considerations on how Apple could evolve Workflow into a native feature of iOS devices and a new developer platform.

Read more