iOS
33 post(s)
-
Braze: WWDC 2026 makes ‘app opens’ a worse engagement metric
If users can complete high-value actions via Siri/App Intents, or get price alerts via Safari, your lifecycle program needs to optimise for outcomes (and instrumentation), not sessions.
-
Your iOS attribution strategy in 2026: the uncomfortable ‘prompt gap’ (Kochava)
Kochava’s survey point is blunt: a lot of iOS ‘attribution loss’ is self-inflicted. If you are not prompting (or you ship the raw system ATT prompt with no context), you are choosing to run most of iOS as a black box.
-
RevenueCat: move your rating prompt out of onboarding, Apple is rejecting apps for it
RevenueCat flags a new-ish App Review enforcement: asking for App Store ratings during onboarding is being treated as manipulation (Guideline 5.6.3). Move the prompt to a real ‘happy moment’ after meaningful engagement, and treat it as part of your UX and support hygiene, not an ASO hack.
-
App Store Connect (June 18, 2026): Brazil alternative distribution support, age rating updates, and Intel Mac drop support
Apple’s June 18 App Store Connect notes bundle three ‘quiet but launch-breaking’ changes: alternative distribution/payment option updates (including Brazil support), region-specific age rating shifts (AU/VN), and an official path to drop Intel Macs for universal apps targeting macOS 13+.
-
DeepClick: Mobile attribution still works post-ATT, but you need to treat iOS as a different data product
A clear, nuts-and-bolts walkthrough of how attribution matches installs to ad clicks, why MMPs matter, and how ATT plus SKAdNetwork turned iOS into aggregated, delayed measurement that needs different expectations (and cleaner inputs).
-
Deferred deep linking after Firebase Dynamic Links: what actually needs rebuilding
A credited summary of Messageflow’s guide on replacing Firebase Dynamic Links post-shutdown: use platform-native Universal Links/App Links as the foundation, add a branded routing layer, and measure deferred deep linking as a funnel (click → install → first open with context), not as a click count.
-
IDFA in 2026: where it still works, and what you need when it doesn’t
Branch’s refresher on IDFA post-ATT, with a pragmatic message: use deterministic IDFA when you have consent, but plan measurement around SKAdNetwork coverage and a unified view across both.
-
Apple Developer: Texas App Store age assurance (Declared Age Range + PermissionKit Significant Change)
A credited summary of Apple’s June 2026 update: new Apple Accounts in Texas now fall under SB 2420 age assurance rules, which adds declared age ranges, parent/guardian consent for minors, and a ‘significant change’ consent flow apps need to implement.
-
Apple Developer: Apple Design Award winners 2026 are a high-signal swipe file for ‘proof moments’
The 2026 winners are a practical reminder: delight is usually a product decision (clarity, feedback, pacing), not a marketing slogan. Use these apps as references for onboarding and screenshot promises.
-
Apple Developer: WWDC26 is one week away (what app teams should sanity-check before the churn)
A credited summary of Apple’s June 1 WWDC26 reminder, plus a practical ‘pre-WWDC checklist’ for growth teams: what usually shifts (store rules, toolchain, App Store Connect quirks) and what to review before launch plans lock.
-
Vmobify: a push strategy is a retention system, but the permission moment is the real bottleneck
A detailed push notification strategy guide focused on two hard truths: opt-in is now a product flow (iOS plus Android 13+), and timing/segmentation discipline matters more than ‘send more’.
-
Apple Newsroom: App Store fraud stats (2025) are a reminder that ‘trust’ is a growth lever
Apple says it blocked $2.2B in potentially fraudulent transactions in 2025 and filtered 195M fake ratings and reviews. The takeaway for teams: reviews, account hygiene, and refund prevention are funnel mechanics, not PR.
-
Brazil looks next for alternative iOS app marketplaces: iOS 26.5 adds a ‘default marketplace’ setting
A credited summary of 9to5Mac’s report that iOS 26.5 introduces an ‘App Installation’ setting for Brazilian users, suggesting Apple is preparing a marketplace-based model (not just web distribution). The practical implication: discovery, trust, and measurement may fragment beyond the EU.
-
Apple vs Epic: the Supreme Court declines to pause the contempt order (why app teams should care)
A credited summary of SCOTUSblog’s May 6, 2026 note that Justice Kagan denied Apple’s request to pause a contempt order in the Apple vs Epic dispute. Practical takeaway: external payments and steering rules are still moving, and ‘link out’ UX plus commissions can become a legal battleground, not just a product decision.
-
Apple Developer releases (May 4, 2026): Xcode 26.5 RC and iOS 26.5 RC are here
Apple posted the 26.5 release candidates across Xcode and the OS lineup. Even if you are not shipping platform features, RC week is when build, signing, and CI toolchain problems surface. Treat it like a launch readiness checkpoint, not a developer curiosity.
-
Apple’s App Store Connect SDK minimum requirements are now Xcode 26 + iOS 26 (treat this as a release pipeline deadline)
As of Apr 28, 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later, targeting iOS 26 (and equivalent platform SDKs). For teams, this is a CI and dependency timeline, not just a developer machine upgrade.
-
App Store Marketing Weekly – Week 18 (2026)
This week’s theme: the lock screen is a product surface. Push, permissions, and platform policy now change retention and conversion as much as creatives do, because they shape what users see (and what they fear) before they ever open the app.
-
Apple releases: iOS 26.4.2 + iOS 18.7.8 (notifications database fix)
Apple’s April 22 releases (iOS 26.4.2 and iOS 18.7.8) are a reminder that platform ‘bugfix’ updates can have direct privacy implications. In this case, it appears to close a hole where deleted notifications could persist in the on-device notification database.
-
EFF: push notifications can leak more than you think (lock screen, cloud routing, device databases)
EFF breaks down two privacy leak points for push notifications: what platforms can see in transit (content/metadata), and what can persist on-device (including recovered ‘deleted’ notifications). For app teams, the takeaway is simple: treat notifications as a public surface and design for minimised content.
-
Apple fixed a bug where deleted notifications could be retained on-device (iOS 26.4.2)
A credited summary of Apple’s April 22, 2026 security note for iOS 26.4.2: notifications marked for deletion could be unexpectedly retained on the device. Practical takeaway for app teams: treat notifications as a privacy and trust surface, and keep lock screen content minimal.
-
TechCrunch: Apple fixes iPhone bug that retained ‘deleted’ notification content
A credited summary of TechCrunch’s April 2026 report: iOS cached notification content in a way that could retain messages marked for deletion. Apple shipped a fix, which is a good reminder for app teams that lock-screen copy is part of your privacy model.
-
FSFE says Apple is still blocking DMA interoperability in practice (56 requests, no solutions yet)
A credited summary of FSFE’s April 2026 report arguing Apple’s request-based DMA interoperability process is producing lots of paperwork and very little actual access. The practical takeaway for app teams: expect platform capability access to remain uneven, and plan for compliance and distribution strategy to vary by region.
-
Apple: App Store Connect update (April 16, 2026)
Apple’s April 16 App Store Connect update is ‘boring’ but important: you can now submit builds created with Xcode 26.4.1 and the latest 26.4.1 SDKs. This kind of toolchain gate is exactly what breaks launch timelines if you ignore it.
-
Apple: TestFlight update (April 14, 2026)
Apple’s April 14 TestFlight update is another toolchain gate: TestFlight now accepts builds made with Xcode 26.5 beta 2 and the matching beta SDKs. If you ship on a tight cadence, this is the sort of ‘small’ change that can block a release if your CI image lags.
-
Location SDK panic is usually a configuration story, not a magic data leak
OneSignal clarifies how location works in its mobile SDK: it is off by default, requires explicit developer enablement, and still depends on OS-level user permission. Useful framing for privacy reviews and stakeholder questions.
-
Moburst: Mobile attribution in 2026 (what marketers actually need to know)
A practical snapshot of the 2026 measurement reality: iOS attribution is now AdAttributionKit-first with volume thresholds, Android still has deterministic signal (for now), and the only stable answer is a layered stack (platform postbacks + MMP SSOT + first-party + incrementality).
-
Push in 2026 is still the fastest way to lose trust, or win back users
OneSignal’s 2026 push best-practices guide focuses on the fundamentals that actually move retention: permission priming on iOS, careful timing and frequency, deep linking, and measuring downstream conversion, not just delivery.
-
RevenueCat: Exit Offers in paywalls can lift conversion, but iOS App Review is a real risk
Exit offers (a discounted or alternative plan shown when a user dismisses a paywall) are effective, but Apple may flag them as ‘manipulative’ under Guideline 5.6.
-
SKAdNetwork 4.0: three postbacks, lockWindow, and what to change in your measurement plan
A credited summary of Airbridge’s SKAN 4.0 explainer: multiple conversion windows, earlier postbacks via lockWindow, and new coarse conversion values (plus the trade-offs).
-
Apple is rejecting ‘trial toggle’ paywalls. Here’s what to build instead
RevenueCat documents a quiet App Review shift: paywalls that let users toggle a free trial on/off are getting rejected. Here’s why it happens, what patterns seem safer, and the quick fixes to ship this week.
-
RevenueCat: Apple is rejecting ‘toggle paywalls’ (trial on/off switches) under 3.1.2
The trial-toggle pattern is being rejected as ‘confusing’ under App Review Guideline 3.1.2. If you used it, move to explicit plan selection (trial is a plan attribute), not a hidden mechanic.
-
Apple Developer: Upcoming SDK minimum requirements (April 28, 2026)
Apple says that from April 28, 2026, new uploads to App Store Connect must be built with the latest platform SDKs (iOS/iPadOS 26, tvOS 26, visionOS 26, watchOS 26). Treat this as release engineering, not an admin footnote.
-
Apple’s Retention Messaging API: a new ‘save’ moment for subscription cancellations
Apple’s Retention Messaging API lets you show a message, offer, or lower tier right inside iOS subscription settings when a user tries to cancel. Here’s what it is, how it works, and the practical guardrails.