Archive for May 6, 2025

Tuesday, May 6, 2025

External Purchasing From the Kindle App

Andrew Liszewski:

Contrary to prior limitations, there is now a prominent orange “Get book” button on Kindle app’s book listings.

[…]

Before today’s updates, buying books wasn’t a feature you’d find in the Kindle mobile app following app store rule changes Apple implemented in 2011 that required developers to remove links or buttons leading to alternate ways to make purchases. You could search for books that offered samples for download, add them to a shopping list, and read titles you already own, but you couldn’t actually buy titles through the Kindle or Amazon app, or even see their prices.

Hartley Charlton:

This is the first time since the enforcement of Apple’s in-app purchasing restrictions that Kindle users on iOS have had a direct route from the app to Amazon’s store. Previously, the lack of in-app purchasing or even external linking meant users had to manually search for titles in a separate browser session.

I’ve discussed the iOS-Kindle timeline before, but as a refresher: Apple used to allow non-IAP purchasing directly within the Kindle app, with no fees, even though Tim Cook told Congress that, “since the App Store debuted, we have never raised the commission or added a single fee.” After all these years and court hearings, the situation is still a regression because Apple no longer allows the purchase to happen within the app.

Dan Moren:

Honestly, I’m not sure I ever thought I’d see the day. I confirmed this for myself: clicking the Get Book link takes you out to Safari to the page for the book on Amazon’s site. No muss, no fuss.

Notably, this is the Kindle app, not the Amazon app. In the latter, you still—for the moment—see a note that “this app does not support purchasing of this content.” I’m intrigued as to why Amazon chose to do one but not the other—I rarely open the Kindle app unless I already have a book I’m reading; it’s the Amazon app I turn to for shopping.

Out of curiosity, I checked Kobo’s app as well, which acts as both the reader and storefront for that site, and there’s now a Get Book link there as well, though it pops up a separate panel and shows Apple’s (now prohibited) scare screen about leaving the app and going to an external website.

Ruffin Bailey:

Kindle iOS kicked me to Safari, which I keep in private mode, and the “Buy with one click” button is activated.

Okay, well shucks. Upon further review, apparently I don’t usually pay much attention to that button, because it’s always active, even if you’re not logged in. Click it and it asks you to sign in.

But I wouldn’t expect that to last long. Right now it looks like Amazon is only adding ref_=rekindleDP&nodl=0 to the URL, but they could add a unique, one-use GUID to the link and, with only a little risk to themselves (oh no! we gave away 200k worth of bytes to the wrong person!), make the button “live” immediately.

Adding a one-use, unique “buy now token” would make it easier to buy using Kindle than Apple’s own Books.

John Voorhees:

I expect other companies will follow Amazon and Spotify’s leads in the coming weeks. Although Apple has appealed Judge Gonzalez Rodgers’ contempt order, the Judge declined to stay its enforcement during the appeals process. It’s always possible an appeal could force Amazon and others to undo changes like this, but I think a more likely outcome is that an appellate court allows Apple to charge a fee where Judge Gonzalez Rodgers wasn’t – one that’s lower than the 27% that got Apple into trouble in the first place.

Previously:

Update (2025-05-07): See also: Hacker News.

M.G. Siegler:

It sounds like I’m making fun of Amazon, but really, I’m making fun of Apple. Because while Amazon did make a choice not to include such a button in their app, Apple really gave them no choice. Given the agency model used in this particular category, there was simply no way for Amazon to make the economics work. Even raising prices would just send more money to the publishers — and to Apple.

[…]

Apple should obviously — obviously — have made the change that Judge Gonzalez Rodgers forced upon them years ago. But why would they? There was money to be made and there was no indication that such stupidity from a pure product perspective was harming iPhone sales.

John Gruber (Mastodon):

But really, this whole situation with e-books has been the best argument against Apple’s App Store policies for at least the last 15 years. […] Apple’s App Store policies therefore make it impossible for a third-party bookseller to sell e-books and make even a penny of profit.

[…]

Apple’s obstinance on this has created nothing but friction, confusion, and hassle for users for 15 years. It makes no sense for anyone.

[…]

But at some point Apple should have just considered their own users. If their users are using the Kindle app looking to buy Kindle e-books on iOS devices, Apple should have just let it happen on the web — and used that as motivation to make Apple Books better so that maybe more users would prefer it to the Kindle ecosystem. What’s the word? Oh yeah ... competed.

PayPal Contactless iPhone Payments

Juli Clover:

PayPal today announced that it is planning to debut contactless payments in Germany, allowing German iPhone users to make tap-to-pay purchases in stores using their PayPal accounts.

PayPal is able to offer this feature because Europe’s Digital Markets Act has forced Apple to open up the NFC chip in its devices to third-party apps. NFC payments are available in apps without the need for Apple Pay or the Wallet app, allowing third-party payment services and banks to offer their own tap-to-pay solutions on Apple devices.

Previously:

Retrospective on Reverse-Engineering a Tiger Bug

Rosyna Keller (Mastodon, tweet):

At the time, Apple only allowlisted specific menu extras by class name (checked in -[SUISStartupObject _canLoadClass:]). Any attempt to load a menu extra that advertised a different class name in its Info.plist’s NSPrincipalClass entry would fail. Menu extras were first-class citizens. You could hold the Command (⌘) key down to move or quit them. They loaded automatically and needed no backing application. This sent lots of developers looking for workarounds to Apple’s allowlist, as they wanted these features for their own menus.

Some developers would steal one of the allowlisted class names for their menu extra plugin. This was unwise. The Objective-C runtime only allowed one class instance with a specific name to be loaded at a time. When it found duplicates, the one it chose was an implementation detail that could cause unexpected crashes. Favorite choices of class names to hijack included AppleVerizonExtra or IrDAExtra, i.e., something a user isn’t likely to have enabled. In the rare case someone did enable these, or if more than one developer chose to steal the same class name, all hell could break loose.

This was the impetus for Menu Extra Enabler. It was an old-style InputManager plugin that automatically loaded into SystemUIServer when installed and overrode the -[SUISStartupObject _canLoadClass:] instance method to return YES unregardless of what class name was used for the menu extra’s principal class.

[…]

I’m desperately looking for any assistance that can be provided. Specifically, I need some temporary help to afford the health insurance and rent. […] My ultimate goal is to find some contracting work for macOS/iOS where I can use my reverse engineering and bug fixing/finding/working around skills. I miss figuring out how things work, something I could do in spades while working on macOS Notarization at Apple.

Previously:

Sharon Zardetto Aker, RIP

Adam Engst:

Sharon started writing professionally about the Macintosh at its inception in 1984, with articles in the earliest issues of Macworld and the premiere issue of MacUser. She contributed to The Macintosh Bible for its second edition in 1989, served as the lead author/editor for the third edition in 1991, and reprised that role for the 1,000-page seventh edition in 1998. In between, she also wrote The Macintosh Companion: The Basics and Beyond, collaborated on two editions of The PowerBook Companion with her husband Rich Wolfson, edited The Macintosh Dictionary, and penned The Mac Almanac. Throughout the 2000s, she continued as a columnist for Mac magazines, ultimately writing nearly a thousand articles, including one in the final print issue of Macworld.

Although mentions of Sharon in TidBITS date back to when I first read The PowerBook Companion (see “Travels with Charley,” 16 November 1992), we began working together around 2006, when she wrote Take Control of Fonts in Mac OS X and its companion volume, Take Control of Font Problems in Mac OS X. She thrived as a Take Control author, writing books about Safari, iBooks, and Numbers, and contributing TidBITS articles on similar topics.

[…]

I’ve never met anyone as insatiably curious and communicative about software as Sharon. She didn’t just want to know how an app worked; she wanted to tell everyone about it. She couldn’t open an app without poking at every menu and every button, and then asking, “What happens if you hold down the Option key while…?” Sharon never met a keyboard shortcut she didn’t like, and she lived to unearth those that didn’t reveal themselves in the interface or the app’s manual.

Previously: