TECH June 28, 2026 · 4 min read

Week in App Store Ops: H2 Starts Monday, iOS 26 Beta Progress, and Play's Large-Screen Push

H2 2026 begins Monday, iOS 26 beta is at full velocity, and Google Play's large-screen compliance window is closing. A synthesis of what moved this week and the five decisions that can't wait until August.

By the AppsOps news desk · June 28, 2026

H2 2026 begins Monday. If your roadmap for the next 90 days isn't written yet, this is the weekend to do it — because the back-to-school featuring window, the iOS 26 GM, and Google Play's large-screen compliance deadline all converge between now and late September. Here's what moved this week, and what it means for teams shipping apps.

iOS 26 Beta: Liquid Glass Is Locking In

iOS 26's design system — Liquid Glass — has now been through multiple developer betas, and the interface is stabilizing enough to act on. The main implication for app marketing teams: screenshots taken on iOS 25 look visually stale on iOS 26 devices, and App Store visitors on iPhone 17 hardware (expected this fall) will see your old creative first.

The risk isn't catastrophic for most apps — Apple doesn't penalize stale screenshots immediately — but first-impression conversion will erode as the installed base shifts to iOS 26. A few things to triage now:

App icon compatibility: Does your icon look right with Liquid Glass chrome? Test on the latest Xcode simulator before committing to a redesign.
Screenshot refresh: At minimum, update your en-US screenshots for the iOS 26 aesthetic. Then decide whether to localize the refresh — screenshot localization costs less than most teams expect at scale, and the conversion lift in non-English markets is often the larger opportunity anyway.
Live Activities on iPad: If you ship Live Activities for iPhone, check the recent post on Live Activities on iPad and lock-screen strategy — a new footprint that affects how your app appears across all Apple hardware.

Apple's developer beta schedule historically delivers the GM roughly 10–12 weeks after WWDC, which puts iOS 26 GM around late August. Submitting an iOS 26-optimized binary before GM gives you a head start in Review queues before the fall rush hits.

H2 2026: Five Decisions That Won't Wait Until August

The decisions that will define your App Store results through December are front-loaded — they need to be made now so implementation, review, and localization can finish before the September window opens.

Proceeds tier: Apps generating under $1M/yr still qualify for the 15% commission tier. If you're near the threshold, model the effect of a price change on both gross revenue and net proceeds before acting.
PPP pricing: Subscription conversion rates in Southeast Asia, Latin America, and Eastern Europe remain well below what purchasing-power-adjusted pricing can recover. AppsOps PPP pricing lets you model localized pricing across all 175 App Store territories before you commit.
Keyword freshness: App Store search personalization has reportedly shifted since the spring, and keyword lists built in Q1 may be missing intent signals that didn't exist before Apple Intelligence began surfacing app content differently. An audit is overdue for most teams.
Screenshot roadmap: See above. The question isn't whether to refresh for iOS 26 but when and across how many locales. Starting in July gives you time to iterate before September.
Custom Product Pages: CPPs remain underused relative to the leverage they provide on paid user acquisition. If you're running Apple Search Ads without at least 2–3 CPPs live, you're leaving measurable conversion data on the table.

For a deeper look at the full H2 decision set, see the recent post: H2 2026 App Store Roadmap.

Google Play: Large-Screen Compliance Is Now Affecting Discovery

Google's H2 2026 Play compliance requirements — covering foldables, tablets, and ChromeOS — were announced at I/O 2026 and are now reportedly influencing discovery rankings. Developer community reports suggest apps failing Google's large-screen technical checklist are seeing reduced placement in the Play tablet charts.

The practical bar is not as high as it sounds. Google's current enforcement focuses on three things:

Requirement	What it means in practice
No letter-boxing on displays ≥600dp	Your layout must adapt, not just scale down
Window resizing without crashing	Test in multi-window mode on a Pixel Tablet emulator
Target API 35+ (Android 15)	Update your `targetSdkVersion` if you haven't already

If your Flutter or React Native app hasn't been tested on a large-screen emulator recently, add it to Monday's backlog. The full Play H2 compliance breakdown covers the details.

Briefly: The AI-ASO Tool Market Is Settling

After a burst of AI-powered ASO tools in H1 2026 — keyword generators, screenshot generators, review summarizers — the market is showing early signs of consolidation. Several tools that launched in Q1 have gone quiet or pivoted to agency-only pricing. What's remaining dominant: platforms that integrate directly with the App Store Connect API for real-time rank data, combined with LLM-assisted metadata drafting.

The practical implication: if you evaluated and passed on an AI-ASO tool six months ago, it's worth another look. The survivors are meaningfully better than their launch-day versions, and pricing has stabilized into predictable tiers. Reports suggest the tools that integrated best with ASC API workflows are pulling ahead of pure-play keyword generators.