MOBILE June 25, 2026 · 4 min read

iOS 26 Brings Live Activities to iPad: What to Ship Before Fall

Apple expanded Live Activities to iPad in iOS 26, opening a new persistent re-engagement surface on lock screens and StandBy mode. Here's what app builders need to update before the September public release.

By the AppsOps news desk · June 25, 2026

Apple's WWDC 2026 delivered dozens of developer API expansions, but one of the more quietly consequential ones was the formal extension of Live Activities to iPad. Since their 2022 debut, Live Activities have been an iPhone-and-Apple-Watch-only surface — iPadOS simply ignored ActivityKit requests. Starting with iPadOS 26, Live Activities appear on the iPad lock screen, the Today View, and StandBy mode on supported hardware. For teams already shipping Live Activities on iPhone, the bulk of the work is layout and testing. For teams that have been deferring adoption, this is the right moment to catch up before the fall OS release lands on user devices.

What changed in iPadOS 26

Before iPadOS 26, an Activity.request() call on iPad returned successfully but never rendered anything — the system silently discarded the presentation. From iPadOS 26 onward, three new surfaces are live:

Lock screen compact strip — a persistent status bar at the bottom of the iPad lock screen, analogous in concept to the iPhone lock screen Live Activity but adapted for the wider display.
StandBy expanded view — when an iPad is docked horizontally and in StandBy mode, your expanded layout can fill significantly more horizontal real estate than on iPhone, making it closer to a dashboard widget.
Today View section — a new dedicated Live Activities row above pinned widgets, visible with a left swipe from the iPad home screen or lock screen.

The expanded layout is the most impactful change. Apple's ActivityConfiguration(.expanded) on iPad can render at up to ~500pt wide in some orientations — well above the iPhone Dynamic Island's expanded width of roughly 250–280pt. Any expanded view that assumed iPhone proportions will feel sparse or misaligned on iPad without adjustment.

What you actually need to change

Layout targets to audit

If you already ship Live Activities, run these three cases on an iPad simulator in Xcode 26 before the July public beta ships:

Compact lock screen — your minimal status indicator. Maps to .minimal but rendered at a wider pitch. Check that text doesn't reflow awkwardly.
Expanded lock screen / Today View — the full detail card. Design for roughly 500pt width rather than the iPhone-centric 280pt. This is where most teams will need new SwiftUI layout work.
StandBy horizontal — treat this like a landscape always-on display. Pull in your most glanceable data and keep visual density low.

Push tokens and targeting

There is no separate ActivityKit push token for iPad. The same token that drives iPhone Live Activity updates will route updates to all active device sessions. Your server-side push pipeline needs no changes — only the rendering layer differs.

Deployment target floor

iPad Live Activities require iPadOS 26. If your app's minimumOSVersion is set below 26, the API continues to no-op on older iPadOS versions exactly as it always has on iPad. No floor change is needed to ship — the iPad surface is purely additive.

Why this matters for subscriber retention

iPad users in productivity, education, and finance categories frequently run their device in StandBy or with the screen locked while monitoring dashboards, timers, or live data. According to public reporting from mobile analytics firms, iPad accounts for a disproportionately high share of subscription renewals in several categories — suggesting that even if your iPad install base is smaller than iPhone, its subscriber LTV profile can be meaningfully different.

Live Activities are one of the few persistent, permission-free re-engagement surfaces Apple permits. Unlike push notifications — which require an opt-in prompt and are increasingly filtered by Focus modes — a Live Activity is started by explicit user action (or by your app with the user in-session), so it carries implicit consent. If your app fits any of the following patterns, iPadOS 26 Live Activities are worth scoping this summer:

Delivery or ride tracking
Sports scores or event countdowns
Language learning streaks or session timers
Subscription trial countdowns or onboarding progress bars
Music, podcast, or audiobook now-playing

For localized apps, note that Live Activity content is rendered entirely by your SwiftUI views, so whatever localization pipeline drives your main app also drives your Live Activity strings. If you ship metadata in multiple App Store languages, ensure your Live Activity text is drawing from the same localized string catalog — it's easy to miss if Live Activities were added quickly.

The timeline

iPadOS 26 developer betas are available now via the Apple Developer Program. Public betas begin in July. The public release typically lands in the second or third week of September alongside new hardware. That gives most teams 8–10 weeks to scope, build, and QA iPad Live Activity layouts before the fall release window — tight, but feasible for any team that already has the iPhone implementation in production.

For teams building from scratch, Apple's ActivityKit documentation is the right starting point. The iOS beta sprint checklist we published earlier this month covers the broader set of iOS 26 regression testing tasks alongside this work.