Performance and distribution terms moved onto the release calendar
Commercial terms, keep rules, and memory ceilings now belong in the same operating review as the binary.
This week, Apple published unified EU business terms effective October 1, Tinder documented material production gains from correcting R8 configuration, and Android warned that per-app memory limits are expanding across devices. The common operational lesson is direct: distribution and performance assumptions expire. Teams need dated evidence for both.
Week at a glance
What changed
Apple unified its EU business terms around an October deadline
Apple says unified EU business terms take effect October 1, 2026, covering alternative payments and distribution, expanded marketplace and web distribution eligibility, and updated commissions and technology fees.
Broad keep rules were hiding measurable product cost
Tinder reports that using the R8 configuration analyzer to remove over-broad keep rules reduced slow cold starts by 47%, cut app size by 28.98%, reduced DEX files from 17 to 11, and coincided with a 3% engagement gain.
Android memory ceilings are moving from guidance to enforcement
Android says per-app memory limits introduced with Android 17 are expanding from Pixel to more manufacturers, with device limits ranging from 4 GB to 16 GB. Apps that exceed the limit may slow down or be terminated.
Store changes
Confirmed platform, policy, and distribution changes.
Apple unified its EU business terms around an October deadline
Apple says unified EU business terms take effect October 1, 2026, covering alternative payments and distribution, expanded marketplace and web distribution eligibility, and updated commissions and technology fees.
- Why it matters
- A distribution choice now changes contracts, fees, reporting, customer support, and entitlement operations together. The Account Holder decision needs a modeled operating path, not a headline comparison.
- Who should care
- iOS teams distributing in the EU or considering alternative payments, marketplaces, or web distribution.
- Suggested action
- Model the current App Store path beside every alternative under the October terms. Include fees, tax handling, refunds, support, reporting, entitlement recovery, and the owner authorized to accept the terms.
Growth and monetization
Commercial patterns worth examining—not universal prescriptions.
Broad keep rules were hiding measurable product cost
Tinder reports that using the R8 configuration analyzer to remove over-broad keep rules reduced slow cold starts by 47%, cut app size by 28.98%, reduced DEX files from 17 to 11, and coincided with a 3% engagement gain.
- Why it matters
- Optimization configuration can preserve code that quietly increases startup work and download size. A cautious rule is not automatically a safe rule when its production cost is unmeasured.
- Who should care
- Android teams with mature dependency graphs, large binaries, legacy ProGuard rules, or startup regressions.
- Suggested action
- Run the R8 configuration analyzer on the release build. Review the broadest keep rule first, remove it in a controlled branch, and compare mapping output, startup, ANRs, size, and the protected flows.
Products and categories moving
Observed product movement and the limits of what it proves.
Android memory ceilings are moving from guidance to enforcement
Android says per-app memory limits introduced with Android 17 are expanding from Pixel to more manufacturers, with device limits ranging from 4 GB to 16 GB. Apps that exceed the limit may slow down or be terminated.
- Why it matters
- A flow that survives on one flagship can fail under another device policy. Memory readiness now depends on resident memory and swap behavior across the supported fleet, not only local heap checks.
- Who should care
- Android teams shipping media, maps, games, generative AI, large bitmaps, or other memory-intensive experiences.
- Suggested action
- Use Android vitals to identify high RSS-plus-swap and bitmap-memory sessions. Reproduce the worst flow on a constrained device, set a release budget, and verify graceful recovery before Android 17 expansion reaches more users.
One move this week
A bounded action to consider, grounded in this edition.
Build the performance and distribution readiness matrix
Commercial terms and runtime ceilings both become expensive when a team discovers them after release.
- Why it matters
- One matrix turns hidden assumptions into dated decisions with owners and evidence.
- Who should care
- Teams distributing in the EU or shipping performance-sensitive Android apps.
- Suggested action
- Create rows for EU terms, checkout path, keep rules, cold start, package size, and peak RSS plus swap. Record owner, current evidence, effective date, threshold, and rollback. Revalidate the riskiest row this week.