iOS 27 Siri AI: What Developers Can Test Now

<!– wp:heading –>
<h2>The WWDC recap covered the roadmap – this covers what you can actually test today</h2>
<!– /wp:heading –>

<!– wp:paragraph –>
<p>This blog already walked through getting an app ready for iOS 27 off the back of WWDC26’s announcements. Since then, iOS 27 Siri AI and the rest of the Apple Intelligence features have moved from keynote slide to something developers can install a beta of and actually poke at. Here’s what’s real, testable, and worth building against right now rather than roadmapping for later.</p>
<!– /wp:paragraph –>

<!– wp:heading –>
<h2>Siri AI: what’s actually different this time</h2>
<!– /wp:heading –>

<!– wp:paragraph –>
<p>Siri AI is available for developer testing across iOS 27, iPadOS 27, macOS 27, and visionOS 27 now, with watchOS 27 support landing in a later beta. The headline change isn’t a bigger vocabulary – it’s Siri finally reasoning across app context and on-screen content instead of matching a fixed set of intents, which is the piece Apple has been publicly behind on for two years.</p>
<!– /wp:paragraph –>

<!– wp:list –>
<ul>
<li>App Intents remain the integration point – if your app already exposes intents properly, Siri AI can reason about when and how to invoke them, not just match exact phrases</li>
<li>On-screen awareness means Siri AI can act on content currently visible in an app, not only on data explicitly exposed through the App Intents framework</li>
<li>Public beta lands next month, with general release expected this autumn as a free software update</li>
</ul>
<!– /wp:list –>

<!– wp:heading –>
<h2>Call Context: a small feature worth checking against your app</h2>
<!– /wp:heading –>

<!– wp:paragraph –>
<p>Call Context surfaces relevant information in the Phone app when a user calls a business – a reservation number, an order reference – computed entirely on-device for privacy. If your app has a customer-facing phone number and stores anything like booking or order references, it’s worth checking now whether Call Context can surface that data automatically, rather than finding out after launch that users expect it to.</p>
<!– /wp:paragraph –>

<!– wp:heading –>
<h2>The Photos changes matter if your app touches images</h2>
<!– /wp:heading –>

<!– wp:list {“ordered”:true} –>
<ol>
<li><strong>Extend</strong> – expands a photo and fills the new space with generated content, relevant if your app lets users export or share images from the system Photos picker</li>
<li><strong>Spatial Reframing</strong> – adjusts a photo’s composition after capture</li>
<li>Every image edited with these tools carries a hidden SynthID watermark – worth knowing if your app does any of its own image-authenticity checking, since you may now be seeing watermarked input you weren’t before</li>
</ol>
<!– /wp:list –>

<!– wp:heading –>
<h2>Compatibility, in practice</h2>
<!– /wp:heading –>

<!– wp:paragraph –>
<p>iOS 27 itself is expected to support devices back to the iPhone 11 and iPhone SE (2nd generation), but the Apple Intelligence features underneath Siri AI require at least an iPhone 15 Pro. That split matters for testing strategy: don’t assume every device running iOS 27 in the wild can exercise the Siri AI paths your app might rely on – build a fallback for devices that update but don’t qualify for the intelligence features.</p>
<!– /wp:paragraph –>

<!– wp:heading –>
<h2>What to actually do this week</h2>
<!– /wp:heading –>

<!– wp:paragraph –>
<p>If your app exposes App Intents already, install the current developer beta and test how Siri AI’s contextual reasoning invokes them – behaviour worth catching now rather than after the public beta brings a much larger, less forgiving pool of testers. If you haven’t touched App Intents at all, this is the release that makes it worth prioritising: Siri AI’s context-aware reasoning is specifically built to make well-integrated apps more discoverable through voice, and that gap between “integrated” and “not” is about to become far more visible to end users than it’s ever been before.</p>
<!– /wp:paragraph –>