TECH October 25, 2026 · 4 min read

The Week in App Store Ops: iOS 26.1, EU Fees, and the November API 36 Deadline

Five stories that shaped app development this week: iOS 26.1 beta lands, Apple reshuffles EU fees again, Android 16 QPR1 drops, Google's November API 36 deadline for existing apps looms, and OpenAI's model routing changes hit mobile builders.

By the AppsOps news desk · October 25, 2026

The last week of October is supposed to be calm — the September launch sprint is over, Q4 hasn't fully kicked in yet. But 2026 isn't cooperating. This week brought beta drops from both Apple and Google, another round of DMA-driven fee adjustments from Apple, a hard deadline from Google Play, and a model routing shakeup from OpenAI. Here's what mattered and what it means for your roadmap.

iOS 26.1 Beta: Point Release, Non-Trivial Implications

Apple seeded the first betas of iOS 26.1 this week. Point releases rarely generate headlines, but developer community reports suggest this one includes fixes to Liquid Glass rendering behavior — specifically around how custom UI components behave in dark mode and under transparency. If your app shipped workarounds during the iOS 26 beta cycle to handle specific visual edge cases, those patches are worth retesting now.

For a detailed checklist of what to audit before submitting against the new SDK, the earlier iOS 26.1 beta developer checklist covers the specifics. The short version: test your Liquid Glass surfaces, re-export device frames if system chrome has shifted, and check whether your screenshot set still accurately reflects the experience reviewers will see.

Review timing: Apple's review window is still reasonable through late October. There are roughly two usable weeks left before Thanksgiving tightens the pipeline.
Screenshot note: If 26.1 changes default system chrome appearance, re-export any frames that include status bars or navigation chrome before Q4 rush.

Apple Reshuffles EU Fees — Again

Apple made further adjustments to its fee structure for multi-seat and family subscriptions in the EU this week, continuing the slow-motion compliance renegotiation the DMA has forced on its business model. According to public developer documentation, the changes affect how family and team plan revenues are calculated under the Core Technology Fee framework.

The specific numbers are less important than the pattern: Apple's EU pricing model has changed meaningfully multiple times this year. If you sell family or team tiers and have EU subscribers, the take rate you assumed in January may not be the rate you're operating at in November. Build a quarterly EU-specific margin audit into your finance calendar — and consider whether your PPP-adjusted price tiers in the EU still hit the margins you need. The PPP pricing calculator can help you pressure-test this by market.

Android 16 QPR1 Beta: Enforcement Is Tightening

Google released the first developer preview of Android 16 QPR1 — its Q4 quarterly platform update — this week. QPR releases sit between major Android versions and are typically where behavioral enforcement flags move from "advisory" to "active." Reports from the developer community suggest QPR1 tightens enforcement around the predictive back gesture and edge-to-edge display requirements.

Neither change should require significant work for apps already compliant with Android 16. But if your app has been operating under the assumption that edge-to-edge enforcement is still soft, QPR1 is a signal the grace period is ending. Check your Play Console pre-launch reports for QPR1 behavior as the build becomes more widely available.

The November 1 API 36 Deadline: This One Is Real

This deserves a separate callout because it's easy to overlook in the noise of beta season. Google's requirement to target API level 36 was already in force for new app submissions. The November 2026 deadline applies to existing apps that haven't yet updated their target SDK.

After the deadline, apps below the minimum target API are hidden from new users in the Play Store — existing installs continue to function, but discoverability for new acquisition effectively goes to zero. That's the enforcement pattern Google has followed consistently for every previous API deadline. Check your targetSdkVersion in build.gradle now. If you're already compliant, verify in Play Console. If you're not, this is the moment.

Full compliance checklist and timeline context: Google Play November API 36 deadline for existing apps.

OpenAI Model Routing Changes: Test Your AI Features

OpenAI made public announcements this week about changes to how it routes traffic across model tiers in its API. It's not yet fully clear how the changes affect all use cases, but early developer reports suggest apps that rely on specific model routing behaviors — particularly around which model variant handles a given request — have seen output-level differences worth testing against.

The structural lesson here isn't OpenAI-specific: if your app's AI features are tightly coupled to a particular model's behavior, you need regression tests that run on every API release. Hosted AI model routing can change without app-level notice. For Q4 in particular — when user acquisition and retention stakes are at their highest — catching a silent output regression in November is far better than catching it in a one-star review in December.

Looking Ahead to Next Week

November 1 is the Google Play API 36 cutoff, but it's also the start of the final push before Black Friday and the holiday surge. If you have offer codes, win-back campaigns, or metadata refreshes planned for Q4, the two weeks straddling the November 1 deadline are operationally your best window. After that, App Store and Play Store pipelines typically tighten through December.