I love AirPods, as you may be able to glean from my official review. They are a product everyone expected Apple to make, but their astounding quality and value took everyone by surprise (yours truly included). So much so that Apple can’t make them fast enough, being virtually out of stock since launching in December 2016. Shipping time was finally down to a few days recently, only to be pushed out again do to the holiday shopping season. Suffice it to say, AirPods have been a massive sleeper hit.
I’m still blown away by how amazing these little things are. That said, here’s how I think Apple can iterate for AirPods 2.
Transmit for iOS always felt like an obvious addition to our lineup, but we never thought it made a ton of sense in the tightly-restricted world of iOS until Apple announced the “Share Sheet” for iOS 8. Finally, we thought, in addition to using Transmit iOS to upload/download whatever you need, you could easily (?) get data out of apps and send it to your favorite servers. So, in 2014, we built it!
On lack of sustainability:
Transmit iOS made about $35k in revenue in the last year, representing a minuscule fraction of our overall 2017 app revenue. That’s not enough to cover even a half-time developer working on the app. And the app needs full-time work […]
On the future of iPad productivity apps:
My optimistic take: we hope that as iOS matures, and more and more pro users begin to seriously consider the iPad as a legitimate part of their daily work routines, Transmit iOS can one day return and triumph like it does on the Mac.
The idea of this needing to happen really sucks, but it’s not Panic’s fault. Apple has only recently begun to capitalize on the form factor and power of iPad. The latest iPad Pro models in conjunction with iOS 11 are huge stepping stones for real productivity when it comes to the tablet as a form factor. As I’ve said before, I use mine to wholly write and publish this blog.
I have been a long-time user of Transmit on iOS, and while it won’t disappear if you already bought it, it’s sad to see development and sales end. I really wish they could have stuck it out longer, as I think iPad is going to have its watershed moment for productivity in the next two years (perhaps with the adoption of an iPhone X-esque edge-to-edge screen, TrueDepth Camera, and Face ID).
Apple today released a statement formally addressing their practice of throttling iPhone performance based on aging batteries. Here are the highlights.
First and foremost, we have never — and would never — do anything to intentionally shorten the life of any Apple product, or degrade the user experience to drive customer upgrades. Our goal has always been to create products that our customers love, and making iPhones last as long as possible is an important part of that.
They then go into a great detail explaining the chemistry of batteries themselves:
A chemically aged battery also becomes less capable of delivering peak energy loads, especially in a low state of charge, which may result in a device unexpectedly shutting itself down in some situations.
It should go without saying that we think sudden, unexpected shutdowns are unacceptable. We don’t want any of our users to lose a call, miss taking a picture or have any other part of their iPhone experience interrupted if we can avoid it.
On preventing unexpected shutdowns:
About a year ago in iOS 10.2.1, we delivered a software update that improves power management during peak workloads to avoid unexpected shutdowns on iPhone 6, iPhone 6 Plus, iPhone 6s, iPhone 6s Plus, and iPhone SE. With the update, iOS dynamically manages the maximum performance of some system components when needed to prevent a shutdown. While these changes may go unnoticed, in some cases users may experience longer launch times for apps and other reductions in performance.
Over the course of this fall, we began to receive feedback from some users who were seeing slower performance in certain situations. Based on our experience, we initially thought this was due to a combination of two factors: a normal, temporary performance impact when upgrading the operating system as iPhone installs new software and updates apps, and minor bugs in the initial release which have since been fixed.
A case of ‘heart in the right place’, but severely lacking in execution.
Here’s the good stuff:
Apple is reducing the price of an out-of-warranty iPhone battery replacement by $50 — from $79 to $29 — for anyone with an iPhone 6 or later whose battery needs to be replaced, starting in late January and available worldwide through December 2018. Details will be provided soon on apple.com.
Early in 2018, we will issue an iOS software update with new features that give users more visibility into the health of their iPhone’s battery, so they can see for themselves if its condition is affecting performance.
As always, our team is working on ways to make the user experience even better, including improving how we manage performance and avoid unexpected shutdowns as batteries age.
Apple really nailed this apology/explainer/discount. They explained the issue, chemistry, and rationale perfectly, using the most accessible language I’ve ever seen in one of these letters. 1 However, they clearly didn’t think anyone would notice this practice, otherwise they would have seen this shitstorm coming from a mile away. What was it I said not long ago about Internet backlash? Ah yes, it’s swift and damning. This just goes to show nobody can hide anything for long from determined geeks.
I hope their new battery features include a choice like this. Until then, it’s back to hating on the MacBook Pro keyboard I guess?
It feels very human, unlike typical PR mechanical fluff. ↩
In emails to The Verge, both companies said they do not employ similar practices with their smartphones. An HTC spokesperson said that designing phones to slow down their processor as their battery ages “is not something we do.” A Motorola spokesperson said, “We do not throttle CPU performance based on older batteries.”
The Verge also reached out to Google, Samsung, LG, and Sony for comment on whether their phone processors are throttled in response to aging batteries. A Sony spokesperson said a response would be delayed by the holidays, and a Samsung spokesperson said the company was looking into it.
Effortless, positive PR for HTC and Motorola, but also Android as a whole. Most people will see this as Android versus Apple, not Apple vs. HTC vs. Motorola vs. LG vs. Samsung, et al.
Though I still don’t agree with how Apple carried out their throttling, I’d take a slowed-down iPhone over an Android device any day. In fact, I’d be curious to compare real life results (read: not quantitative benchmarks) between a throttled iPhone 7 and a comparable Android device.
Apple has been put through the ringer this week on what will hopefully be their last “controversy” of 2017. The charge? Intentionally slowing down aging iPhone models. It turns out there is truth to this old trope, but not for the reason you would think.
I did a Geekbench score, and found I was getting 1466 Single and 2512 Multi. This did not change wether I had low power mode on or off. After changing my battery, I did another test to check if it was just a placebo. Nope. 2526 Single and 4456 Multi. From what I can tell, Apple slows down phones when their battery gets too low, so you can still have a full days charge.
Since then, Apple published this official statement on the matter:
Our goal is to deliver the best experience for customers, which includes overall performance and prolonging the life of their devices. Lithium-ion batteries become less capable of supplying peak current demands when in cold conditions, have a low battery charge or as they age over time, which can result in the device unexpectedly shutting down to protect its electronic components.
Last year we released a feature for iPhone 6, iPhone 6s and iPhone SE to smooth out the instantaneous peaks only when needed to prevent the device from unexpectedly shutting down during these conditions. We’ve now extended that feature to iPhone 7 with iOS 11.2, and plan to add support for other products in the future.
I believe Apple’s intentions were in the right place. There’s no reason to think they weren’t. I believe they always try to put the customer first, which has made them incredibly successful.
That said, any way you spin it, the optics here are terrible. For years, people have speculated about Apple intentionally slowing down older technology when new software updates are released, which has always been refuted with evidence. Admitting the slowing down of old iPhone models for any reason was never going to go over well. In fact, they have already been sued three times since their admission.
This seems like a classic damned if they do/damned if they don’t scenario. If Apple did nothing, the ‘planned obsolescence’ trope moves forward in a different way when you have phones dying at 30% battery for seemingly no reason.
I do question their methods. Apple provides a disclaimer when your battery needs to be serviced, but it is easily missed and hidden away in Settings. They should have made the notice abundantly clear, instead of downplaying it.
Problem with Choice
Should Apple have offered this setting change as a choice? Let’s first consider some of their history on the subject.
Apple has always been accused of not giving customers enough choice (especially on iOS). Lack of customization and utility early on spurred the jailbreak movement, creating choice where there was none. The reality nowadays is an abundance of choice; enough to render jailbreaking irrelevant. Does Apple always offer choice when there should be? I wouldn’t say so, but it’s not for nefarious reasons. Although, it can make choice on iOS sometimes feel like an illusion. 2 Here’s an example:
Outside of Apple Music, they haven’t integrated music streaming services with Siri just yet. Obviously, integrating first-party services is much easier and has advantages (e.g. controlling music via Siri on Apple Watch), but writing an API for other services to play music must be a gargantuan task. Just think of all the variables at play (artist, album, track, composer, genre, etc.) among many nuances. I would expect to see Apple open this up as early as iOS 12 — the timing feels right. Suffice it to say, I don’t think they are completely holding out on Spotify, Google Play Music, Pandora, and the others.
One more: twelve years into the platform, you still can’t choose ‘default’ apps on iOS. This is probably a decently-sized task as well, but one I feel should have arrived already.
Now, back to the matter at hand. Offering throttling as an option to the user sounds like a very un-Apple thing to do. Apple would never want its customers to deliberately make such a large trade off, but if they were going to do something about it anyway, why not? In theory, it sounds like the choice would be incredibly inelegant. In fact, I wouldn’t expect them to ask the question as a simple yes/no. I would have liked to see something like this:
Prompt the user about their battery issue and explain the throttling, along with a button to learn more via an option in Settings.
Turn on throttling.
Allow user to turn off throttling in Settings, but prompt them with the original notice every time.
The prompt could be as simple as:
This would have been a simple CYA step that could have avoided a lot of this mess. I think Apple needs to think a bit harder about offering choice in new ways, especially in a day and age where devices last much longer than they used to. We’ll see if there is any course-correction moving forward or if they double down.
As reported by the benchmarking app ‘Geekbench’. ↩
The iMac Pro exists because it turns out that there is a lot of air underneath the aging Mac Pro and above the incredibly popular MacBook Pro. A single-digit percentage of Mac customers buy the Mac Pro and, in recent years, Apple had been seeing a major rise in “pro” customers of all shades purchasing iMacs because of their incredible screens, all-in-one form factor and overall ease of deployment.
The rear ports are definitely different, of course. You have 4 Thunderbolt 3 ports, which run on two separate controllers, 2 ports each. So you should get blazing speeds on those whether they’re used for e-GPUs or storage or displays. There are 4 USB 3.0 A ports and SD slot and, for the first time ever, a 10 Gigabit ethernet port right on the back.
Not every configuration of the iMac Pro will be available to order today online and in stores next week. You’ll be able to get the 8 and 10-core Intel Xeon W versions of the machine with any other memory, graphics or storage options you like, but the 14 and 18-core editions are just orderable now for delivery in January. Those new core configurations are previously unannounced options. Each has 1MB of L2 and 1.365MB of L3 cache.
This thing sounds incredible. I’d love to have one, but it’s way beyond me. It should be a nice stopgap while developers seeking even more power (or a purely standalone Mac) await the completely-redesigned Mac Pro. I bet the space grey accessories will go for a pretty penny on eBay since you can’t buy them separately.
As Spotify continues to inch towards a public listing, Apple is making a move of its own to step up its game in music services. Sources tell us that the company is close to acquiring Shazam, the popular app that lets people identify any song, TV show, film or advert in seconds, by listening to an audio clip or (in the case of, say, an ad) a visual fragment, and then takes you to content relevant to that search.
We have heard that the deal is being signed this week, and will be announced on Monday, although that could always change.
One source describes the deal as in the nine figures; another puts it at around £300 million ($401 million). We are still asking around. Notably, though, the numbers we’ve heard are lower than the $1.02 billion (according to PitchBook) post-money valuation the company had in its last funding round, in 2015.
Obvious Apple Music and Siri benefits aside, Apple must be really impressed with Shazam’s underlying technology to make this purchase. I’ve never seen anyone use Shazam on a TV show or in any capacity other than identifying music, but there could be some real benefits to tried and tested audio recognition down the line (e.g. AR, advanced Siri functions, HomePod).
Apple Chief Design Officer Jony Ive is once again taking over management of the design team at Apple according to changes made to Apple’s official “Apple Leadership” website.
The site was updated this morning to remove the profiles of Richard Howarth and Alan Dye, who were managing the day-to-day operations at Apple while Ive oversaw all of Apple’s design projects, and Bloomberg has confirmed that Ive is once again in direct control of the team as shared by Mark Gurman.
Ive first stepped back from day-to-day management of Apple’s design teams in 2015, when he took on the role of “Chief Design Officer.” Alan Dye and Richard Howarth were elevated to vice president positions at that time, with Howarth responsible for industrial design and Dye responsible for user interface design.
There is one of two stories here. Either Apple is executing a plan long in the making now that Jony is done with the new campus and retail makeover (most likely), or this is a reactive measure to something bigger.
In the case for something bigger: Apple makes polarizing decisions, but none have been more divisive than ones introduced in the past few years (largely dealing with MacBook), such as:
Although Jony has no doubt been engaged with all these hardware and software design changes, his attention has absolutely been elsewhere. Also, let’s not get software design confused with software engineering — a sensitive area for Apple as of late with multiple widespread bugs. We can argue the software design of Apple’s systems all day, but the area needing more attention right now is hardware design.
Either way, I’m more interested to see what exactly has happened to Alan Dye and Richard Howarth.
“With the completion of Apple Park, Apple’s design leaders and teams are again reporting directly to Jony Ive, who remains focused purely on design,” Amy Bessette, a company spokeswoman, said Friday in a statement.
Finally took my 2016 MacBook Pro in to the Apple Store this past week for the ‘sticky’ keys problem. ↩
Updated 12/5 at 1:30 PM Pacific: watchOS 4.2 for Apple Watch is now available with Apple Pay Cash support.
Chaim Gartenberg for The Verge:
Apple was forced to release iOS 11.2 on Saturday, which was a little earlier than planned, due to a software bug. Now, Apple Pay Cash — one of the marquee features of the update — is being activated for users.
Apple Pay Cash lets users send and receive money directly though iMessages, similar to Venmo or Square Cash. Money that people send you will live on a digital Apple Pay Cash card in the Wallet app, which users can spend anywhere that Apple Pay is accepted, or send to other people. (The new feature is only available in the US for now, though.)
Nice to see this finally launch (if in a weird way), after being delayed from the original iOS 11 release.
The setting to activate Apple Pay Cash seems to be rolling out slowly, as mine didn’t appear until about 7pm Pacific. To check if it’s active for you, go to Settings > Wallet & Apple Pay. Once set up, you’ll find your Apple Pay Cash card inside the Wallet app (along with a cool shimmering animation when you tilt your phone). As you can see in the featured image above, you can send and receive cash in Messages via the Cash app in the app drawer. 1 My Dad … graciously helped me test this important new feature.
This really demonstrates what a trojan horse the Messages app has become (in a good way). Don’t underestimate how important iMessage is to Apple. It’s one of the main reasons people love iPhone, and it keeps them locked into the Apple ecosystem.
It won’t be too long before iOS users relegate Venmo/Square Cash/PayPal to payment methods only for cross-platform because of Apple Pay Cash being baked in.
Apple has released iOS 11.2 to address the nasty date and time bug discovered late last night. This is definitely an unprecedented action for them, but I suppose a good decision as long as iOS 11.2 doesn’t break anything else.
The full release notes are below, and include many other improvements/fixes. Despite the nature of the release, there is some pretty nice stuff listed here. NOTE: Apple Pay Cash is included, but it won’t be active until next week.
Full release notes for iOS 11.2:
iOS 11.2 introduces Apple Pay Cash to send, request and receive money from friends and family with Apple Pay. This update also includes bug fixes and improvements. For information on the security content of Apple software updates, please visit this website.
Other improvements and fixes:
Adds support for faster wireless charging on iPhone 8, iPhone 8 Plus and iPhone X with compatible third-party accessories.
Introduces three new Live wallpapers for iPhone X.
Improves video camera stabilization.
Adds support in Podcasts to automatically advance to the next episode from the same show.
Adds support in HealthKit for downhill snow sports distance as a data type.
Fixes an issue that could cause Mail to appear to be checking for new messages even when a download is complete.
Fixes an issue that could cause cleared Mail notifications from Exchange accounts to reappear.
Improves stability in Calendar.
Resolves an issue where Settings could open to a blank screen.
Fixes an issue that could prevent swiping to Today View or Camera from the Lock Screen.
Addresses an issue that could prevent Music controls from displaying on the Lock Screen.
Fixes an issue that could cause app icons to be arranged incorrectly on the Home Screen.
Addresses an issue that could prevent users from deleting recent photos when iCloud storage is exceeded.
Addresses an issue where Find My iPhone sometimes wouldn’t display a map.
Fixes an issue in Messages where the keyboard could overlap the most recent message.
Fixes an issue in Calculator where typing numbers rapidly could lead to incorrect results.
Addressed an issue where the keyboard could respond slowly.
Adds support for real-time text (RTT) phone calls for the deaf and hard of hearing.
Improves VoiceOver stability in Messages, Settings, App Store and Music.
Resolves an issue that prevented VoiceOver from announcing incoming Notifications.