Elon Musk is seemingly done attacking Apple over its decision to integrate ChatGPT into iPhone features.
Back in 2024, when the partnership was first announced, Musk slammed the integration as an agreement from Apple to let OpenAI install “creepy spyware” on users’ devices. The next year, he sued, claiming the partnership gave the firms a “monopoly” on Apple users’ AI prompts, which allegedly harmed competition in both smartphone and chatbot markets.
For Musk, the fight with Apple seemingly escalated after he believed that his chatbot, Grok, was perhaps being illegally blocked from topping Apple’s App Store rankings. Last August, he claimed that “Apple is behaving in a manner that makes it impossible for any AI company besides OpenAI to reach #1 in the App Store, which is an unequivocal antitrust violation.”
A Google começou a alterar os resultados de pesquisa na Europa para cumprir com o DMA da UE, mas avisa que a experiência dos utilizadores vai piorar, e os custos para empresas locais vão subir.
The Schiller exit is a bit more notable. Unlike Maestri, he still had a real job: The veteran executive ran the App Store and Apple Events. The App Store portion alone is no joke. It generates an estimated $30 billion a year and can be very challenging to manage. Apple’s app marketplace is loved by many consumers, but often criticized by developers and subjected to increasingly onerous regulations. It was a busy, all-encompassing gig and nowhere near a semiretirement.
[…]
But there’s a bit more to the story, I’m told. Ternus and services chief Eddy Cue want to make even more money from the App Store and figure out ways to raise margins and squeeze additional recurring revenue from the platform. Schiller, on the other hand, seems to believe that such moves will only further irk developers and governments. While there was no internal blowup or anything like that, it’s something he wanted no part of.
“Product guy” dreams about margins, forgets that people buy Apple hardware because of the software.
Apple admitted during its July earnings call that regulatory changes have started to weigh on its Services growth. Apple reported services revenue of $30.7 billion for the June quarter, a record for the period but short of the $31.4 billion that analysts expected.
New iPhone colors could give Wednesday’s launch an immediate visual refresh, with Dark Cherry and lighter blue finishes among the shades rumored for the iPhone 18 Pro generation. But replacing Cosmic Orange in the promotional photographs would leave an uncomfortable question behind: what happens to customers whose orange iPhone 17 Pro has reportedly turned pink?
Owners have posted accounts of discoloration on Reddit and Apple’s own community forum. Some describe receiving replacement devices; others say their requests were rejected as cosmetic issues. The reports establish a reason for scrutiny, although they do not establish how frequently the problem occurs or whether every affected phone shares the same cause.
Apple does not appear to have published a dedicated technical explanation or a general service program addressing these complaints. With another generation approaching, the company has an opportunity to explain what owners should expect from the finish on an expensive phone—and from support when that finish changes.
The iPhone Colors Expected This Week
The most consistent iPhone 18 Pro rumors center on Dark Cherry, sometimes described as burgundy or deep red, and Sky Blue, also called Light Blue. The neutral option remains disputed.
According to the latest color-leak roundup, Sonny Dickson shared an image of alleged SIM trays suggesting Silver, Dark Cherry, and Sky Blue. A separate claim from Fixed Focus Digital points to Black taking Silver’s place.
That leaves a plausible three-color lineup without agreement on all three finishes. The names also remain unofficial; a supplier’s description does not necessarily become the name displayed in the Apple Store.
The same reporting favors black and white for the foldable iPhone Ultra. A purported reddish version lost credibility after Mark Gurman identified the images associated with it as Xiaomi renders, and the post sharing them was subsequently deleted.
Cosmic Orange is absent from these leading launch rumors. Its possible departure would fit the annual rotation of signature shades, but there is no evidence that Apple is changing colors because of the discoloration complaints.
For buyers, the distinction is straightforward: a new shade may make the next phone look different. Its name cannot establish that its finish will age better.
Image Credit: Apple Inc.
Cosmic Orange Owners Have Described Different Outcomes
One detailed Reddit replacement account describes an iPhone 17 Pro camera plateau turning pink approximately two weeks after purchase. The owner said the rest of the phone was protected by a case and denied using bleach, peroxide, or other treatments to produce the change.
According to that account, Apple Support escalated the case and supplied a warranty replacement without initially identifying the cause. The owner posted comparison images and later said an engineer contacted them after receiving the original phone, asking questions about usage and environmental conditions.
That reported follow-up complicates any claim that Apple has ignored every customer. At least some owners describe service and further investigation.
A separate Reddit complaint about a salmon-pink camera plateau describes a less satisfactory experience. The owner said the change became noticeable after several months and continued to develop. They reported being directed toward cleaning guidance and told that assistance would be outside warranty coverage, despite saying they had used only a microfiber cloth.
These accounts are owner testimony, not independently inspected service records. Different histories or inspection findings could explain different decisions. Even so, they expose the uncertainty customers face when trying to understand whether a changing finish is considered wear, external damage, or a possible manufacturing problem.
Someone seeking help should not have to reconstruct an unofficial support policy from strangers’ experiences.
Apple Community is a customer discussion forum hosted by Apple. A complaint appearing there is evidence that an owner raised the issue publicly; replies from community participants do not amount to an official engineering finding or company statement.
The posts also cannot tell us the failure rate. A forum collects people who have a reason to speak, and the same incident can circulate through multiple websites. Counting photographs, comments, or reposts would not produce a reliable estimate of affected devices.
But the absence of a reliable denominator should not make individual complaints disappear. A customer does not need to demonstrate that thousands of other phones have changed color before their own device deserves an inspection and a reasoned response.
The unresolved issue is how Apple distinguishes those cases and communicates the result.
Image Credit: Apple Inc.
Cleaning Guidance Is Not a Diagnosis
Apple’s official iPhone cleaning instructions advise against products containing bleach or hydrogen peroxide. They recommend appropriate gentle cleaning methods and warn against abrasives and several categories of household cleaner.
That guidance is useful for protecting a device. It does not establish that prohibited cleaning products caused every Cosmic Orange complaint.
Some owners expressly deny using those substances. Their statements cannot rule out every possible exposure, but a general warning cannot substitute for examining what happened to a particular phone.
Suggestions involving sunlight, chemical reactions, or variations in the finish’s protective treatment continue to circulate. None should be presented as the universal explanation without testing that connects the proposed cause to the reported changes.
A credible public response could explain whether Apple has identified a recurring mechanism, whether certain production periods require attention, and what service teams should examine. If the company concludes that several unrelated causes are involved, that would also be useful information.
The current uncertainty leaves customers debating material science when they should be able to ask a much simpler question: why does this phone no longer look like the one they bought?
A Premium Finish Is Part of the Product
Color is something Apple asks customers to choose deliberately. It receives prominent space in launch presentations, retail displays, advertising, and the ordering process. Buyers coordinate cases and accessories around it, and some wait for a particular finish to become available.
It is reasonable to expect that choice to survive ordinary use.
Normal wear exists, and no finish should be described as indestructible. Scratches, impacts, and chemical exposure can alter a device. A reported change from orange to pink, however, warrants an explanation rather than an assumption that every visible change belongs in the same category.
The financial stakes are also difficult to quantify responsibly. There is no verified public count of affected Cosmic Orange devices, no established failure rate, and no disclosed average remediation cost. Those gaps prevent a credible estimate of billion-dollar exposure.
The purchase value of potentially affected phones would not equal Apple’s repair liability in any event. A repair, replacement, refund, and lost future sale are different costs.
The more immediate commercial concern is confidence. A customer who receives a satisfactory explanation may accept a service decision even when it is disappointing. A customer who feels dismissed may carry that experience into their next purchase—and into conversations with other buyers.
New Colors Need Evidence That Lasts Beyond Launch Day
Dark Cherry could become the finish most associated with the iPhone 18 Pro. The Ultra’s rumored neutral palette could place greater attention on the foldable design itself. Neither possibility tells us how those surfaces will look after months in pockets, cases, cars, and everyday handling.
Early product photographs will help buyers judge appearance. Longer ownership will reveal whether the finish retains it.
For existing Cosmic Orange owners noticing a change, documenting the phone under consistent lighting is a useful first step. Images taken on different days can help distinguish a developing alteration from reflections or camera white balance. Photographs of the complete device can also show whether the change is limited to exposed areas.
Keeping the purchase receipt, support case number, and written inspection outcome makes subsequent conversations easier. If service is declined, the useful question is what finding led to that decision and whether the device was assessed for a possible materials or workmanship issue.
A new color announcement will not supply those answers to someone still holding the previous generation.
Apple is facing a £2 billion ($2.7 billion) London lawsuit brought on behalf of app developers over its app tracking rules, with the iPhone maker accused of abusing its power to unfairly impose greater restrictions on third parties.
[…]
Lawyers bringing the new lawsuit against Apple, though, say the feature imposed stricter requirements on third-party app developers than on Apple’s own services, giving its advertising ecosystem a competitive advantage.
The latest lawsuit has an interesting twist: it’s being brought by Ann Pope, who was previously a senior official with the regulator behind today’s case.
The company told Reuters it was “bound by the exact same requirements as all developers.”
However, regulators across Europe including in France, Italy and Poland have investigated ATT. Germany’s competition regulator, the Federal Cartel Office, last month determined that Apple was favoring its own apps over those from external developers.
The EU is saying “you’re big enough that you have to treat your other business models like third parties” and Apple replies with “but we know we’re solid, so that makes no sense!”
Apple has agreed to make changes to its App Tracking Transparency feature in Germany, according to the country’s competition regulator.
[…]
In Germany, Apple has agreed to remove “possibly discouraging symbols and wording” from the App Tracking Transparency prompt, the regulator said. Apps will also be “given more scope to explain to users what significance personalized advertising has for their offering and their business model,” and the “freedom to combine the consent request required by Apple with the consent requests required under data protection law.”
The FCO’s objection appears to be that Apple’s existing prompt is making app tracking sound scarier than it really is. The iPhone maker will make eight changes in order to address this – including removal of the word “track.”
The regulator helpfully offers an illustration of the differences between these prompts on the fourth page of its FAQs (PDF) about the case. There are many things they say could be deterrents in the App Tracking Transparency dialog, and I do not think Apple would deny that they are suggesting that users opt out of tracking. The definition of “tracking” Apple uses is self-serving, which would not matter so much if it did not also have a parallel desire to grow its advertising business.
[…]
A particularly damning finding in that comparison, to my eyes, is the way Apple puts “Ask App Not to Track” as the topmost button in the App Tracking Transparency dialog, but puts the option to “Turn Off Personalised Ads” at the bottom of it its own advertising prompt.
A Rust issue opened August 21 (and now closed) noted that Rust 1.98 emits a zero method entry in a compiler-generated vtable, resulting in a segmentation fault and a crash. According to the Rust 1.98.1 release notes:
In Rust 1.98.0, in some circumstances, rustc would incorrectly generate a trait object vtable with a null pointer where a function pointer should be. This leads to undefined behavior in the emitted code. In some cases this may “just” cause segfaults due to the null pointer being loaded, but it is possible for it to be justification for arbitrary effects.
This bug is fixed in Rust 1.98.1. The Rust 1.98.0 release brought algebraic methods for addition, subtraction, multiplication, division, and remainder to floating-point types, allowing optimizations on these operations using algebraic properties of real number.
Users of a previous version of Rust installed via rustup can install Rust 1.98.1 by running the command rustup update stable. The Rust team asks developers who would like to help test future releases to consider using the beta (rustup default beta) and nightly (rustup default nightly) channels and to please report any bugs.
A US federal judge has sided with Google, ruling that the company will not have to sell its online advertising exchange (previously known as AdX). The US Department of Justice (DOJ) sought this remedy in the long-running ad tech antitrust trial, which Google lost in 2025. However, the remedies imposed upon Google for that loss are shaping up to be minimal.
[…]
While divesting the ad exchange would have been the most serious penalty, the government also asked for fines and court-ordered changes to Google’s business practices. It’s likely that the DOJ will get a lot of that, but we don’t know the specifics yet. Judge Leonie Brinkema has sealed the order for 14 days, giving the parties a chance to request redactions.
[…]
After all these years of hearings, appeals, and decisions, Google’s market power will remain largely unchanged going forward.
The settlement between Google and Epic that aimed to put to rest the companies’ long-running antitrust battle is being withdrawn, and that means third-party app stores are coming to the Play Store.
[…]
While Apple suffered little penalty in its Epic case, Google was tripped up by its anti-competitive management of the supposedly open Android ecosystem. Google used its market position to discourage device makers from promoting or pre-loading non-Google app stores and attempted to hide that conduct. The remedies set by Judge James Donato included lower fees, mirroring Google Play apps in other stores, and most vitally, placement of alternative app stores in Google Play.
[…]
Google and Epic were set to return to court on July 16 to argue in favor of the settlement. However, the writing may have been on the wall. In a recent expert analysis provided to the court, MIT economics professor Nancy Rose noted that the settlement was “unlikely to enable Google Play’s potential competitors to overcome their long-standing network-effect disadvantage in a timely manner.”
[…]
Under the terms of Judge Donato’s original injunction, these stores will have access to the full catalog of Google Play apps by default. […] Google will also require approved stores to block malware, respect intellectual property, and include mechanisms to update and uninstall apps.
The team behind the rustup installer for the Rust programming language has released an update to the command-line utility.
Announced September 1, rustup 1.29.1 improves concurrency in two rustup operations, according to the Rustup Team. Now, when running rustup update, rustup will first check for possible updates in parallel. And when running rustup component add with multiple components, the components now will be installed concurrently.
The rustup 1.29.1 update also re-enables implicit installation, which was removed with rustup 1.28.0. However, implicit installation of the active toolchain in rustup-init and rustup invocations has been deprecated and will now produce a warning. In versions 1.27 and earlier, rustup would implicitly install the active toolchain if it was found missing whenever rustup was invoked. This behavior could not be disabled and had become a source of confusion, the Rustup Team said. Developers now can control it with the RUSTUP_AUTO_INSTALL environment variable or the rustup set auto-install command, the team explained in a blog post.
Elsewhere in rustup 1.29.1:
rustup doc now supports the --serve flag, which allows serving the docs over local HTTP. This should help users with containerized browser or rustup setups.
Installing i686-pc-windows-* host toolchains on 64-bit Windows now requires --force-non-host.
rustup-init will no longer leave unexpected files on disk after cancelled installations.
A bug that could cause Windows installation to fail when using rustup-init.sh has been fixed.
“Target triple” has been renamed to “target tuple” across the project to reflect the new terminology.
An August 20 update to the Rust language brought algebraic methods for addition, subtraction, multiplication, division, and remainder to floating-point types, allowing optimizations on these operations using algebraic properties of real number.
A US federal judge has sided with Google, ruling that the company will not have to sell its online advertising exchange (previously known as AdX). The US Department of Justice (DOJ) sought this remedy in the long-running ad tech antitrust trial, which Google lost in 2025. However, the remedies imposed upon Google for that loss are shaping up to be minimal.
In this case, the DOJ and a coalition of states sought to prove that Google leveraged its immense market power in online display ads to reduce the reach of competitors. Government lawyers argued that Google had "rigged" ad auctions to give itself an advantage. While the court agreed that Google illegally locked publishers into using its exchange, it did not agree that Google had broken the law when it came to the tools used by advertisers.
Despite the mixed ruling, the DOJ argued during the remedy phase that forcing Google to sell its ad exchange, which facilitates connections between ad buyers and sellers, was the best way to level the playing field. But that won't happen. While the ad exchange represents a relatively small part of Google's revenue, forcing the company to sell may have sent ripple effects through the rest of its ad business. It would also have been a powerful message to Big Tech firms, which have successfully knocked back a recent wave of antitrust cases.
These changes resolve Apple’s disagreements with the Commission over business terms and alternative distribution. They also reduce complexity by moving every developer that distributes apps in the EU to a single set of business terms.
[…]
The Core Technology Fee, a per-install fee for developers that achieve extraordinary scale, will be replaced by the Core Technology Commission, a simple 5 percent commission on digital transactions in apps distributed outside the App Store. The new terms also eliminate the initial acquisition fee and store services fee.
[…]
Under the updated terms, developers can now offer Apple In-App Purchase alongside alternative payment options, which had not previously been permitted in the EU.
[…]
Apple is also expanding who is eligible to operate an alternative app marketplace or distribute apps via the web in the EU.
[…]
Apple will continue to require every alternatively distributed app to go through Notarization[…]
Apple will charge a 26% fee for apps distributed through the App Store that use in-app purchase.
[…]
Apps in the App Store that use in-app alternative payment processing will pay 20%.
[…]
Apps that link to a website purchase option will pay 15%.
Apps using Web Distribution or App Marketplaces would pay the 5% CTC (and report transactions). I like that the new terms are simpler and that the fees are slightly lower, but it seems like the EU got tricked or surrendered here.
This is bonkers, I can’t believe the EU Commission agreed to it. The main issue that the DMA was about still remains: Apple retains ultimate control over app developers’ dealings with users.
The status quo that the EU should have pushed for, and which Article 6(7) of the DMA requires, is one where a developer can distribute iOS apps to users without ever entering into any contractual relationship with Apple.
All in all, still extremely anti-consumer. If I can download and run arbitrary code on my Mac--even if I have to jump through scary warnings--why should I not be able to do so on my phone? Why would one computing platform be different from the other?
However, while Apple hopes it will be allowed to charge these lower commissions, it has admitted in a new regulatory filing that it may not be allowed to charge any commission at all on purchases made through third-party app stores and other external platforms.
The commission Apple earns from the App Store is shrinking in markets where it has been forced to relax its grip on in-app purchases, based on new analytics data.
Notably, this isn’t a proposal, it’s the announcement of actual changes that Apple will implement (starting October 1) after “close collaboration” with the EC. And lest we think Apple is overplaying that last aspect, that group gave a statement to Bloomberg backing up the assertion[…]
[…]
This feels like mainly a way to keep the all-important big gaming fees – which make up most of in-app payments, and as such, most App Store fees – mostly intact.
[…]
It sure looks like Apple knew this EU deal was coming down the pike and that the bloc agreeing to their terms would bolster the case that these are “fair”. The US judge still gets to decide that, and Epic has already pushed back as Apple seeks to negotiate directly. One big reason for pushing? Epic wants to ensure any changes Apple tries to negotiate be put in place for all developers.
The European Commission has since confirmed that it approves of Apple’s changes to its App Store policies, giving a statement to the Irish Independent[…]
Epic Games, a longstanding critic of Apple’s App Store practices, called the scheme “junk fees,” adding that the plan did “nothing to open up the mobile app ecosystem to competition, as required by Digital Markets Act.”
“The law makes it clear that Apple must allow developers to offer link outs to the web for purchases ‘free of charge’ and has to allow ‘effective use’ of competing stores,” the company wrote.
I hope this isn’t the end of DMA. Apple taking a cut of out-of-store apps revenue makes as much sense as app developers taking a cut of iPhone revenue.
[…]
And also I still want to live in a world where anyone can write a program and run it on the devices they own and send it to friends, without having to pay $100/year of developer account and do the whole notarization thing (which considering the amount of scam in the app store we know is pretty useless in terms of security). Not everybody is a professional programmer, some people are just doing programming as a hobby, some are also young people that don’t even own a credit card yet.
I have refused to sign any of Apple’s EU DMA agreements thus far, because I think they are illegal, and they have been optional.
I still think their new terms are illegal — they don’t meet the minimum requirements of the DMA, and will not be approved by stakeholders — but they are no longer optional, so the choice now becomes accept the updated developer agreement or stop being a developer.
Thanks to the DMA’s sprawling scope, complexity, and overreach, Apple came out of this conceding only 4 percent of the App Store’s 30 percent commission, and no reduction at all to the 15 percent for subscriptions after the first year.
The CTC is preferable to the CTF in much the same way that a fire burning down your kitchen is preferable to a fire burning down your entire house.
[…]
The Digital Markets Act was introduced to ensure that sideloading would be an available alternative, to essentially force open platforms that have been closed. Debates about the wisdom of this notwithstanding, in the biggest case, and up until recent developments in Android app marketplace governance also only case, it has failed to deliver the promises that were the entire point of the law.
I’m sure some of you think I’m all wet in my argument that the point of the DMA was merely to impose ongoing bureaucratic complexity. But my view jibes with the reality of how it’s worked out.
In other words, maybe we who had high hopes were the ones who got tricked, not the EU Commission.
I don’t recall seeing POSIWID before, but I love the concept. A friend sent this to me, with the quip that I forgot to include a link to it in my “What Is the Point of the DMA?” piece this week. Indeed, it encapsulates my arguments about the DMA specifically and the European Commission generally. The purpose of the DMA is what it does, not what you imagine it is intended to do.
I admit to being primed by seeing Jeff Johnson’s post, but I’m certain that my mind would anyway have immediately gone to our favorite scam promoting toll booth, the place that “gives people around the world a safe and trusted place to discover apps that meet [Apple’s] high standards for privacy, security, and content.”
Also consider which apps have to pay the toll and which ones show their own ads for free.
Apple has again failed to earn a stay for fee calculations in its ongoing legal fight with Epic Games. Apple's case will be heard by the Supreme Court in the term that begins in October, and Apple asked the U.S. District Court for the Northern District of California to pause proceedings until then, but the court said no [PDF].
U.S. Supreme Court Justice Elena Kagan today granted Apple a one-day stay in its legal fight with Epic Games, giving Apple more time to outline the fees it wants to charge developers for linking out to purchase options on the web.
Apple tried to freeze the entire thing while they appealed to the Supreme Court – and the Supreme Court denied the freeze. But they didn’t deny hearing the case – yet. That’s why they’re pausing the proceedings for now (after Judge Gonzalez Rogers denied the same request), while they weigh Apple’s appeal. But before they do that, they’re basically likely to decide today – again, it was just a 24-hour delay – whether they should grant a longer stay. Presumably if the court thinks they’re unlikely to hear Apple’s appeal, they may not grant that longer stay. Or if they think Apple filing their number won’t harm their business, they’ll let it proceed. But Apple will argue that if the longer stay isn’t granted, it will cause major harm to their business because again, it will effectively end the App Store cut as we know it.
Apple today submitted a court-ordered proposal outlining the commission it believes is reasonable to collect from U.S. apps that link to purchase options outside of the App Store.
Apple is asking for half of its commission on standard apps, so apps that would pay 30 percent for an in-app purchase would pay 15 percent when linking to a web purchase option. Small Business Program participants that would normally pay 15 percent would pay 5 percent.
[…]
The appeals court suggested the commission could be limited to the direct costs of facilitating link-outs, and under that approach, the fee would be zero. Apple says a zero commission would not reflect the value that it provides developers, and its suggested commission gives it fair compensation for the App Store platform.
[…]
The district court will now evaluate Apple’s fee proposal and hear a response from Epic Games , and Apple will need to implement the fee the court sets.
Unlike cost-only based commissions, Apple’s revenue-based commissions incentivize
continued investment. Apple charges developers a $99 annual fee for the Apple Developer
Program. May 17, 2021 Trial Tr. at 2762:21–2763:13. This modest fee—designed to prevent fraud
and expressly not intended to compensate Apple for the use of its IP-protected tools, technologies,
and services (id.)—allows developers to build apps using Apple’s offerings and deliver experiences
to iOS and iPadOS users worldwide.
The annual developer fee is nominal. Apple relies on percentage-based commissions to
recoup and profit from its investments. See id. ¶¶ 87–93. Apple is incentivized to invest in IP-
protected tools, technologies, and services that generate revenue for developers (and benefit users).
[…]
Dr. Carlton explains that “reduc[ing] Apple’s incentive to invest and provide the technology and services that benefit users and developers” would harm users and developers, as well as Apple.
I like the part where Apple’s expert argues that its normal commission rates are so high that it would still be profitable for developers to pay the proposed linking commissions on top of what they would pay to Stripe or Paddle. In other words, paying Apple for “IP” almost twice what it admits the other companies charge for “full-service, turnkey payment processing.”
If the point [of the $99] is just to prevent fraud, why do we need to keep paying $99 yearly FOREVER? Is 10 years not enough to prove I’m not a fraud?!?
If the fee doesn’t help pay for Apple IP, then it’s even more blatantly unfair that a minority of apps have to pay for ALL apps to access Apple IP. Free apps, no matter how big or how much $ they make via ads, get access to Apple IP from OUR REVENUE CUT, and not even their $99 counts.
That’s what that enormous hardware margin from customers is already supposed to be paying for — Apple IP! In the early 00’s, I gladly paid the “Apple tax” (PowerBook G4) to get access to the Mac OS X software/ecosystem, including all the Unix and dev tools. I’m not sure why anyone thinks that double-dipping is fine on all the non-Mac platforms, App Store or not.
Schiller’s [previous] testimony about the previous program is extremely misleading, because the new program began in 2008 at the same time as the App Store, so there was no previous iOS developer program, and Mac Developer ID did not begin until 2012, so Apple Developer Program membership was not actually required to distribute Mac apps!
I want to quote another remarkable passage from Schiller’s testimony, again with questions from Apple’s own lawyer.
Q. And Mr. Jobs says, “And also just to make it a little
clearer, we don’t intend to make money off the App Store. I
mean, we don’t make a lot of money off iTunes, and the split
with the music companies is about the same, so in the case of
the iTunes Music Store, we give all the money to the content
owners, and we are basically giving all the money to the
developers here. And if that 30 percent of it pays for
running the store, well, that will be great, but we just want
to create a very efficient channel for these developers to
reach every single iPhone user.”
Is that a statement that Mr. Jobs made back in March 2008?
A. He did.
[…]
I won’t quote the following passage in which Schiller testifies about his internal email suggesting that Apple limit itself to $1 billion per year in profit from the App Store, hand-waving away the suggestion as merely “spurring conversation.” Of course the email also seems to contradict Schiller’s (absurd) testimony that Apple does not specifically calculate profit from the App Store, only company-wide profit. Apple’s public financial statements also appear to contradict Schiller’s claims.
On the same day, Apple submitted another motion, asking Judge Gonzalez Rogers to order the parties to attend a settlement conference.
[…]
Epic has now responded to Apple’s motion, stating that although the company “has been, and remains today, willing to entertain any direct approach from Apple with a serious settlement proposal that would introduce competition and benefit all developers,” it “does not believe the prospects of such settlement would be meaningfully advanced through referral to a settlement conference at this juncture.”
In addition to the proposal itself, Apple submitted supporting expert reports, alongside a request to seal portions of those filings containing financial data, link-out adoption estimates, developer survey results, and other information Apple considers commercially sensitive.
Epic has now filed an opposition to Apple’s request, arguing “Apple again seeks to conceal information from the public and unnecessarily hamper proceedings.”
The panel examines a Bluetooth-related earbuds vulnerability, debating whether the issue lies in the protocol or Apple’s proprietary pairing approach, and why the implications feel unsettling. Chuck Joiner, David Ginsburg, Eric Bolden, Ben Roethig, Marty Jencius, Jim Rea, Jeff Gamet, and Guy Serle also touch on a useful tool born from a creator’s own workflow before turning to another LastPass incident and where it puts them on the trust spectrum.
At Flip The Script, Grant Belaire, Chief Marketing Officer for MacPaw, discusses how the company approaches AI, app discovery, and developer support through their trusted products like CleanMyMac, Setapp, Moonlock, and Clear. He explains why AI should be useful rather than forced, how Setapp balances customers and developers, and why long-term commitment matters in building successful app marketplaces.
The Road to Macstock takes a serious turn as Mike T. Rose previews his workshop on becoming a digital caretaker for family members and loved ones. Mike discusses scams targeting older adults, password sharing, remote support, Apple Passwords, financial preparedness, and the need to balance protection, respect, independence, and trust when helping others manage their digital lives.
Google began offering third-party app store downloads in the Play Store earlier this week, but US District Judge James Donato says the company isn't doing enough. After reviewing the process for accessing the first non-Google store, Donato ruled that Google has added unnecessary "anticompetitive friction," ordering the company to rectify the issues.
While Epic and Google are patching things up with a global partnership agreement, the two are still on opposite sides of the antitrust case in the US. Google lost the case in 2023, and the intervening years have been about determining how to implement remedies to address Google's anticompetitive behavior. One of the court's key elements is the requirement that Google include third-party app stores in the Play Store, giving users an easy way to get apps from non-Google sources. Aptoide Games became the first such app store recently.
However, Google worked hard to avoid this outcome, attempting to settle with Epic to keep third-party app stores out. When it was forced to admit the Aptoide store under the terms of the ruling, Google didn't exactly put up a banner welcoming third-party app stores. In fact, Judge Donato found in a Thursday hearing that Google's implementation was not good enough, according to The Verge.
A new day has dawned in the Play Store, and it's one that Google tried very hard to avoid. The first third-party app store has arrived in Google Play as a result of the long-running antitrust lawsuit with Epic. Those in the US can now head into Google Play and download Aptoide, a game-focused store that has been available as a sideloaded client since the early days of Android.
Forcing Google to distribute third-party app stores in Google Play was one of several remedies imposed by Judge James Donato after Epic emerged victorious in 2023. The remedies also included lowering developer fees, mirroring Google Play apps in other app stores, and allowing developers to use alternative payment systems. But it was the app store stipulation that seemed to irk Google the most.
Google almost avoided this outcome when it agreed to a settlement with Epic, which was announced early this year. Under the terms, Google would certify third-party app stores to allow users to install and use them with less friction, but it would not host them in Google Play. However, Google and Epic withdrew the settlement when it appeared the court would not approve it. This Registered App Store program is still slated to launch internationally, but in the US, Google is only doing what it must to comply with the judge's orders.
A new day has dawned in the Play Store, and it's one that Google tried very hard to avoid. The first third-party app store has arrived in Google Play as a result of the long-running antitrust lawsuit with Epic. Those in the US can now head into Google Play and download Aptoide, a game-focused store that has been available as a sideloaded client since the early days of Android.
Forcing Google to distribute third-party app stores in Google Play was one of several remedies imposed by Judge James Donato after Epic emerged victorious in 2023. The remedies also included lowering developer fees, mirroring Google Play apps in other app stores, and allowing developers to use alternative payment systems. But it was the app store stipulation that seemed to irk Google the most.
Google almost avoided this outcome when it agreed to a settlement with Epic, which was announced early this year. Under the terms, Google would certify third-party app stores to allow users to install and use them with less friction, but it would not host them in Google Play. However, Google and Epic withdrew the settlement when it appeared the court would not approve it. This Registered App Store program is still slated to launch internationally, but in the US, Google is only doing what it must to comply with the judge's orders.
Login
