One of my favorite features of Workflow was its ability to share workflows as files. It was this functionality that made it possible for me to start Workflow Directory and create my own GitHub repository of workflows. Unfortunately, Shortcuts doesn’t support this functionality and I suspect it never will again.
Although it’s possible to jump through some hoops to import workflow or shortcut files, lack of file support makes it impossible to maintain my GitHub repository. Instead, I’ve started the long overdue process of creating iCloud links to my shortcuts and publishing them here instead.
All of my shortcuts are being made available on my site and can be found at a dedicated Shortcuts page. Although I’ve written about some of them in more detail, there are plenty of shortcuts I’ve never blogged about. I will publish any shortcuts I think are useful and continue to write about some of them in more detail.
I’m also using this opportunity to clean up my shortcuts, fix any broken ones, and remove any that are no longer functional. I’ve already gone through my blog posts to update them all with iCloud links and have identified a few that rely on APIs or functionality that’s no longer available (e.g., all my IFTTT-based workflows can’t be used anymore).
The Personal Automations feature of Shortcuts makes it possible to run actions automatically whenever a supported event is triggered. I recently purchased a new car that supports CarPlay so I’ve been working on some automated shortcuts that run whenever CarPlay is connected or disconnected. In particular, I’ve been creating automations that can help make driving safer.
In 2019, 52 children in the United States died of vehicular heatstroke. These preventable deaths mostly occurred when a parent or caregiver accidentally forgot there was a child in the car. It’s a tragic loss whenever this happens and, as a driver and a father to a young child (who is still in a rear-facing child seat), is a hazard that’s always in the back of my mind. Some car manufacturers have started to add technology to help prevent this from happening but it’ll be some time before this is standard in every family car.
Rear Occupant Alert is a shortcut I’ve created that reminds a driver to check for rear occupants (not just children, pets too) whenever CarPlay is disconnected—this most commonly occurs at the end of a journey. When this happens, the shortcut plays an alert sound at maximum volume, vibrates three times, and displays a notification to remind the driver to check for rear passengers.
The shortcut performs some additional steps but doesn’t contain any complex logic like if statements or repeat blocks. It turns off Do Not Disturb (in case it wasn’t already turned off), sets the iPhone volume to maximum, then runs the alert process.
The Play Sound action in Shortcuts ignores the status of silent mode so there’s always an audible alert when the action is run. To prevent any unexpected loudness after the shortcut has run, it gets the current volume before changing it to 100% and then sets it back.
Since personal automations can’t be shared, you can download this shortcut and create an automation that uses the Run Shortcut action. To use Rear Occupant Alert:
Create a new Personal Automation that’s triggered whenever CarPlay disconnects.
Add the Run Shortcut action and select the Rear Occupant Alert shortcut.
Uncheck Ask Before Running so the shortcut can run without confirmation.
If you use this shortcut, please remember that it is not a replacement for common sense. It may provide a helpful reminder but you shouldn’t rely on it to remember that you need to check your car. There are plenty of reasons why this shortcut might not run at all; you could forget to connect your iPhone or Shortcuts has crashed and is not responding. Nothing replaces common sense and developing the habit to check every time you exit your vehicle. An reminder, however, can be helpful.
I’ve been having some troublesome sync issues with Shortcuts since upgrading to iOS 13. None of my devices would stay in sync and shortcuts I’d delete would reappear moments later. In some cases, shortcuts would even be duplicated.
A helpful tip on the Shortcuts subreddit has provided a simple solution for my syncing woes: delete the app and reinstall it. I did this on each of my devices and now shortcuts sync perfectly.
My iPhone photography workflow includes sharing some of the photos I’ve taken to Instagram. I usually include relevant hashtags to increase discoverability and have a collection of frequently used hashtag sets—different hashtags for the same topic—that I can choose from. I also include a five-dot prefix (each dot on a separate line) to separate the photo’s caption text and hashtags. This is a commonly used method for hiding hashtags “below the fold” so they’re only visible when tapping the more button.
I’ve used a few different methods for managing my hashtag collection and wanted to share my experiences with each.
iOS text replacement
iOS has built-in text substitution that can be used to replace a shortcut with a longer piece of text. For example, a shortcut of ,,iphone could be replaced with #shotoniphone #iphonexs #iphonephotography.
Text replacement is a good option if you occasionally use hashtag sets. You can easily add them to an Instagram caption without leaving the app. It’s basic organization and need for you to remember what shortcuts you’ve created isn’t well suited for more frequent users or those with a larger collection.
Copied is a clipboard manager app for iOS and was the first standalone app I used for managing hashtag sets. Each set can be saved a separate clipping and accessed directly from Instagram using Copied’s custom keyboard.
Clippings can be organized into lists and the custom keyboard also includes a built-in search, both of which make Copied useful if you have a lot of hashtag sets.
The popular iOS photo editor has built-in support for hashtag set management. Darkroom makes it easy to manage and create new hashtag sets and provides some useful ways of accessing them.
Hashtag sets can be selected and copied to the clipboard—along with an optional five-dot prefix—as part of the photo export flow so that you can switch to Instagram and simply paste the hashtags in. You can also use Darkroom’s Today View widget to select and copy hashtag sets to the clipboard.
The app also supports Siri shortcuts for quick access to hashtag sets. You can select which hashtag sets to include and then record a phrase to use with Siri. Once invoked, the hashtag sets are copied to the clipboard.
My preferred method for managing hashtag sets nowadays is, unsurprisingly, with a shortcut. I created Instagram Hashtag Sets to manage my hashtag collection and use them whenever I post a photo to Instagram. The shortcut is more flexible than other methods I’ve tried and also includes some additional functionality.
It can be run as a normal shortcut or from the Share Sheet, the Shortcuts Widget, the Home screen, or as a Siri Shortcut. I primarily use the Share Sheet by selecting the caption text I’ve specified and tapping Share; the shortcut includes the caption text when it copies hashtags to the clipboard to make it easier to simply paste it over the existing text.
The shortcut contains a dictionary of my hashtag sets, each of which is an array of hashtags. When run, it displays a list of these hashtag sets for you to select from. All of the chosen hashtags are copied to the clipboard, after which it switches back to Instagram and displays a notification. The shortcut also includes support for a five-dot prefix and includes this if the option is enabled.
Instagram limits the number of hashtags per photo to 30. The shortcut counts how many hashtags have been included across all hashtag sets and allows you to deselect individual hashtags if there are more than 30. The shortcut also repeats the check until there are 30 or fewer hashtags.
Shortcuts no longer supports shortcut file imports. Any links to shortcuts in this post have been updated to use iCloud links.
I last updated my shortcut for creating device-framed screenshots in December 2017 by adding support for iPhone X. I’ve been meaning to add more device frames for a while now but, since becoming a father six months ago, free time has been a precious commodity.
In the meantime, Federico Viticci released his impressive Apple Frames shortcut which does a fantastic job at framing screenshots for different devices. I still wanted to update my shortcut though it now seemed redundant to simply add more frames. Instead, I decided to start from scratch and approach the concept of screenshot framing differently.
My original shortcut, like Federico’s, makes use of Apple’s marketing product images—high-resolution images of devices for use in marketing or promotional material—that are ideal for screenshot framing. However, there’s no variety in what’s available, only flat images of devices and usually in Space Gray.
Instead of framing screenshots using just these images, I wanted to create mockups using different product images that are more distinctive and, in some cases, three-dimensional. The result is Mocktail, a shortcut that creates framed iOS screenshots using various device images I’ve sourced from Apple’s website (e.g., product landing pages or the online store). Where necessary, Mocktail applies perspective distortion to screenshots using Cloudinary, an online image manipulation API.
Mocktail creates mockups for the following devices:
Notably absent is the iPhone XR. There aren’t yet any usable images of the device to create mockups with (the only ones I could find aren’t a high enough resolution) nor has Apple created a product marketing image for it. I hope to support the iPhone XR sometime in the future.
Using the shortcut
Mocktail can be run as a normal shortcut, accepts images from the share sheet2, or using drag-and-drop, and performs the following steps:
Checks if any images were shared to the shortcut via the share sheet (or using drag-and-drop). If not, the shortcut displays a list of recent screenshots for you to select from. Multiple images can be shared to create a batch of mockups all at once.
Checks that the required base images are available in iCloud Drive. If not (i.e., the shortcut is run for the first time), they are automatically downloaded and saved3. The shortcut then continues.
Calculates the pixel count of the screenshot by multiplying its width and height. This is used to determine what device the screenshot was taken on.
Determines the orientation of the screenshot (either landscape or portrait).
Using the device information and orientation, the shortcut displays a list of suitable base images for you to select from.
Applies rounded corners if the device requires it (e.g., iPad Pro or iPhone XS). For iPhone XS and XS Max, a notch is also added to the screenshot.
For flat base images, the screenshot is overlaid onto the base image. For three-dimensional base images, Mocktail uses Cloudinary to apply perspective distortion to the screenshot, then overlays it onto the base image.
Certain base images have a significant amount of white space. Where necessary, the shortcut crops the completed mockup.
The completed mockup is saved to iCloud Drive. Each mockup is saved in a folder corresponding to the name of the device, such as /Shortcuts/Mocktail/iPhone XS Max.
Distorting images with Cloudinary
Mocktail uses Cloudinary’s upload and image manipulation APIs to apply perspective distortion to screenshots. You need to create a free Cloudinary account to use Mocktail. The free pricing tier is more than sufficient as you would need to run this shortcut several thousand times a month before you would exceed the free plan.
When you first launch the shortcut, it asks you to provide the following information about your Cloudinary account which can be found in the Dashboard:
Username (your Cloudinary “cloud name”, not email address)
By default, Cloudinary requires uploads to be signed with the account’s secret key. Mocktail doesn’t do this so you need to enable unsigned uploads and specify the upload preset in the shortcut. This randomly generated value is used to upload images without needing to sign them4.
Once you have provided your Cloudinary details, you can begin using Mocktail to generate mockups.
Mocktail is one of the most complex shortcuts I’ve created and it makes extensive use of dictionaries to store information. To figure out how screenshots should be distorted, I used Affinity Photo to draw lines along the sides of the display. I then added horizontal and vertical guides at the location where these lines intersected, providing me with the necessary X,Y coordinates required by Cloudinary.
Mocktail is available from my GitHub repository of shortcuts. I prefer not to use iCloud links when sharing shortcuts because of they’re one-time use limitation. Rather than generate a new link every time I update the shortcut, I can push an update to GitHub and the existing link still works (there’s also the usual benefits of using a version control system).
Both iPad and iPad mini are the same resolution so iPad mini screenshots are handled as iPad screenshots—there are no iPad mini-specific base images. ↩
At the time of writing, the current version of Shortcuts—2.1.3—has a bug that can prevent image-based action extension shortcuts from working. If Mocktail doesn’t work from the share sheet, run it from within the app. iPad users can also drag-and-drop images into the shortcut. ↩
Federico cleverly uses Base64 encoding to store all images as text within his shortcut. I decided against a similar method because it seemed to severely impact the performance of Shortcuts. Instead, the base images are made available as a ZIP file in my repository that the shortcut downloads and extracts. ↩
Signing uploads would have been a more significant undertaking. I don’t think it’s necessary considering the use case. ↩
BBC 6 Music has a fascinating and nostalgic two-part series on the history of video game music. There’s also a bonus episode with Charlie Brooker, creator of Black Mirror and former video games journalist, talking about his love of video games and sharing some of his favorite game music.
Our two-month-old daughter is formula fed. My wife and I prepare a batch of bottles every day using this formula mixing pitcher so they’re readily available at feeding time. Some arithmetic is needed to work out how much formula powder to add to a certain volume of water, and the amount of formula we need to prepare steadily increases as she grows. To give our sleep-deprived brains a break and avoid any miscalculations, I created some shortcuts to help out and do the math for us.
Formula Calculator works out how much formula we should prepare for the day, based on our daughter’s current weight (in pounds and ounces). The general rule of thumb for babies up to six months old is to offer 2.5 ounces of formula per pound of body weight in a 24 hour period. Her weight is entered when running the shortcut, along with how many feeding sessions to expect that day 1. The amount of formula to prepare, along with how much to fill each bottle with, is then displayed.
This next shortcut, Formula Prep, is the one I use the most. It calculates how much formula powder to add to a specified amount of water. Most formula powder in the US specifies one scoop (8.7g) of powder for every 2 fluid ounces of water. I specify how much water is in the pitcher and it calculates the amount formula powder to add—both in grams and scoops. I prefer to measure by weight as it’s all too easy to lose count of the scoops being added.
Prepared formula can be stored in the refrigerator for up to 24 hours. After that, it must be discarded. Formula Reminder is a shortcut I run once I’ve prepared formula that creates a reminder with an alarm set 24 hours later.
The number of feeding sessions can vary from day to day. We’ve been tracking our daughter’s feeds since birth and she’s currently averaging about six sessions per day. ↩
Moment is discounting all of their lenses, cases, and accessories by 20% and offering $5 shipping worldwide for the next three days when you use the code 72HOURSALE during checkout. Moment’s lenses are a core part of my iPhone photography kit and I highly recommend them.
Here are a few photos I’ve taken with Moment lenses:
If you’re thinking about getting started with Moment lenses, I recommend picking up the Wide lens first. It’s a versatile lens you’ll get a lot of use from and the one I like to use the most. You’ll also need one of their photo cases for your phone—this is what the lenses attach to.
For iPhone X and Xs users1, there’s also a battery photo case with built-in shutter button. When used with Moment’s iOS camera app, the button supports half-press to focus. If you prefer to use any other camera app, it operates the same as a volume button to trigger the shutter.
Moment’s camera app has some advanced features, such as manual controls, and can also shoot in RAW. If you’re a stickler for EXIF data, you can select the Moment lens you’re using and the app embeds the information within the photo’s metadata.
The case is MFi certified for iPhone X, though iPhone Xs certification is still pending. I use the battery photo case with an iPhone Xs and it works fine, and it’s expected that the case be certified in the near future. ↩
Shortcuts no longer supports shortcut file imports. Any links to shortcuts in this post have been updated to use iCloud links.
I often post photos to Instagram or Unsplash. Now that I’m using my website for microblogging, I’ve started publishing my photos here as well. I’ll have more ownership over the content and, should either of these services ever go away, my photos will still be available.
I’ve also imported into my website a copy of all the photos I’ve posted to Instagram–about 1,200 photos spanning almost eight years. To do this, I requested an archive of all my Instagram data, copied the photos to my site, and generated all of the posts using Shortcuts.
The ZIP archive provided by Instagram contains a copy of everything uploaded, along with JSON files containing data about each post, comment, like, and more. While the archive contains all of this data, I was only interested in the photos.
Extracting the photos
The archive’s photos/ directory is neatly structured, with all photos organized into subdirectories using a YYYYMM date format (e.g., 201804/). The media.json file contains a photos dictionary, where each item contains information about each photo1:
path: The relative path to the photo.
location: The location the photo was tagged with. This is blank if no location was specified.
taken_at: The date the photo was posted.
caption: The caption of that photo. Similar to location, this is blank if no caption was included.
The first step was to import all the photos into the media/ directory of my website. I extracted the archive using Documents on my iPad , then created a new ZIP file containing just the photos/ directory. I opened this in Working Copy and extracted this new archive into my website’s git repository. After committing and pushing the changes, all of those photos were live and available to link to.
Creating the posts
Next, I copied media.json to iCloud Drive, then used Shortcuts (née Workflow) to create this shortcut that performs the following actions:
Loops through every item within the media.json file’s photos dictionary.
Gets the value for each item’s path, location, taken_at, and caption.
Creates a text file for each photo with the required Jekyll front matter using the values retrieved above, and sets the category to photo. The caption, if available, is included in the post.
Sets an appropriate name for the text file, based on the date information from taken_at.
Creates a ZIP file of all the text files that have been generated.
This is an example of a text file that the shortcut generates:
---layout: microblogpostcategory: photodate: '2018-09-02T14:54:40'title: ''slug: '18090212145440'mf-photo: - https://www.jordanmerrick.com/wp-content/uploads/2018/11/e22680154ef0b993e870789b69764673.jpg---I love Central Park...
The photo URL is included in mf-photo as I’m using the same template I use for microblog posts, and that field was established when I set up the Micropub to GitHub service I use. You can easily change this to whatever you need.
Once complete, I opened the archive in Working Copy and extracted it into my site’s microblog/_posts/ directory.
Making changes to my Jekyll template
With my photos imported, I made a few small tweaks to my Jekyll template files. My microblog archive page displays a 10-word excerpt of the micropost’s text and uses it as the post’s link. However, many of my photos had no caption. As a result, there was no text to create an excerpt from, so Jekyll was skipping them and they weren’t being listed.
To make sure all my photos were listed on my archive page—and distinguish between plain text and photo posts—I added an emoji icon for any microblog posts that have the photo category set. I also edited the template for individual microblog posts to display the location information (along with the emoji pushpin symbol), if available.
Finally, I created additional JSON and RSS feeds that only include microblog posts with photos.
Instagram treats posts with multiple photos as separate posts in the data archive. That was fine for me, as I’ve used only that feature maybe two or three times. ↩