Apple Has a DevRel Problem

The iPhone Duo, Apple’s first foldable iPhone, goes on sale today and my app isn’t ready for it. Dewfall, my app for reading the whole Bible one verse at a time, is on the App Store. The only thing Apple sent me about the Duo as one of its developers was a single notification in App Store Connect about the new Xcode. That’s it!

I’ve spent years on the company’s side of this, in developer relations (DevRel): head of developer relations at ZEIT (now Vercel), director of developer relations at Xata, my own DevRel consultancy, then developer advocate at DataStax until IBM bought it (my about page has the rest). I love Apple’s stuff too (I said so on stage at RenderATL in 2023). And to be fair to Apple, it did a lot for developers before this launch: more than 2,000 of them went to its in-person workshops in 19 cities. I still think Apple has a DevRel problem.

What is DevRel?

DevRel, short for developer relations, is how a company builds mutually beneficial relationships with the developers who build on its platform. A DevRel team writes docs and sample code, runs early access programs and events, and takes developers’ feedback back to the product team. You measure it by what those developers ship.

I did a 2-hour solo episode of my podcast, ConTejas Code, on what DevRel is and how to measure it. Early in it I gave “the practice of building mutually beneficial relationships with software developers on behalf of a company” as the definition and called it “the most Wikipedia definition you can get”. Wikipedia’s own is close: “an umbrella term for practices employed by an organization that builds developer-facing software to connect with the developers that use that software.”

The way I usually explain it uses the iPhone (kind of funny today). Apple sells iPhones to people like my parents so it needs customer relations. Some of its customers are developers who build the apps you use on it so it needs developer relations as well.

On the show I said Microsoft’s Windows developer relations group in 1997 “literally looked at how many apps did these people produce”. A minute later I said “If that number doesn’t work, then the function is broken. That’s it.” For a new phone, that number is the apps that are ready on the day people open the box. For the Duo, when the reviews went up 2 days before launch, a lot of the big ones weren’t.

What does DevRel actually do?

Day to day DevRel is docs, sample code, demos, talks and streams, a developer community and a lot of listening. On the show I borrowed an idea from developerrelations.com and described it as “this, like, two way bridge. You help external developers succeed with your product, and you bring their needs and feedback back into the company.”

On Langflow I once noticed some components were missing and shared it with the team. A few days later, developers at a hackathon said the same thing. With my feedback and theirs together, the team started investigating a fix. That’s classic DevRel.

The gold standard, as I put it in my DevRel episode, is “you’re a product engineer with a megaphone”. DevRel is an incredible job (the travel did wear me down badly: I wrote about it in my 2022 health post). I’ve talked about the job on the show with Rachel Nabors in episode 28, on the future of DevRel and with Tracy Lee of This Dot in episode 48, on how to be successful in DevRel.

Before a launch it’s the same work with a date on it. In the same episode I said the path a developer walks, from signing up to their first success, “needs to be well traveled by your DevRel team before you expect developers to go down”. The DevRel team’s job is “to get rid of all the mines, and then you invite your developers to come walk that.” For the launches I helped with at Liveblocks, OpenSauced, Ravion and Xata, DevRel meant:

• demos and sample apps
• docs and guides, written before launch day
• early access developers using the product, with their feedback going back to the team before launch
• the launch videos, streams and talks

I remember Liveblocks especially (its CEO, Steven Fabre, came on episode 24 of my show). I’m also an angel investor in OpenSauced and Ravion (both are on my investing page).

Developer relations vs developer advocate

Developer relations is the function. Developer advocate and developer evangelist are job titles inside it.

In Defining Developer Relations, Phil Leggetter splits the titles by what they do. Developer evangelists “may focus much more on activities that result in acquisition such as docs, blog posts, event sponsorship and talks”. Developer advocates “may undertake all of the above activities”, especially the ones he tags with retention and product, like capturing developer feedback.

Title	What it means
Developer relations (DevRel)	All of it: docs, community, developer experience, advocacy and getting feedback into the product. Apple’s team for it is Worldwide Developer Relations (WWDR).
Developer evangelist	The role Apple invented in the 1980s, when it was called software evangelist. Mostly outward: talks, posts, demos and docs that get developers to try a platform.
Developer advocate	Can do all of that and also brings developers’ feedback back to the product and engineering teams. It was my title at DataStax.
Developer relations engineer	The title Google gave both roles when it merged its developer advocates and developer programs engineers, as Justin Poehnelt wrote up. On the show I called myself “one of the developer relations engineers on Langflow”.

Why iPhone Duo apps aren’t optimized yet

Many iPhone Duo apps aren’t optimized yet because a fully optimized app needs the iOS 27.1 software development kit (SDK). Apple released that SDK in beta on September 18, 2026, 35 days before the phone went on sale. App Store submissions for Duo apps opened on October 5.

An SDK is the set of tools a developer builds an app with (for an iPhone app, that’s Xcode and the iOS SDK inside it). Marques Brownlee (MKBHD) shows what an app without the new one looks like in his iPhone Duo review (past 9 million views). Closed, the Duo is a normal iPhone on the left with the buttons moved over to the right where your thumb is. He calls Apple’s own apps “sort of the blueprint for an optimized app”. Then he flips through Spotify, Google Maps, Waze, Discord, X (he still calls it Twitter) and Google Calendar, every one of them with “a black bar down the right-hand side where the buttons are supposed to be”. Open the phone and they’re mostly “small, unoptimized iPhone apps in the… middle of this huge screen”:

He shows the good ones too: Instagram “just got the update today” while he was filming and Carrot Weather “did it”. Even Apple’s own Keynote, Pages and Numbers only got their Duo update the day before the phone went on sale. Then Apple pulled all 3 from the App Store for a while!! MacRumors couldn’t tell whether that was on purpose or a bug.

6 weeks earlier, John Ternus (Apple’s CEO since September 1) made fun of everybody else’s foldables in the keynote where Apple announced the Duo. On theirs, he said, “movies are boxed in by oversized black bars, making a larger screen feel much smaller.”

Oversized black bars!! On a phone that starts at $1,999, that’s literally what most of MKBHD’s apps look like this week. To be fair to Ternus, he meant movies on square screens and not apps.

Apple’s own guide, Three steps to make your app shine on iPhone Duo, says which look an app gets from which SDK:

• Built with the iOS 26 SDK or earlier, an app runs but “won’t adapt to all layouts”. Open, it appears “in the center of the display, with empty space surrounding the window”. Closed, it sits “to the left of the status bar and camera”.
• Built with this year’s iOS 27 SDK, apps “resize to fill most of the inner display” but still avoid the status bar on the right edge. That’s probably what Spotify is doing when MKBHD says it “kind of stretches things”.
• Only an app built with the iOS 27.1 SDK or later is “optimized for iPhone Duo”, with “toolbars and tab bars appearing vertically below the status bar”.

The apps sitting small in the middle of MKBHD’s open screen are the first kind. They hadn’t even shipped a build with the iOS 27 SDK, which Apple explained at its Worldwide Developers Conference (WWDC) in June and opened for App Store submissions on September 9. So the 35 days explain the missing side toolbars but not the tiny windows.

Dewfall is one of the apps that aren’t optimized. So on a Duo it probably looks a lot like the ones in MKBHD’s review (I didn’t order a Duo).

Here’s who had what, and when, from the day Apple announced the Duo to the day it went on sale (the dates are on Apple’s releases page and in its developer news):

Apple announces the Duo

Sep 9

Xcode 27: apps resize, no Duo simulator

Sep 14 to Oct 23: 39 days

Xcode 27.1 beta: the Duo SDK and simulator

Sep 18 to Oct 23: 35 days

The App Store takes Duo apps

Oct 5 to Oct 23: 18 days

Reviewers have a Duo

Oct 14 (or earlier) to Oct 23: 9+ days

The final Xcode 27.1

Oct 15 to Oct 23: 8 days

The reviews go up

Oct 21

On sale, and most developers' first Duo

Oct 23

Sep 9Oct 1Oct 23

On September 9 Apple’s press release said “Third-party apps, including Netflix, Zoom, and Slack, are already taking advantage of the folding design.” The next day 9to5Mac wrote that “most developers won’t have access to a real iPhone Duo until launch day”. Xcode 27’s iOS 27 SDK resizes apps to fill most of the Duo’s inner screen (its release candidate opened App Store submissions on September 9), but it had no Duo simulator. The Xcode 27.1 beta on September 18 brought the iOS 27.1 SDK and a Duo simulator you can fold and unfold on a Mac.

An app built with a beta can’t go on the App Store. The first day a developer could submit a Duo version was October 5, 18 days before launch. Every one of those updates still had to get through App Review in that window.

Apple did run DevRel for the Duo

It started in June. At WWDC, a session called Modernize your UIKit app (UIKit is Apple’s original framework for building an iPhone app’s screens) told developers that iPhone apps were now “fully resizable” and that “it is important that your app dynamically adjusts to any available scene size at runtime”. It gave iPhone Mirroring on the Mac and iPhone apps on iPad as the reasons and never mentioned a foldable (in hindsight it was probably the Duo). On September 9, the day it announced the Duo, Apple put up a developer page with design guidelines and Tech Talks like Prepare your app for iPhone Duo. A week later it ran online Group Labs, where developers ask Apple engineers questions live. It posted developer news about the Duo on September 9, 16 and 18 and on October 5. Its October newsletter pointed developers to Duo submissions and new Group Labs.

And yesterday Apple said in its newsroom that “More than 2,000 developers have attended more than 50 in-person workshops in 19 cities around the world”. The same post highlights 58 apps from other companies that are optimized or on their way, from Netflix, Zoom and Slack to Instagram (Apple hasn’t said how many optimized apps there are in all). Susan Prescott, Apple’s vice president of Worldwide Developer Relations, says in it that “The response to iPhone Duo from our developer community has been incredible”. That’s a DevRel program!

Developers who went to the workshops say they helped. At the one in Berlin, Michael Temper wrote that “It was really helpful to get a feeling for the device” and that he “was able to optimize the UI for the different poses” of his game. Apple’s developer relations team also reached out one to one. Graham Dawson, an indie developer, wrote “Thanks to Apple Developer Relations reaching out to me, I found an issue with my proposed Duo update”. It was a rotation bug that only showed up on an actual Duo (“something that waasn’t visible in Duo simulator”).

35 days from SDK to launch

Developers got the Duo’s tools 35 days before customers got the phone. For some of Apple’s other new devices and screens since the App Store, and for Microsoft’s own 2-screen Duo, it looked like this:

Microsoft Surface Duo, 2020

232

Apple Vision Pro, 2024

226

Apple Watch, 2015

157

Apple silicon Macs, 2020

148

iPhone SDK and the App Store, 2008

126

iPad, 2010

66

iPhone X, 2017

52

Apple TV with tvOS, 2015

51

iPhone Duo, 2026

35

iPhone 6 Plus, 2014

10

iPhone 5, 2012

9

The Duo got the third shortest runway on that list. The iPhone 5 had 9 days in 2012 and the 6 Plus 10 in 2014, both new sizes of a screen developers already knew. Apple seeded the iPhone 5’s tools the day it announced the phone. When the iPhone 5 went taller, Phil Schiller showed an app that hadn’t been updated and said “We center it and place black borders on either side” (TechCrunch). The Duo asks more of an app than a new screen size did: it folds, it has a closed screen with the buttons on the side, it has poses and it can run 2 apps side by side. Counting from the WWDC sessions in June it’s 137 days, but Apple didn’t name a device until September 9.

The closest match on the list is the iPad, which ran iPhone apps small in the middle of its screen the way the open Duo does (MKBHD remembers the “iPad days where you could just hit the 2x button and it just made it bigger”). iPad developers got 66 days (almost 2× the Duo’s).

Vision Pro got 226 days, developer labs in 6 cities and developer kits that teams could apply for. It launched with “more than 600” apps built for it. In 2015 developers who won a lottery got an Apple TV developer kit for $1!! It came “at no cost, with a $1 fee being charged to verify billing and shipping addresses” (MacTech). In 2020 Mac developers could get a Developer Transition Kit for $500 (a Mac mini with an Apple chip inside that went back to Apple afterward), about 5 months before the first Apple silicon Macs went on sale.

Apple did put the Duo in front of developers this time. More than 2,000 of them at the workshops is way more than the “over 100 different developers” who reportedly got into the Apple Watch labs in Cupertino in 2015. But Apple’s Duo page for developers lists workshops, Group Labs, Q&As, Tech Talks, Xcode, docs and design kits. It doesn’t list a developer kit or a loaner.

When a developer asked about loaners on r/iOSProgramming, one answer was “You won’t get a loaner. If you go to an Apple-run iPhone Duo development event, you may get the opportunity to run your app on a real iPhone Duo. May.” A more upvoted one said “Get in touch with your local Apple Developer Evangelist. They should be able to help out.” The person asking had missed the local workshops (“Scheduling problem and early sell out”). Their app also “wasn’t ready” the week before. And Jonathan Unikowski, who came to iOS after 3 decades of web and desktop work, posted this when MKBHD’s clip went around:

That’s a little harsh on the workshops (they did put a Duo in front of whoever got a seat). A commenter who says they’ve been an iOS developer for 10 years left a comment with 1,600 likes under MKBHD’s review: “The SDK was released way too late. We’re currently working on adapting our apps, and many developers will be releasing updated versions soon.”

MKBHD’s own guess is that things start feeling “way better” in about 6 months, “once developers get a bunch of these”.

Apple invented the developer evangelist

In the early 1980s Mike Murray of the Macintosh division coined the term software evangelist for the people whose job was to get other companies writing software for the Mac. Mike Boich became the first one in 1982 and hired Guy Kawasaki, who became Apple’s chief evangelist and made the word famous. Wikipedia says the word is borrowed from religious evangelism, which goes back to the Greek euangélion, good news (the same word the Gospels are named after).

Kawasaki’s own definition of the job, as Wikipedia quotes it, is “using fervor and zeal (but never money) to convince software developers to create products for a computer with no installed base, 128K of RAM, no hard disk, no documentation, and no technical support, made by a flaky company that IBM was about to snuff out.”

No installed base! That’s the Duo this week, at least for an app’s Duo layout: almost nobody owns the phone yet (every iPhone app still runs on it). In the r/iOSProgramming thread about loaners, somebody asked how many people would have a Duo and also have your app. One commenter answered “At most 1% over the next 6-12 months.”

Microsoft created its own evangelist role in 1987 (Wikipedia again) and wrote the playbook down. Its developer relations group’s Effective Evangelism came out years later as evidence in an antitrust case. An evangelism timeline filed with it is dated October 9, 1997. The playbook lists IBM among Microsoft’s “enemies”, which is hilarious to read as somebody who works at IBM. It says “Success is measured in shipping applications.” It also says “Platforms, by themselves, are of little or no value to end users.”

Apple still calls them evangelists! After the Berlin workshop, Lennart Fischer thanked “the entire Design & Technology Evangelist team and our Partnership Managers” for hosting it.

Secrecy beat DevRel this time

Apple chose the secrecy and it’s proud of it. In an interview MacRumors wrote up, Greg Joswiak, Apple’s senior vice president of worldwide marketing, said he’s “super proud” that Apple kept the project relatively secret: “We put the extra security on it. We didn’t talk about it to anybody.” Joswiak joined Apple in 1986 and, in Apple’s own words, “began his career at Apple working on the early Macintosh computers and supporting the Mac’s community of third-party developers.” Wild!!

DevRel needs developers to know early. Joswiak was proud that almost nobody did. Apple has managed secrecy and early access at once before. In 2010 it sent iPads to a few developers before launch with “10 pages of rules and regulations”, including that “the iPad has to be kept secured to a fixed object in a windowless room” and that Apple “requires photographic proof of compliance” (Engadget). A windowless room! Within a week of launch, “some 3,500 applications” had been optimized for the iPad (Technologizer).

Who gets early access is a DevRel decision. For the Duo, the apps Apple showed in its keynote (Zoom, Slack, Detail and Netflix) clearly had it. Major League Baseball (MLB) says in Apple’s October 22 post that it’s “grateful to have worked with Apple to ensure the app is ready for the World Series”. AppleInsider wrote that “with the exception of firms whose apps were shown at the launch, few or no developers had an iPhone Duo to try.” Apart from the workshops, that matches what I found.

Reviewers got hardware early too. The Duo “has been in reviewers’ hands for at least a week”, Tom’s Guide wrote on review day. MKBHD’s video description says “Phone provided by Apple for review.” Meanwhile someone on r/iPhoneDuo learned that “many app developers have their apps set to update the day before October 23, and didn’t plan on reviewers testing their apps a week prior.” So some of the apps in the reviews had a Duo update ready and waiting to go out the day before launch!! Apple picked the day reviewers got their phones and many developers picked the eve of launch for their updates (the 2 weren’t lined up).

Tanmay, who makes a handful of iOS apps, says “almost all devs I know have a working Duo update on day 1, the media had no idea.” He’s even “actually okay with devs not receiving early units” (“The documentation and workshops were pretty solid to get a working version ready”). His next line is “The problem is marketing, their marketing team completely sidelines devs. 0 help in connecting the people Apple gave review units to with devs making Duo app.” “At the very least,” Tanmay wrote, “have the WWDR team connect devs to the media who receive review units.”

Apple can drag developers along (most companies can’t)

MKBHD says it himself, 16:32 into his review: “this is one of Apple’s biggest strengths, to be fair, like just dragging developers along for stuff like this.” He’s right! Mark Gurman thinks it’ll be sorted out in weeks:

John Gruber goes further on Daring Fireball: “my gut feeling is that there are more third-party apps ready to go on day one for the Duo than for any of those previous transitions” (he lists iPhone X, 6 Plus, iPhone 5 and Retina on the iPhone 4). He says “Some of the apps that aren’t yet updated are quite popular” and then “developer support is not a problem for the Duo.” He compares it with Android: “‘Flagship’ Android foldables have been out for over 7 years and developer support for them today remains nothing close to developer support for the Duo”.

Developers got 52 days with the iPhone X in 2017. Cult of Mac complained about “those massive black bars” on iPhone X apps that October. By April 2018 Apple required new apps to support its display. Apple has the same stick ready for the Duo. From April 2027 every App Store submission needs Duo screenshots and has to be built with the iOS 27 SDK or later. That SDK alone gets an app most of the way across the inner screen (apps that never update, like the gym app MKBHD says is “probably not gonna get updated”, keep their black bars). Apps that submit Duo screenshots get a “Made for iPhone Duo” badge on their App Store page.

For lots of apps the fix really is small. Chad Etzel wrote that “if your app is a NavSplitView + Lists, iPhone Duo support is free. I didn’t have to make a single change to the code for LinkShare. Just recompile with Xcode 27.1+”. If your app already has an adaptive layout that works on iPad and Mac, Apple says “you’re well on your way to supporting iPhone Duo”. On Reddit, u/juju0010, an iOS developer, told worried buyers that the companies working on Duo layouts “don’t need the physical device to test them”. They also wrote “Rest assured, we’re aware our apps look like shit and we’re already working on it.” Their own Duo doesn’t arrive until November 16 and they’ve already optimized several of their apps for it.

The unoptimized apps MKBHD shows come from big companies with big app teams (3 of them are Google’s). Apple probably has less pull with them than with a launch partner. Spotify, Discord and X haven’t said why they hadn’t shipped an update when the reviews went up. Google had started: on October 22 Nicole Nguyen of The Wall Street Journal wrote that Gmail, Maps and Photos were “rolling out UI optimizations today” (still with “no right-side controls”).

I agree with them about where this ends up. Apple can drag developers along because few of them can afford to skip the iPhone (Apple counts an ecosystem of “more than 2.5 billion devices worldwide”). On the show I said “DevRel is all about relationships”. I just don’t think dragging developers along is the same thing as a relationship with them. Dragging means the gap gets paid for by the people who spent $1,999 this week and by the developers who got 35 days and (unless they got a workshop seat) no Duo to test on.

A long runway doesn’t guarantee anything either. Microsoft gave developers 232 days and an emulator for its own 2-screen Surface Duo. By 2024 Windows Central was writing that “The product line is dead”. Samsung first showed developers the Galaxy Fold’s screen 303 days before it went on sale (the plan was 170, until review units’ screens broke) and set up test labs with Google “from Seoul to Mountain View to Beijing”. Apps that didn’t fit the screen were still “a pretty major problem in the early days of Android foldables” (9to5Google).

Most companies launching a platform don’t have Apple’s pull. A startup with a new application programming interface (API) or a new device can’t drag anybody anywhere (I’ve worked at a few).

What a DevRel launch strategy looks like

A DevRel launch strategy gets developers ready before customers show up: tell a few of them early, get them hardware, ship docs and samples, fix what they find fast and count the apps people use.

If I were running developer relations for a launch like the Duo, these are the things I’d ask for (Apple already did some of them):

1. Tell a few developers before customers know. Microsoft’s 1997 evangelism timeline says to talk to “a small number (four, plus or minus two)” of the developers who matter most, under a non-disclosure agreement, “Well before there is a detailed spec”. Apple did this with the apps in its keynote (and in 2010 with the iPads in windowless rooms).
2. Get hardware to developers before reviewers get it. The $1 Apple TV kit is the model (a loaner program is the cheap version). Supply made this hard for the Duo. Mark Gurman wrote in his newsletter that Apple “knew there would be severe supply constraints but went ahead with the launch anyway” (MacRumors). Delivery dates slipped to January 25 within 30 minutes of preorders opening, which means every developer kit would have competed with a customer’s order. It also means a lot of buyers won’t have a Duo for weeks or months (some customers have since been given earlier delivery dates, MacRumors reported). MKBHD expects “way more apps optimized for the Duo” by the time they do. Apple will soon have a place that could do this in Berlin, my city: in June it announced its first developer center in Europe there for “later this year”, with “dedicated labs” and “hands-on support from Apple experts”.
3. Ship docs and samples before launch. Apple did this one well! The design guidelines and the Tech Talks went up the day it announced the phone. The 3-step guide lists the exact code to search your project for, from UIScreen.main to userInterfaceIdiom == .phone. Step 1 is literally to ask Xcode’s coding assistant to “get my app ready for iPhone Duo.” Very 2026 of them. I’ve given talks on docs, like Changing The Game with Developer Experience at ConFrontJS in 2022, where I said docs are “key to good developer experience”. At Xata we wrote ours for the person trying a brand new product in beta who searches Google and Stack Overflow and finds nothing (I said so on a livestream in 2022).
4. Fix what early developers find, fast. I’d measure DevRel by the “time between feedback received and feedback addressed”. The final Xcode 27.1 shipped October 15. So anything developers reported against the September 18 beta had under 4 weeks to be fixed in Apple’s tools. Their apps still had to get through App Review before October 23.
5. Line up review units with developer updates. That’s Tanmay’s fix.
6. Pick launch partners by what people use most. Microsoft measures its push to get apps onto laptops with Arm chips by “apps representing 90% of total user minutes” (Windows Developer Blog). MKBHD’s Spotify, Maps, Waze, Discord, X and Calendar are his user minutes.
7. Count the apps people actually use. Mary Thengvall, who wrote The Business Value of Developer Relations, puts it as “Don’t conflate work output with goals”. By that test the more than 2,000 workshop seats are output. So is a list of 58 launch apps. Apple’s newsroom post doesn’t say how many of the apps people open every day were optimized on launch day.

Are people canceling their iPhone Duo preorders?

Some buyers say they’ve canceled over the apps, but nobody has numbers and Apple reportedly raised its orders for the Duo. A post on r/AppleWhatShouldIBuy called “The iPhone Duo reviews just made me cancel my order” leads with the apps: “Dealing with black bars on the sides when apps are open? I honestly can’t accept that.” Under MKBHD’s video, one commenter is “holding off on buying the duo” because “Apple did the developers so dirty in giving them the SDK so late”.

The most viewed post about canceling I found on X, Daniel Berk’s “I canceled my iPhone Duo preorder.” with more than 8 million views, quotes MediaStorm’s test of the Duo after 10,000 folds. The apps only came up in his follow-up. And a poll on the MacRumors forums asked who’s canceling now that reviews are out:

78%

No! It's everything I expected and more

197 votes

Yes! The reviews changed my perspective

33 votes

Unsure, I'm waiting on user reviews once it launches

24 votes

That’s 33 people on an enthusiast forum who chose to vote. GadgetReview says the claims of canceled orders “should be treated as individual reactions rather than a confirmed pattern”. And 9to5Mac reported on October 22, citing DigiTimes, that Apple raised its Duo orders by more than 40% on strong demand, from 9.7 million to 14 million units for the first year.

Relations means relationships

In 2020 I wrote that what gets me on a plane to speak at a conference “is really only love” and that my favorite part is “the conversation”. In my ConFrontJS talk in 2022 I said “we really see ourselves as servants of our users”. On a platform the users are developers. I think serving them means showing up early and in person, before you need anything from them.

Apple’s evangelists did that in Berlin with a phone nobody could buy yet. Somebody at Apple reached out to Graham before his update shipped and he found that rotation bug before any of his users did.