Apple just opened the Siri AI app intents to developers, and you can start testing now. The developer beta covers iOS 27.3, iPadOS 27.3, macOS 27.3, and visionOS 27.3. App Store submissions using the new capabilities arrive in the spring.
If you've built anything on App Intents, this is the one to read. Siri AI works directly with Apple Intelligence and, unlike earlier versions, understands context and can chain actions across apps. That means a single voice request can hit your app and another one in sequence. Start prototyping those flows now, before everyone else does.
The catch? Availability is thin. Siri AI runs in a limited number of languages and regions, and Traditional Chinese support is only expected by the end of 2026. In the EU, Siri AI is unavailable on iOS, iPadOS, and watchOS, and Apple says EU availability is still being negotiated over interoperability concerns. Bottom line: build for the US first and treat EU as a later phase.
Voters just made data centers a political problem. In the 2026 midterms, 38 of 44 measures restricting data centers passed across 10 states, and Democrats flipped governor races in Arizona, Georgia, and Ohio, three states that had been courting developers hard.
If you ship code on AWS, Google Cloud, or Azure, this hits your roadmap. Developers nationwide will face tighter rules on tax incentives and on who pays for grid and water upgrades. Capacity that was supposed to come online for your inference workloads could slip, because some projects need 12 to 18 months just to secure state environmental permits.
The numbers are big. Texas was expected to take more than 41 percent of added data center capacity in 2028, and roughly 13 gigawatts is now exposed. Nearly two-thirds of 2028 capacity could face similar delays. The measures don't touch projects already under construction or approved through 2027, so the near-term pipeline is mostly safe. Spoiler: the mandate here is murkier than the headlines suggest, since cost of living ranked higher for many voters. Let's dive deeper…
In today's ContentBuffer update: