I always knew that the [Workflow] gallery could be updated at any time, making Workflow Directory redundant. In fact, I have always hoped it would, which is why I’m not in the least bit sad or disappointed about this announcement. Like all workarounds, Workflow Directory was something I only considered as temporary. Now that the limitations the gallery have been addressed, there’s no further need for a workaround.
Earlier this week, my Apple Watch met an unfortunate end when I dropped it onto the kitchen floor. Sod’s law was in full effect as it landed face-down, shattering the glass instantly. This was less than a week after reading about Stephen Hackett’s own Apple Watch coming to a similar end.
Unlike Stephen, I (for reasons I still cannot fathom) had not purchased AppleCare+ for it. This meant replacing it at the Genius Bar would cost $199. Considering that the Series 1 starts at just $269 and is much faster, I decided to pay a little more and bought the Series 1 Space Gray 42mm at the West 14th Street Apple Store–this time with AppleCare.
Replacing an Apple Watch is, in theory, no different than transferring an Apple Watch from one iPhone to another. It should have been simple and straightforward. Unfortunately, and what is becoming a trend at Apple, that wasn’t the case. The process should have been as follows:
- Unpair the old Apple Watch from your iPhone, creating a backup in the process
- Pair the new Apple Watch to the iPhone
- When prompted, select the backup to restore from
What I actually had to do was reminiscent of a usability issue that once plagued iOS. A backup can only be restored to an Apple Watch that is running the same version OS (or earlier). While that isn’t necessarily an issue in itself, the way this is handled by the Watch app is kind of ridiculous.
Once I unpaired my damaged Apple Watch, I began the pairing process with the new one. When prompted to select a backup to restore from, the only options I had were a backup from September and one from last year. The backup from my just-unpaired Apple Watch was nowhere to be seen. Without any context, it simply appeared that the backup didn’t happen. Perhaps something had gone wrong during the unpairing process that prevented a backup from being made?
After a few expletive-filled minutes, I realized that this must be because my old watch was running watchOS 3.1, whereas the new one from the Apple Store was still running 3.0. I tested this by setting up my old watch again and restoring it from backup to see what options I had. As I had hoped, the recent backup did appear.
This backup ambiguity used to be a common issue in iOS and one that resulted in many headaches. If you backed up a device running a version of iOS that’s newer than the new device to restore to, you couldn’t restore a backup. Instead, you’d have to set up the device as new, update it, then restore it and try again. This isn’t the case anymore as it was finally fixed earlier this year and iOS now offers to update your device before doing anything else if it detects the backup was made with a newer version of iOS.
Alas, this doesn’t apply to the process of setting up an Apple Watch. In fact, there’s no information at all that you might need to update the watch before you can restore a newer backup. As far as the Watch app was concerned, I could either set up my watch as new or restore from one of the two older backups. Only after performing the following steps was I able to restore the recent backup to my new watch:
- Unpair the old Apple Watch from your iPhone, creating a backup in the process
- Pair the new Apple Watch to the iPhone
- Set up the watch as a new Apple Watch
- Go through all of the various confirmation screens
- Perform a software update
- Unpair the watch
- Pair the watch again, this time being able to restore from the recent backup
I worry about how many people have not been able to restore a recent backup to a new watch because their replacement watch wasn’t running the same software as the previous one. I only knew about this workaround because I’d experienced it before with iOS–and I’m an Apple nerd.
The watch is essentially a companion to the iPhone so there isn’t much data that the watch itself contains, but being able to restore from a backup is the best way to keep the disruption to a minimum. Considering how long it takes to set up, update, or unpair a watch, the whole process was an experience almost as painful as smashing the watch in the first place.
Because I’ve yet to find a set of Bluetooth headphones that reliably pair with my Apple Watch, I sometimes take my iPhone 7 with me when going for a run. I use an Incase armband that I originally purchased for my iPhone 6 which fits the iPhone 7 perfectly. Although the screen cover doesn’t interfere with taps and clicks, it also covers the Home button, rendering it useless.
While this isn’t too much of an issue because I still use my Apple Watch to track activity and control music playback, there are times when I need to do something on the iPhone. This means stopping, taking it out of the armband, and then unlocking it. As a workaround, I make use of AssistiveTouch to display an alternative Home button on the screen which I can use instead, avoiding the need to expose the iPhone and risk dropping it out of my sweaty hands.
AssistiveTouch is enabled in Settings > General > Accessibility > AssistiveTouch. For quicker access, the Accessibility Shortcut (also within the Accessibility settings) can be set to toggle AssistiveTouch so it can be enabled or disabled by triple-clicking the Home button.
This works great before, and after, a run. All I need to do is triple-click the Home button before I place the iPhone into the armband. Then, if I ever need to unlock the phone, I tap the on-screen Home button and unlock the iPhone with its PIN. Once I’ve finished a workout, I triple-click the button again to disable AssistiveTouch.
Workflow received another major update today, part of which drastically improves how workflows can be shared. The most notable change is the revamped Workflow Gallery. Until now, it always felt overlooked and didn’t seem to be updated with any regularity (which was one of the reasons I created Workflow Directory). By having a more user-orientated gallery with profiles and the ability to share more information with each workflow, it’s going to be much easier to discover and share workflows without needing to use a whole separate website.
Another feature that I’m excited about is that you can now specify import questions that are asked when a workflow is installed by another user. When setting an import question, Workflow asks the user to provide certain information that the workflow might need. This is especially useful with the recent API support so that you can make sure other users can easily provide their own API keys.
There are some additional changes to Workflow so you should check out Federico Viticci’s detailed coverage over at MacStories.
Although Workflow’s recently added support for API interaction, it’s already been possible to create workflows that interact with many online services already, albeit in a more basic way. Back in June, Workflow added support for IFTTT, a web automation service that makes it simple to connect hundreds of different services to each other.
IFTTT functionality within Workflow is something that I feel is too easily overlooked. I rarely see any workflows that make use of this integration, and even I don’t make much use of it. In fact, the only workflow at Workflow Directory that uses IFTTT is one that I wrote to demonstrate its functionality–a workflow that triggers an IFTTT recipe to call your phone and get you out of an awkward situation.
Workflow’s API support opens up so many possible uses but it can get really complicated very quickly. It’s worth keeping in mind that some of the functionality you’re looking to achieve could be done much more easily with IFTTT1. After spending some time exploring what’s possible, I’ve created some examples of IFTTT-powered workflows that demonstrate the usefulness of this action.
Post to Medium
Only a handful of iOS apps support posting to Medium, each of which has slightly different limitations or requirements. Using Workflow, it’s possible to send Markdown-formatted text from almost any app and post it to Medium. Thanks to IFTTT’s extensive Medium support, it’s also possible to specify tags, publication ID, and even a canonical URL if you’re cross-posting a piece you’ve published somewhere already. Interestingly, IFTTT’s support for Medium is actually better than most iOS apps that provide some sort of Medium integration.
This workflow, used as an action extension with any Markdown-formatted text, uses this IFTTT recipe to create a published post on Medium. The workflow prompts for a title, tags, and canonical URL (if required) during the process before it’s published. If you prefer, you can edit the recipe so that the post is unlisted or also added to a publication.
If you edit the recipe to have IFTTT create a draft post instead, tags are not included and need to be added when you edit the draft.
Create GitHub issue
I’ve covered using the GitHub API in Workflow before, but you don’t need to start delving into that if you just want an easy way to create GitHub issues. Using this workflow and IFTTT recipe, you can create an issue within the GitHub repository you specify. There’s also provides an option to include a photo or screenshot when creating the issue. To accommodate this, the workflow uploads it to Dropbox and gets a direct link to use within the issue description.
Subscribe to RSS feed in NewsBlur
This workflow makes me wish I had spent more time looking into Workflow’s support of IFTTT. I’d been looking into the NewsBlur API to create a workflow that subscribes to a site I provide, but this is something that I can do just by using IFTTT. This workflow makes use of this recipe and detects the RSS feed of a website, then passes it to NewsBlur to subscribe to.
There might even be services that you want to make use of which don’t have a public API but are available through IFTTT. ↩
Microsoft’s Cognitive Services (née Project Oxford) is an interesting collection of APIs that leverage machine learning to determine useful information about any provided data. One useful example of the APIs available is the Computer Vision API. It offers OCR functionality that detects any readable text within an image and outputs the results as plain text. Thanks to Workflow’s new API support, we can harness the power of machine learning to perform some very quick, and very accurate, text recognition.
This workflow prompts you to either select a photo or take one with the camera, then uses it to make an appropriate API request. The detected text is returned back and displayed as plain text that can be easily shared or copied to the clipboard.
Cool, right? Well it gets even better. The Computer Vision API can OCR images containing text in different languages so Workflow can also translate the detected text into our chosen language. The workflow includes a Translate Text action so you can try this for yourself.
This is really useful, especially when traveling. For instance, if you’re on vacation and are wondering what a street sign means, just run this workflow and take a photo, and you’ll get a translated version of the text.
Similar to other API services, an API key is needed to authenticate your requests. Just register for the service and copy/paste the appropriate subscription key for Computer Vision. There are also some size limits (both file and resolution) you need to consider so I recommend reading through the relevant documentation.
In what is most certainly an early Christmas present for people like myself, Workflow has just received one if its most significant updates-extensive support for making API requests. I can’t emphasize enough how useful this is and the impact it’s going to have when it comes to iOS automation.
Workflow’s “Get Contents of URL” action has been overhauled to provide support for GET, POST and PUT request methods, including custom header information. The action also features an easy-to-use way of creating a request body that handles the formatting and escaping of values automatically. This opens your workflows up to all kinds of interactions with many APIs, such as Stripe or GitHub.
To demonstrate just how powerful this revamped action can be, I’ve created a few example workflows that leverage some popular APIs. These examples don’t perform any sort of error handling, nor do they represent what the limits of Workflow are. Consider these workflows a starting point for building your own.
A word about API keys
Keep them secret, keep them safe.
– Gandalf the Grey hat
Interacting with an API almost always requires some sort of API key or token. This is usually a string of random characters that can be used to directly perform actions on behalf of your account. If someone were to obtain this, they can not only access your account information but also perform actions on your behalf.
If you create a workflow that you want to share, make sure to remove your API key from it beforehand!
GitHub: Create Gist
This is a workflow I’ve always wanted to create, and the new API support makes it possible. Gists are great to share small pieces of text information, such as code snippets or scripts. This action extension workflow accepts files of any type (though they must be text-based) and creates a gist using the GitHub API.
You need to create a GitHub personal access token before you can use this workflow. GitHub allows you to create multiple access tokens with different permissions. For the purpose of this workflow, I recommend creating a token that can only be used to work with gists.
Stripe: Get Recent Charges
Stripe is a payments platform that’s built for developers. This workflow retrieves some basic information about the last three charges processed on your Stripe account, such as:
- Charge ID
- Last four digits of the card used
To use this workflow yourself, include your test or live secret API key, depending on whether you want to retrieve test or live payment information.
Stripe: Create a Payment
This is an excellent demonstration of Workflow’s API support–use Workflow as a point-of-sale device! This workflow prompts you to enter credit card information and an amount to charge, along with some additional information, then creates a payment.
A notification is displayed once the payment has been processed and a link to the payment in your Stripe Dashboard is copied to the clipboard.
Stripe: Create a Customer
Moving on from creating payments, this workflow creates a customer object using the information you provide. A link to the customer object in your Stripe Dashboard is also copied to the clipboard.
Digital Ocean: Create Droplet
Digital Ocean is a cloud computing platform that makes it easy to deploy a server (droplet) in just a few seconds. Using its API, this workflow creates a new droplet using the information provided, such as the Linux distribution, how much RAM it should have, and the datacenter location.
Digital Ocean: Get Droplets Info
This workflow simply retrieves a list of all your current droplets and provides the following information for each:
- IP address
I only received my iPhone 7 yesterday so I’ve not been able to put the camera through its paces, though the few shots I’ve managed to take so far have been magnificent. The quality certainly isn’t close to my DxO One, but the iPhone 7 is far superior to my previous 6s Plus—especially in low-light conditions.
The first two photos, hosted at 500px, were edited using a combination of Photoshop Express, Pixelmator, and Snapseed1. While these have been edited, no attempts at noise reduction were made with the night shot of Manhattan. I’m very impressed with how well the iPhone 7 performs in low-light conditions.
The last photo, posted on Instagram, is unedited and unfiltered.
I’ve been editing photos entirely within iOS, using apps like these, ever since iCloud Photo Library was first made available. I can’t even remember the last time I opened Photos on my Mac, let alone edited a photo with it. ↩
There are two Macs in our home using Time Machine to back up to a 1TB USB hard drive connected an AirPort Extreme 802.11ac. After the painful process of changing the country of my iTunes Store account when I moved to the US, I was forced to keep a local copy of all the movies and TV shows I had purchased. This is backed up as well, so the 1TB drive began to run out of space.
The drive would soon need to be replaced with something bigger, so I purchased a 2TB Seagate Expansion portable hard drive. However, I didn’t want to just swap the drive connected to the AirPort Extreme and start backing up the Macs from scratch–I wanted to retain the existing backup history1. The AirPort Extreme’s Time Machine support has had a spotty history so I was a little wary about whether it was even possible to even do.
After a search online didn’t yield any meaningful results, I decided to wing it and see if I could just plug both drives into my Mac. Turns out, this works perfectly. Here’s what I did:
- Make sure both the USB disk attached to the AirPort Extreme was not mounted on either Mac
- Disconnect the USB drive from the AirPort Extreme
- Connected the new USB drive to the Mac and created a single HFS+ volume named Time Machine (this is the same name as the existing USB drive)
- Connected the old USB drive to the Mac, then copied the disk images to the new drive
Both drives, along with my MacBook Pro, are equipped with USB 3.0, so I left the Mac for a few hours to copy 800GB between the drives while I ran some errands. Once this was finished, I then connected the new USB drive to the AirPort Extreme and restarted the base station2.
After the AirPort Extreme powered back up, I started a Time Machine backup on my Mac. The backup worked flawlessly, creating an incremental backup and not, as Time Machine does when it thinks something is amiss, start an entirely new one. I could also view, and restore from, any part of the Time Machine backup history.
I’ve owned a variery of cameras over the last ten years, from bulky DSLRs like the Nikon D50 to the much more pocketable Sony NEX-3N, but I’ve never enjoyed carrying a separate camera around. It was always another device to carry, something else to remember to bring. For the last couple of years, the only camera I’ve been using is an iPhone.
After moving to the U.S. earlier this year, I’ve been tempted by the thought of a dedicated camera to take better shots than the iPhone is capable of, especially in low light. However, I still didn’t want something else to carry. With that in mind, I decided to purchase the $479 DxO One after reading some favorable reviews.
The DxO One isn’t like any other digital camera–it has a built-in Lightning connector and is designed as a a companion for the iPhone or iPad. Since most of the typical camera functions are offloaded to the iOS device and companion app, the unit itself is extremely small and feels more like a tiny battery pack than a fully-fledged camera.
When the camera is connected to an iPhone using the Lightning connector, the appearance of the two is reminiscent of one of the first digital cameras from Casio. It can also pivot around 60 degrees in either direction. The DxO One has a 1-Inch 20.2MP sensor, the same one found in the popular Sony RX100 III, and a 32mm equivalent fixed lens with a maximum aperture of f/1.8. There’s full support for PASM modes, and the camera even shoots RAW. There’s even microSD card slot to save these to, though JPEGs are automatically synced to the iPhone1.
After using the DxO One for a week, I’ve been completely blown away with the quality of the shots it produces, especially in low light. It even works with a Bluetooth remote camera button I bought for less than $20 to use with my iPhone, so long exposures are super-easy to perform. Here are a few examples from my 500px gallery, edited using Adobe Photoshop Express (click through to view more detailed information about the camera settings for each photo):
The DxO One certainly isn’t cheap and there are many point and shoot cameras that offer more functionality for less money. There’s no optical zoom and it’s video recording capabilities are overshadowed by the 4K support the iPhone offers. But there’s no other camera that works as seamlessly with the iPhone as this. The DxO One’s portability, ease of use, and regular feature updates makes it one of the best cameras I’ve ever had2, and it’s perfect for my needs. It’s so small and light that there’s never a question about whether I want take it somewhere–it just comes with me.
DxO have recently announced a range of new accessories for the DxO One, such as a waterproof casing and optical adapter, further expanding its functionality. If you use an iPhone and want to take higher quality photos but, like me, don’t want to carry a whole other camera around, I urge you to check out the DxO One.
- Dec 2016
- Nov 2016
- Oct 2016
- Sep 2016
- Aug 2016
- Jul 2016
- Jun 2016
- May 2016
- Apr 2016
- Mar 2016
- Feb 2016
- Jan 2016
- Dec 2015
- Oct 2015
- Sep 2015
- Jul 2015
- Jun 2015
- Apr 2015
- Mar 2015
- Jan 2015
- Aug 2014
- Jun 2014
- May 2014
- Apr 2014
- Mar 2014
- Feb 2014
- Jan 2014
- Dec 2013
- Nov 2013
- Oct 2013
- Sep 2013
- Aug 2013
- Jul 2013
- Jun 2013
- May 2013
- Apr 2013
- Mar 2013
- Feb 2013
- Jan 2013
- Dec 2012
- Nov 2012
- Oct 2012
- Sep 2012
- Aug 2012