I know a couple of friends who have disabled iMessage in their iCloud backups because they don’t fit in that pesky 5GB limit.
Since users who have iCloud Backup enabled and have a 2FA iCloud account get automatically enrolled into iCloud Messages, surely Apple has foreseen the fact that tens of thousands of users’ iCloud Storage limits will cry out in terror and backups will be suddenly silenced?
So now I wonder.. what if Apple releases Messages in iCloud at WWDC18 combined with an increased storage limit for iCloud? 50GB instead of 5GB should do nicely and is a nice way of showing off iCloud Messages during WWDC18 without making it a rehash of last years backup by reframing it within an iCloud upgrade:
“iCloud now has a 50GB limit. BOOM. Perfect to store all your messages, photos and documents in the cloud and synced across devices.’
Yesterday I got a notification for a memory from three years ago called Kris’s Birthday. iCloud Photos had somehow found out that it was Kris’s birthday yesterday, and that he and I were at the same event on his birthday a few years ago.
I really like these kind of memories and alerts. They’re timely, often bring back events I had forgotten about, and the photo selection is quite good.
Only, this time, the event itself had nothing to do with the fact that it was my friend’s birthday. And I couldn’t find a way to change the memory’s title within iOS Photos.
Thanks to @joshducharme, that’s now been solved:
You can! It’s non-obvious though:
1. Select the video made for the memory
2. Once it downloads and starts, tap on it and choose Edit
3. Change the title of the video
Once you save, it renames the video title and the name of the memory.
Anyone can build a website thanks to great resources like Squarespace. And, if the website is responsive and written with any decent framework, it’ll behave nicely on macOS and iOS. Safari will use the Title and Favicon tag to create a nice bookmark, it’ll pickup on the specified RSS feed and, if the site has any article content, it’ll show the Reader View option.
But, with a few extra additions to your site’s <Head>, it can become a first class iOS and macOS citizen.
Way before native iOS apps, Apple allowed you to add web apps, or regular websites to the Homescreen of iOS. Via a specific meta tag you can add a custom icon to your site. The easiest way is one simple 512px image, but you can add specific sizes for every screen size if you want to. Sadly, vector images are not supported.
And, if your site has a very long title you can add a shorter custom title for WebClips. The maximum amount of characters shown on the iOS Homescreen without being shortened with ellipsis is around 11 characters.
Newly added in El Capitan, you can pin a site in Safari to the left of the Tab bar, making it easily accessible all the time. These pinned sites get a custom icon that’s highlight when active and is specified with a specific tag.
There’s a few rules:
The icon has to be an svg with a single layer and a <0,0,16,16> viewport.
The icon should be #000 black filled with no other styles.
The icon is always displayed in one color specified in the tag.
By default the MacBook Pro’s Touch Bar displays the default favicon for Bookmarked websites. But, as a free bonus, every site that has the pinned tab icon defined, gets a nice icon in the Touch Bar consisted of their icon in white surrounded by the specified color.
We’ve got Alexa running at home to control our Sonos devices. Alexa, play Metallica. Alexa, play VRT Studio Brussels. Alexa, lower the volume. Alexa, stop the music.. Once you’re used to controlling music by voice, anything else feels antiquated and clumsy.
Before Alexa, I had already installed HomeBridge on my Mac mini to integrate Sonos into HomeKit. Nothing fancy, it just enabled Play/Pause via the homebridge-sonos plugin. This allowed us to say Hey Siri, Stop Music in the Dining Room. Or, combined with a Hue Tap next to our front door, enabled me to tap one button when exiting the house and having all lights and music turn off with a single action.
But Homebridge on my Mac mini wasn’t the most stable of installations. Updating the Mac often resulted in a broken node.js or npm installation. A recent series of tweets from Federico Vittico about installing Homebridge on a Raspberry Pi made me remember I had one somewhere in the house.
So, an afternoon later I now have a Raspberry Pi running HomeBridge with the Sonos plugin active.
A friend messaged me yesterday: do you know an app that can log ‘times fallen’ in Health? His lovely girlfriend needs a wheelshare to get around, and has to log these kind of medical events.
I didn’t find one with a search in the App Store (then again, no surprise there), I didn’t want to tell him she can just log it manually in Health and being lazy as I am, writing one myself wasn’t really an option.
Or could I? Thanks to Workflow’s Health integration, writing an app that logs a fall with a touch of a button is easy.
Five minutes later his girlfriend now has a Workflow complication on her Apple Watch. Pressing it runs the ‘Fallen’ workflow and logs a fall with the time and date in Health. You can find the workflow here.
If you wonder why Apple bought Workflow? In the words of Gusteau:
I finally got my hands on the new iPhone 6s plus today. Since Belgium wasn’t in the first release wave, I had two options: wait until the next wave hits (next friday), or go to France and buy an iPhone via in-store reservations. I’ve been checking Apple’s preorder page and iStockNow every morning at 6 AM —I’m not very patient when it comes to buying new toys (hello Lego WALL-E on my desk), so— hoping to see the iPhone 6s Plus in stock. And I finally managed to get a reservation today.
A two hour train ride, 15 minutes in the Apple Store and a three hour trainride later, my new iPhone sits next to my Mac, and it will probably remain there for the rest of the night.
Why? Because after you unwrap a new iPhone you have two options: start from scratch and say goodbye to your Health Data, or go through the restore-process and retain that data.
Stay connected and wait for the process to complete. (..)
It just works right? That is.. until you use it in real live in combination with an Apple Watch and don’t get your device on day one.
Transfer your iCloud backup to your new device (Extended Version)
Within a week after Apple released iOS 9 and the new iPhone they already pushed two small bug fixes. Which means your old iPhone probably runs a newer iOS than your new iPhone will.
Optionally: Update all apps on the old device to make sure they work on the new hardware.
Verify that everything has uploaded and synced. Especially Photos and iCloud Drive documents.
Unpair your Apple Watch and wait for the syncing process to finish. Takes about 10-15 minutes.
Make an iCloud Backup, which now contains a recent backup for your Apple Watch. Hope nothing errors out, or goes wrong. Takes about 15 minutes.
Unwrap your new iPhone. Enjoy that new Apple product smell. If you try restoring your backup now, it will fail because the backup you just made is made on a more recent iOS version.
Configure your new iPhone as a new device.
Upgrade to the latest iOS. (Takes, yet again 10-15 minutes)
Wipe your new iPhone. (Feels so wrong).
Finally you can follow Apple’s steps and restore your iCloud backup. Naturally, only confirming that your Apple ID belongs to you via two-factor authentication on another device.
Wait until restore finishes. Takes ages.. unless your running a Caching Server on El Capitan with your iCloud backup locally seeded.
Wait until apps are downloaded, Photos and iCloud are cached.
Enter dozens of passwords and reauthenticate most services. Move from 1Password to Dropbox and back again and hope nothing goes wrong.
Re-pair the Apple Watch again and select its latest backup.
Wait until your Watch restore finishes, which takes… a long long time.
Finally enjoy your new iPhone.
Enter some more passwords in password prompts that didn’t occur upon first boot
Repeat in a year, or earlier if you break your device.
Steps 8 and 9 should be part of the initial wizard. If the iPhone detects its not running the latest OS, just update it. It may frustrate some users, but it makes the process so much easier for less-technical-inclined people.
And the Apple Watch really needs either independent iCloud backups, or an easier way to re-pair it to your new iPhone. How about:
You don’t need to unpair your Apple Watch
After restoring your backup to your new iPhone, show an alert that asks you if you want to move your Watch to the new iPhone.
If yes: show that awesome QR code thingie again and voila, re-paired.
But even though the process is frustrating at times, in the end the process does work, and takes way less time than manually redownloading all your apps and configuring all the little settings.