iPad is a great option for students, writers, artists and many more. But not developers. It’s time to change that.
(via Cult of Mac - Your source for the latest Apple news, rumors, analysis, reviews, how-tos and deals.)
Xcode 26.6 includes Swift 6.3 and SDKs for iOS 26.5, iPadOS 26.5, tvOS 26.5, macOS 26.5, and visionOS 26.5. Xcode 26.6 supports on-device debugging in iOS 15 and later, tvOS 15 and later, watchOS 8 and later, and visionOS. Xcode 26.6 requires a Mac running macOS Tahoe 26.2 or later.
[…]
Google Gemini is now available in the coding assistant.
Xcode adds support for the Agent Client protocol.
[…]
Launch Time similar-app goals have been refined for improved accuracy, establishing new baselines.
Previously:
You manage all the devices that appear in Xcode as run destinations using Device Hub.
Run your app on simulated devices in Device Hub to quickly evaluate new features and fix bugs, and to see how your interface works on devices that you don’t have physical access to. Run your app on physical devices to test features or services that have hardware dependencies or investigating performance issues. For more information, see Running your app on simulated or physical devices.
Device Hub is undoubtedly a major surprise. It integrates simulators, physical device management, system state testing, and dynamic size adjustment into a new workflow. Its impact on day-to-day development experience may be more direct than that of many individual APIs. That said, iPhone apps now also support dynamic size adjustment, which will bring new challenges for developers, especially in terms of data and state organization. Adapting to different sizes is not something that can be solved merely by relying on dynamic layout containers. In many scenarios, large and small sizes correspond to very different navigation logic.
Xcode 27 introduced, among other new features, a new Device Hub app for developers that takes the place of the Simulator app. Where Simulator relied on separate windows for each device, Device Hub brings them all together into a single window where each simulated device is the detail view from a source list of devices on the left. It’s a more organized approach, made necessary by the wide variety of platforms Apple and Apple platform app developers have to build and test against.
[…]
In releases prior to Xcode 27, you could resolve this by importing the root public certificate into the simulated OS. On iOS, this could be done by dragging and dropping the
.cerfile onto the Simulator device window. Nothing would appear to happen, but you could then navigate to Settings, General, About, Certificate Trust Settings and mark the certificate as trusted.[…]
In Xcode 27 with Device Hub, this process is much more uniform. […] While this new process does require you to wrap certificates in an Apple Configurator profile, this is much more consistent with how Apple’s device management system works, as it relies on signed profiles with policies, not loose
.cerfiles. And now, just by adding the.mobileconfigto the Profiles section of the device inspector, the embedded certificate is automatically marked as trusted, greatly speeding up installation on new virtual devices.
I get what Apple is trying to do with the Device Hub, but it’s nowhere near as usable and as useful as the iOS Simulator (in this seed)
Device Hub is missing the “pixel accurate” and “point accurate” zoom options and that’s not acceptable.
Maybe someday the Simulator/Device Hub might even be able to output screenshots in the same orientation as the emulated device 😛
Thanks to the remote control / screen sharing features of Device Hub, I can remotely navigate to Settings and start a software update on all my iOS27 devices without having to go collect them around the house 👌
For all of Apple’s nonsense about adding iPhone Mirroring to the EU, the new Device Hub (iOS Simulator) lets you remote-control your physical iOS devices just fine. I don’t think the DMA has an opt-out for developer tools 😛
It’s such a shame for now that Xcode 27’s Device Hub doesn’t support remote screen sharing with iOSes earlier than 27. I wish the screen sharing functionality was part of the developer disk image, and backported to iOS 26 and even iOS 18. Having a physical device plugged in somewhere is so much faster than booting a Simulator.
Previously:
Update (2026-06-26): Léo Natan:
Xcode 27’s “Device Hub” is a broken shitshow, but most importantly, it lacks the Debug menu, where you could toggle slow animations and simulate memory warnings. Apple works tirelessly to destroy any good tool they used to have.
He has a thread of issues. Hopefully these will be addressed before it’s out of beta.
Update (2026-07-01): Craig Hockenberry:
The Device Hub sometimes doesn’t kill CoreSimulator processes when you quit the app (not sure if this is a bug or intentional). Given that each device uses several hundred processes, the memory/processing impact is significant.
You’ll probably want to keep an eye on how many you have running: use right-click on the simulator in the list to “Shut Down” as necessary.
Discover Core AI, Apple’s new framework for on-device AI model deployment. Tour the ecosystem, from Python libraries for converting, authoring, and optimizing models, to a Swift API for simple plug-and-play inference and advanced use cases with strict latency and memory requirements. Explore the new Core AI models repository with ready-to-run examples for popular architectures. See how deep Xcode integration, including ahead-of-time model compilation, streamlines the workflow so you can deliver smarter, more responsive app experiences.
Dive into Core AI model authoring and optimization:
Dive into the complete custom model deployment workflow for Apple silicon with the new Core AI framework. Discover powerful techniques for authoring models using custom Metal kernels, alongside platform-aware compression strategies. The new Core AI Debugger offers deep intrinsic analysis, and AI-assisted workflows guide you from initial concept to optimized on-device execution.
Integrate on-device AI models into your app using Core AI:
Discover a curated collection of popular open-source models — including Qwen, Mistral, SAM3, and more — optimized for Apple silicon using the new Core AI Framework. Learn how to download, run, and benchmark models on your Mac, and integrate them into your app with just a few lines of code. Explore a new workflow for model compilation and on-device specialization to speed up first-time model load. Find out how to profile and optimize runtime performance with Core AI tools in Xcode.
Core AI Documentation (Hacker News):
Core AI helps you build, run, and deploy AI models in your app. Designed with Apple silicon in mind, Core AI allows your app to use the latest model architectures and inference techniques across the CPU, GPU, and Neural Engine. The Swift API makes common tasks simple, while giving you more control over model specialization, caching, and inference performance when needed.
Previously:
General:
Documentation:
Sessions:
Podcasts:
Previously:
A Anthropic implementou no Claude Code a possibilidade de testar aplicativos para iPhone em um painel interativo do iOS Simulator.
Aos interessados, será possível construir aplicativos para iPhones diretamente do Claude Code Desktop a partir da versão 1.24012.0 do app. A integração possibilita ainda a utilização de toques, gestos e atalhos da solução nativa da Apple para simular o iPhone.
Claude Code on desktop now works with the iOS simulator.
— ClaudeDevs (@ClaudeDevs) July 21, 2026
Build and run your iOS app, and the simulator opens in a panel right next to your conversation. Available today in public beta. pic.twitter.com/su4IguzPVb
O recurso é exclusivo da versão para macOS do Claude Code (levando em conta, claro, a disponibilidade do Simulator da Apple), e é necessário ainda ter o Xcode com a plataforma iOS instalada.
Para executar um determinado app, basta abrir o projeto na aba “Code” do Claude Code Desktop, pedir à inteligência artificial (IA) para testar o aplicativo e… pronto. É possível que no primeiro acesso o app solicite uma permissão para seguir com a instalação. O painel dispensa o uso do Computer Use (com exceção da versão em CLI), controlando diretamente o uso do iOS Simulator.
Ainda em beta pública, a ferramenta exige sessões locais, pois sessões em nuvem não são capazes de acessar simuladores instalados no Mac. A novidade está disponível para usuários dos planos Pro, Max e Team.
Apple's SigLens acquisition brings Cupertino an app-monitoring tool that could make Xcode’s debugging tools a whole lot smarter.
(via Cult of Mac - Your source for the latest Apple news, rumors, analysis, reviews, how-tos and deals.)
Login