Gabe Roeloffs Left Apple to Rewire the App Store's Checkout

In January 2015, Gabe Roeloffs published a dispatch from the tender frontier of beginner iPhone development. He had made an app called Bruh. Tap a friend, and their phone said “Bruh.” The product may have been mischievously slight, but the lessons were sturdy: programming language fluency was not the same as understanding a platform; marketing mattered; experience accumulated by shipping. “The best way to learn iOS Development is by building,” he wrote. Eleven years later, Roeloffs is still building on the same platform. Only now the tap involves money, the platform takes a commission, and the app is a company called ZeroSettle.

Roeloffs is its founder and CEO. The company, part of Y Combinator's Winter 2026 batch, gives mobile developers a direct-billing path for eligible purchases. The headline promise is almost impolitely specific: about 15 minutes to integrate. Underneath that neat number sits a mess of payment processing, customer entitlements, taxes, fraud, refunds, chargebacks, pricing, analytics, and review rules. A good checkout feels uneventful. Making it uneventful is the event.

A small app, a durable instinct

That old Bruh essay is revealing because Roeloffs did not treat code as a private technical triumph. He noticed the whole loop. The language was easy; the platform APIs were not. Building was rewarding; finding users was essential. He teased the vanity of developers who consider themselves indispensable and, naturally, humble. Then he landed on the more useful point: a technically interesting app with no users has failed its practical test.

The arc from there was unusually coherent. Roeloffs attended California Polytechnic State University, San Luis Obispo from 2017 to 2021, making the President's List in 2018. His personal site records stints in Microsoft cloud software and Tesla infotainment. After college, he joined Apple as a software engineer. Four years later, when he announced his departure, he wrote that projects he had touched now ran on billions of devices.

“Experience is everything.”Gabe Roeloffs, writing about his first Swift app in 2015

Operating systems are an education in invisible consequences. A small mistake can travel farther than its author. A small improvement can disappear into the quiet competence people expect from their devices. Roeloffs described Apple as a place where colleagues pushed, taught, and shaped him as an engineer. His farewell was grateful and spare. The accompanying image was Apple Park's rainbow arch beneath a broad California sky: a cheerful punctuation mark after four years spent in the machinery.

The ruling and the receipt

ZeroSettle's opening arrived in May 2025, when the Epic v. Apple case changed what Apple could prevent US developers from doing. Direct purchase links and alternative checkout became a practical possibility for more apps. The legal door opened, but it did not arrive with hinges, a handle, or instructions. Developers still had to build a flow, preserve conversion, manage subscriptions, understand app-review requirements, and inherit the chores that a store had previously handled.

Roeloffs and co-founder Ryan Elliott knew the platform from the inside. Elliott had also worked as an Apple systems software engineer. Their response was not a manifesto. It was an SDK. ZeroSettle launched support for Swift, Kotlin, Flutter, and React Native across iOS and Android. In one mode, the company acts as Merchant of Record and takes responsibility for sales taxes, VAT, GST, fraud, disputes, refunds, and billing support. In another, developers bring their own Stripe account and remain the merchant.

The arithmetic attracts attention because it fits in a screenshot. Apple's familiar commission can leave $6.99 from a $9.99 sale. ZeroSettle illustrates a direct route that can leave as much as $9.35. But Roeloffs' public explanations keep returning to the less photogenic constraints. A developer cannot simply make a web checkout imitate Apple's native payment sheet. In the US, eligible direct billing must still coexist with applicable store rules. Discounts and incentives can help, but the flow must survive review and retain the customer's trust.

This is where his career begins to look less like a pivot and more like a change in altitude. Microsoft cloud work, Tesla infotainment, Apple operating systems, mobile billing: each sits between a human gesture and a large technical system. Each must translate complexity into something that appears simple at the edge. A person taps. A lot happens. The product is judged by how little of the “lot” they have to notice.

The founder as systems accountant

Roeloffs' more recent writing adds another clue. He posts about compiler hygiene in AI-assisted Swift development and about the economics of delayed marketplace payouts. The subjects sound unrelated until you notice the shared habit: look for the hidden cost in a system everyone treats as normal.

In Swift, his suggestion is to turn warnings into errors. Unused variables and unreachable branches, he argues, do more than offend an engineer's sense of tidiness. In an AI coding workflow they pollute a finite context window, crowding out useful signal. In his marketplace analysis, he calculated how delaying seller payouts allows a platform to hold billions in working capital and earn a return on the float. One observation concerns tokens; the other concerns dollars. Both concern waste, timing, and who benefits from the default.

The small interface is never merely small. It is where the rules of the larger system collect.

ZeroSettle now describes itself more broadly than its original direct-billing pitch. The company offers unified entitlements, regional pricing, analytics, and Autopilot, a system for running pricing experiments while leaving live changes subject to approval. The move makes sense. Once a developer controls a checkout, the next question is not merely how to pay. It is what to charge in Brazil, Britain, India, or the United States; how to treat a subscriber who wants to cancel; and how to understand access across stores and the web.

Billing, in this view, is a control surface for a mobile business. The fee matters. So do conversion, retention, payout timing, customer ownership, and the right to experiment. ZeroSettle is attempting to gather those scattered levers into one instrument panel.

There is also a useful restraint in how Roeloffs talks about the opportunity. His practical guidance to app makers distinguishes what a court permits from what platform review accepts. The difference is where many glossy market maps go to die. A rule may change in a paragraph; developer behavior changes through documentation, rejected builds, revised interfaces, and nervous tests on real customers. ZeroSettle's work is therefore partly translation. It turns legal room into product choices, then turns those choices into components a small app team can actually ship. For a founder who began by discovering that Swift fluency was not the same as iOS fluency, the pattern is familiar. Knowing what is allowed is only the vocabulary. Building something that behaves correctly is the sentence.

What a two-person company can carry

There is a comic mismatch between ZeroSettle's founding headcount and its list of nouns: tax, fraud, compliance, subscriptions, entitlements, pricing, analytics. Two people is a dinner reservation. It is not the number one naturally associates with financial infrastructure across more than 190 countries. The model works by packaging technical interfaces and operational partners behind a developer-facing layer. Roeloffs and Elliott do not need to become every institution in the chain. They need to make the chain behave like one product.

That constraint helps explain the 15-minute refrain. Integration time is not merely a convenience metric. It is the company's editorial judgment about what developers should have to understand. The unpleasant complexity does not vanish. It changes address.

Roeloffs' aspiration, in the words on his personal site, is to rewrite how money moves in games. ZeroSettle's homepage now speaks to apps more generally, but games remain a vivid test case. Coins, gems, passes, upgrades, and subscriptions create high-frequency relationships among platform rules, virtual goods, and real money. Every extra tap can hurt conversion; every percentage point changes margin. The checkout must be compliant, legible, and almost forgettable.

The boyish joke of Bruh survives here in a grown-up form. Build the thing. Watch where people hesitate. Learn the platform's actual behavior rather than its brochure. Remember that distribution and use matter as much as code. Roeloffs' first app made a phone say one word. His present company has a longer vocabulary: billing, entitlements, price, retention, ownership. The instinct remains compact. Put a difficult system behind an easy tap.