# Xcode Published articles for Xcode. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## iOS Startup Performance in Practice, Part 2: Measuring App Launch Time in Production DevFeed: [iOS Startup Performance in Practice, Part 2: Measuring App Launch Time in Production]() Original publisher: [Read original article]() Author: oreshina Published: 2026-11-08T16:47:54Z Content type: article Language: en Sources: [HackerNoon]() Topics: [app startup](), [mobile-app-performance](), [performance-engineering](), [digital experience monitoring](), [Monitoring](), [iOS](), [ui-testing](), [mobile devops]() Tags: [app](), [benchmark](), [buffer](), [devices](), [ios](), [ios-app-development](), [ios-app-launch-time](), [ios-performance-testing](), [ios-startup-performance](), [launch](), [measuring](), [metrickit](), [milestones](), [mobile-app-development](), [performance](), [production](), [startup](), [swift](), [time](), [xcode](), [xctest]() ### AI overview Reliable iOS startup measurement requires two complementary clocks: Xcode Organizer or MetricKit captures system launch milestones such as First Draw and resume, while lightweight custom telemetry measures product milestones such as route readiness and interactivity. Define each metric's population and start/end boundaries, then report percentiles, sample counts, and relevant segments; averages can hide slow device or user-state cohorts. When production data identifies a regression, reproduce that cohort on physical hardware with a Release-like build, deterministic data, and controlled network conditions. XCTest provides repeatable launch or signpost benchmarks, while Instruments helps diagnose causes but adds overhead and should not be treated as the final stopwatch. Validate fixes against the same production segment. System metrics cannot infer product readiness, and application timers cannot capture work before app code runs. ### Source excerpt Learn how to measure iOS startup on real user devices with MetricKit, production milestones, percentiles, segmentation, XCTest, and Instruments. ## Building Reliable iOS Apps With AI Agents DevFeed: [Building Reliable iOS Apps With AI Agents]() Original publisher: [Read original article]() Author: Yehor Chernenko Published: 2026-11-08T16:39:14Z Content type: article Language: en Sources: [HackerNoon]() Topics: [iOS](), [agentic workflows](), [Loop Engineering](), [Swift](), [SwiftUI](), [CI/CD](), [Xcode]() Tags: [agent](), [agentic](), [agents](), [agents-md](), [ai](), [ai-coding](), [ai-coding-agents](), [analytics](), [api](), [app](), [architecture](), [async](), [auth](), [automation](), [await](), [backend](), [bash](), [blocking](), [c4-model](), [claude-code](), [design](), [harness](), [ios](), [ios-development](), [swift-concurrency](), [system](), [xcode]() ### AI overview AI agents can build, run and check iOS apps, making prototypes and MVPs largely feasible, but reliable products still require human ownership of system design and the quality harness. The article recommends documenting architecture in discoverable C4 diagrams under docs/architecture/, linked from a short AGENTS.md and detailed only as needed; a skill and Claude Code Stop hook can refresh affected diagrams after Swift changes. For quality, it prioritizes automated tests, CI and linters, then agentic review, then careful human review of small diffs. Use focused skills with good and bad examples for issues such as Swift concurrency, and keep context lean because loaded rules and docs consume tokens on every turn. ### Source excerpt AI agents can build iOS apps end to end. For reliable apps you still own two things: the system design, kept in C4 diagrams, and the harness around the agent. ## GitHub Copilot weekly releases -- November 2 DevFeed: [GitHub Copilot weekly releases -- November 2]() Original publisher: [Read original article]() Author: Allison Published: 2026-11-06T21:00:26Z Content type: release Language: en Sources: [GitHub Changelog]() Topics: [GitHub Copilot](), [releases](), [Pull Request](), [IntelliJ IDEA](), [GitHub]() Tags: [agent](), [agents](), [air](), [app](), [coding](), [coding-assistant](), [copilot](), [github](), [github-copilot](), [github-copilot-app](), [jetbrains](), [jetbrains-air](), [manage](), [merge](), [pull-requests](), [release](), [releases](), [sessions](), [settings](), [weekly](), [xcode]() ### AI overview This week's releases add Copilot integrations for JetBrains Air and Xcode, alongside changes to pull request handling and agent workflows. Agent Merge can be set up from a pull request and stays enabled while required checks or rules are pending; users can also inspect reviewer status and request reviews. In the Copilot app, users can recover from context limits by compacting a conversation, open CSV and TSV files as tables, and manage sessions in batches. Assisted approval instructions are opt-in and apply to local sessions. The Xcode integration is in public preview starting with Xcode 27.3 beta. In VS Code, preview features include remote app inspection and interactive canvases; local automations add cron scheduling and workspace custom agents. Cloud sessions support image files through Add Context, while local sessions can add other files. ### Source excerpt This week, Copilot comes to JetBrains Air and Xcode's coding assistant, with updates to help you manage pull requests, settings, and agent sessions. GitHub Copilot app Set up Agent Merge... The post GitHub Copilot weekly releases -- November 2 appeared first on The GitHub Blog. ## Announcing one-click APNs setup with the Appwrite CLI DevFeed: [Announcing one-click APNs setup with the Appwrite CLI]() Original publisher: [Read original article]() Author: Arnab Chatterjee Published: 2026-11-05T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite]() Tags: [announcements](), [app](), [apple](), [cli](), [command](), [providers](), [run](), [setup](), [xcode]() ### AI overview `appwrite init apns` streamlines iOS push setup by creating or updating Appwrite production and sandbox providers, configuring Xcode entitlements and background mode, adding a missing Apple platform, and checking the bundle ID's Push Notifications setting with Apple. It reads identifiers from an Xcode project or Expo `app.json`, and can use an existing `.p8` key or create one with `--create-key`. Key creation is experimental and relies on Apple's private APIs; the CLI offers interchangeable sign-in providers. Apple sign-in changes require confirmation unless `--register-app-id` is passed. Reruns preserve enabled providers, while `--force` or `--key-path` replaces their key. Expo users must also put the settings in `app.json` because prebuild regenerates iOS files; device registration and sending remain separate steps. ### Source excerpt Run appwrite init apns and the CLI creates your APNs providers, configures Xcode, checks your App ID with Apple, and can even create the APNs key for you. ## GitHub Copilot is now available in Xcode's coding assistant DevFeed: [GitHub Copilot is now available in Xcode's coding assistant]() Original publisher: [Read original article]() Author: Allison Published: 2026-11-04T19:10:40Z Content type: release Language: en Sources: [GitHub Changelog]() Topics: [GitHub Copilot](), [coding assistant](), [Xcode]() Tags: [coding](), [coding-assistant](), [copilot](), [github](), [github-copilot](), [release](), [xcode]() ### AI overview GitHub Copilot is in public preview in Xcode's built-in coding assistant, starting with Xcode 27.3 beta, and supports all Copilot plans. Setup requires a Mac running macOS Tahoe 26.6 or later; in Xcode, open Xcode > Settings > Intelligence to configure it. The existing GitHub Copilot for Xcode extension remains a separate workflow option. The excerpt directs users to Apple Developer Downloads for the beta and suggests sending feedback through the GitHub Copilot for Xcode repository or Apple Feedback Assistant. ### Source excerpt You can now work with GitHub Copilot directly in Xcode's built-in coding assistant, bringing Copilot into your native Xcode workflow. The integration is now in public preview, available starting with... The post GitHub Copilot is now available in Xcode's coding assistant appeared first on The GitHub Blog. ## Maestro CLI 2.12.0: queue priority for Cloud uploads DevFeed: [Maestro CLI 2.12.0: queue priority for Cloud uploads]() Original publisher: [Read original article]() Author: Maestro Team Published: 2026-10-28T13:24:00Z Content type: release Language: en Sources: [Mobile]() Topics: [mobile devops](), [queueing theory]() Tags: [2](), [cli](), [cloud](), [device](), [ios](), [ios-simulator](), [maestro](), [priority](), [queue](), [screenshot](), [simulator](), [uploads](), [xcode](), [xcode-27]() ### AI overview Maestro CLI 2.12.0 lets you prioritize Maestro Cloud uploads within your own organization's queue: `high` moves flows ahead of waiting `normal` and `low` flows, while `normal` remains the default. Set it with `maestro cloud --priority high`; it also works through GitHub Actions and MCP `run_on_cloud`, and the Console can change priority while an upload is running. Priority does not affect other organizations' queues or concurrency limits. Configuration requires Maestro CLI 2.12.0 or Maestro Cloud action 3.1.0. The release also supports simulators on Xcode 27, prevents Android `start-device` from hanging indefinitely, restores Cloud uploads for screenshot flows, and makes invalid scroll speed values fail the flow instead of silently using a default. ### Source excerpt Maestro CLI 2.12.0 adds queue priority for Maestro Cloud uploads, unblocks iOS Simulator on Xcode 27, keeps start-device from hanging, and fixes screenshot uploads. ## Using AI for Testing in iOS \[SUBSCRIBER\] DevFeed: [Using AI for Testing in iOS \[SUBSCRIBER\]]() Original publisher: [Read original article]() Author: ehabamer Published: 2026-10-28T00:00:00Z Content type: tutorial Language: en Sources: [Kodeco]() Topics: [Test automation](), [Unit testing](), [AI-assisted coding](), [agentic-coding](), [iOS](), [Xcode]() Tags: [agent](), [agentic](), [agents](), [ai](), [ai-agent](), [audits](), [console](), [english](), [ios](), [mcp](), [module](), [multimodal-module](), [parallel](), [plan](), [simulator](), [subscriber](), [testing](), [tests](), [unit-test](), [unit-tests](), [xcode](), [xcode-27]() ### AI overview The module turns findings from prior AI-generated audits into a prioritized unit-test plan, with each test tied to a specific approved finding. It shows how to direct AI agents to write those tests in parallel using Conductor, then use Xcode 27's simulator MCP to run plain-English UI test steps against a running app. Agents also use breakpoints and console output to debug the app. The focus is on deciding which tests to write and why, not manual test authoring or generic goals such as increasing coverage. Completion of "iOS Feature Implementation Using AI" is a prerequisite. ### Source excerpt This module focuses on the testing side of Agentic Development. Rather than teaching you how to write tests by hand, since the code itself is now written by AI agents, it focuses on how to instruct an agent about which tests to write and why, and on prioritizing tests before implementing a fix. You'll consolidate the audits produced by the previous module into a concrete, prioritized unit-test plan and use Conductor to write those tests in parallel. Then you'll use Xcode 27's simulator MCP to have an AI agent simulate human behavior in a running app by executing plain-English test steps itself, and have that same agent debug the app directly through breakpoints and the console. This module does not cover how to write tests manually, and treats "write unit tests" or "increase coverage" as anti-patterns to avoid -- every test in this module traces back to a specific, reasoned finding. Prerequisites: Completion of "iOS Feature Implementation Using AI" module. ## How the Xcode 27 MCP can lead to higher token costs when navigating the Simulator DevFeed: [How the Xcode 27 MCP can lead to higher token costs when navigating the Simulator]() Original publisher: [Read original article]() Author: Antoine van der Lee Published: 2026-10-26T12:09:51Z Content type: news Language: en Sources: [SwiftLee]() Topics: [context window](), [Tool](), [User interface design](), [Xcode](), [Test automation]() Tags: [agent](), [ai-development](), [benchmark](), [cli](), [costs](), [ios](), [ios-simulator](), [mcp](), [navigation](), [screenshot](), [simulator](), [token](), [token-costs](), [tokens](), [xcode](), [xcode-27]() ### AI overview In the author's scripted benchmark, Xcode 27.1 MCP's accessibility hierarchy took about seven times more input than RocketSim CLI's compact output across ten scenarios, though Xcode needed fewer calls and can build and launch the app. Xcode returns paths to a hierarchy, screenshots, thumbnails, and logs; the agent reads the hierarchy after actions, while the benchmark's screenshots were not opened. Xcode requires approval with a project open and routes interaction through a subagent. It missed a hidden accessibility element that RocketSim could activate; Face ID, two-finger touches, and accessibility audits were RocketSim-only in this benchmark. Results used one machine and fixture app, estimated tokens from bytes, and were not live model token counts. The author recommends filtering competing screenshot tools, stating the preferred tool in agent instructions, reserving screenshots for visual checks, and using clear accessibility labels. ### Source excerpt The Xcode 27 MCP can lead to higher token costs when your agent navigates the iOS Simulator, because it reads about seven times more text after every action than RocketSim's CLI did in my benchmark. Efficient navigation comes down to what your agent reads after every tap. A screenshot shows what the screen looks like, ... -> The post How the Xcode 27 MCP can lead to higher token costs when navigating the Simulator appeared first on SwiftLee. ## Get Your .NET MAUI App Ready for Xcode 27 DevFeed: [Get Your .NET MAUI App Ready for Xcode 27]() Original publisher: [Read original article]() Author: Gerald Versluis Published: 2026-10-19T16:05:00Z Content type: tutorial Language: en Sources: [.NET Blog]() Topics: [.NET MAUI](), [Xcode](), [.NET](), [Agent Skills](), [XcodeGen](), [Continuous Delivery (CD)]() Tags: [activation](), [agent](), [agent-skill](), [agent-skills](), [apple](), [authentication](), [build](), [c-sharp](), [cli](), [code](), [coding-agent](), [command-line](), [content](), [ios](), [lifecycle](), [mac-catalyst](), [net](), [net-10](), [net-for-ios](), [net-maui](), [net-maui-cli](), [net-sdk](), [scene-lifecycle](), [uikit](), [xcode](), [xcode-27]() ### AI overview This tutorial explains how to migrate an existing .NET MAUI app for Xcode 27's UIKit scene lifecycle requirement. It covers matching SDK and workload versions, adding scene delegates and plist configuration, preserving custom lifecycle behavior such as authentication and deep links, adjusting deployment targets, and testing the migration on iOS 27 and Mac Catalyst. ### Source excerpt Use an agent skill to prepare your existing .NET MAUI app for Xcode 27, with the scene lifecycle changes and manual migration steps explained. The post Get Your .NET MAUI App Ready for Xcode 27 appeared first on .NET Blog. ## SwiftUI Performance: Find Redraws in Xcode Instruments DevFeed: [SwiftUI Performance: Find Redraws in Xcode Instruments]() Original publisher: [Read original article]() Author: Antoine van der Lee Published: 2026-10-19T11:27:45Z Content type: tutorial Language: en Sources: [SwiftLee]() Topics: [SwiftUI](), [Xcode](), [performance-optimization]() Tags: [code](), [debug](), [debugging](), [performance](), [swiftui](), [xcode]() ### AI overview This tutorial explains how to use Xcode Instruments to find SwiftUI redraws, measure how often view bodies update and how long they take, and trace updates to their causes. It also describes common sources of excessive updates and how to verify changes by recording the same interaction again. ### Source excerpt SwiftUI performance problems often come down to views that redraw too often or take too long to run their body. Before you can fix them, you need to find out which views are responsible and what triggers their updates. Xcode Instruments can show you exactly that, as long as you know where to look. In ... -> The post SwiftUI Performance: Find Redraws in Xcode Instruments appeared first on SwiftLee. ## CodeQL changes for macOS 27, Xcode 27, and Swift 6.4 DevFeed: [CodeQL changes for macOS 27, Xcode 27, and Swift 6.4]() Original publisher: [Read original article]() Author: Allison Published: 2026-10-19T10:29:09Z Content type: release Language: en Sources: [GitHub Changelog]() Topics: [Xcode](), [macOS](), [Swift](), [CI/CD]() Tags: [2026](), [actions](), [apple](), [application-security](), [binaries](), [builds](), [code](), [codeql](), [github](), [intel](), [libraries](), [macos](), [macos-27](), [retired](), [swift](), [swift-6-4](), [system](), [trace](), [with](), [x86-64](), [xcode](), [xcode-27]() ### AI overview Starting with macOS 27 and Xcode 27, Apple's removal of Intel code from some system binaries and libraries prevents CodeQL from supporting traced scans on those versions; CodeQL also does not support Swift 6.4 on any platform. With Xcode 27 installed, traced extraction is unavailable for C/C++, C#, Go, Java, Kotlin, and Swift; on macOS 27 it may be unavailable for those languages. Intel Mac support is slated for deprecation in mid-December 2026. The excerpt advises pinning workflows to macOS 26 or earlier and Xcode 26 or earlier, including GitHub Actions runner images and toolchains. For C/C++, C#, and Java, build mode `none` is an option that does not require build tracing. ### Source excerpt Starting with macOS 27 and Xcode 27, Apple no longer includes Intel (x86_64) code in some of the system binaries and libraries that CodeQL relies on to trace builds. As... The post CodeQL changes for macOS 27, Xcode 27, and Swift 6.4 appeared first on The GitHub Blog. ## Xcode 27 runner image generally available DevFeed: [Xcode 27 runner image generally available]() Original publisher: [Read original article]() Author: Allison Published: 2026-10-16T04:36:30Z Content type: release Language: en Sources: [GitHub Changelog]() Topics: [Xcode](), [CI/CD]() Tags: [actions](), [apple](), [applications](), [build](), [image](), [release](), [runner](), [xcode](), [xcode-27]() ### AI overview The Xcode 27 runner image is generally available for building and testing Apple apps in GitHub Actions. It runs on macOS 27 and includes the Xcode 27 toolchain and Apple SDKs; each image tracks one major Xcode version rather than a specific OS version. Use `xcode-27` or `xcode-27-xlarge` as `runs-on` labels. Existing workflows using those labels need no changes. The image is available only on Apple Silicon (arm64), not Intel runners. ### Source excerpt You can now use the generally available Xcode 27 runner image to build and test your Apple applications in GitHub Actions. Previously in public preview, this GitHub-hosted image runs on... The post Xcode 27 runner image generally available appeared first on The GitHub Blog. ## iOS Feature Implementation Using AI \[SUBSCRIBER\] DevFeed: [iOS Feature Implementation Using AI \[SUBSCRIBER\]]() Original publisher: [Read original article]() Author: ehabamer Published: 2026-10-16T00:00:00Z Content type: tutorial Language: en Sources: [Kodeco]() Topics: [AI-assisted coding](), [Multi Agent Systems](), [Expo]() Tags: [accessibility](), [ai](), [git-worktrees](), [multi-agent](), [multimodal-module](), [pull-request-review](), [subscriber](), [worktrees](), [xcode]() ### AI overview This module shows how to use AI to implement an iOS feature from a written plan. It covers creating a multi-agent task sequence, running parallel tasks in separate git worktrees with Conductor, and opening, reviewing, and merging the resulting pull request. Xcode specialist agents then audit the implementation for VoiceOver and Dynamic Type accessibility violations. It assumes completion of a prior iOS feature development module and a paid Claude account. ### Source excerpt This module teaches you how to use AI to carry a planned iOS feature all the way to a reviewed, verified implementation. Starting from a written feature plan, you'll prompt AI to work out an implementation sequence and turn it into a multi-agent workflow that carries out the plan. You'll then use Conductor to run several AI tasks in parallel, each isolated in its own git worktree, and use Conductor itself to open, review, and merge the resulting pull request. Finally, you'll use Xcode's built-in specialist agents to audit the merged implementation for VoiceOver and Dynamic Type accessibility violations. This module does not cover improving the plan itself, fixing bugs in the implemented app, or creating custom agents. Prerequisites: Completion of "AI-Assisted Feature Development for iOS", and a paid Claude account. ## AI Controls iPhone Via ESP32 DevFeed: [AI Controls iPhone Via ESP32]() Original publisher: [Read original article]() Author: Zoe Skyforest Published: 2026-10-15T02:00:25Z Content type: article Language: en Sources: [Hackaday]() Topics: [AI Agent](), [ESP32](), [ESP32-S3](), [ip-kvm](), [iphone]() Tags: [agent](), [ai](), [apple](), [developer](), [device](), [esp32](), [esp32-s3](), [iphone](), [iphone-hacks](), [phone](), [xcode]() ### AI overview The article describes using an ESP32 to give an AI agent access to an iPhone screen through AirPlay mirroring and UxPlay, then control the phone with an ESP32-S3 emulating a USB mouse and keyboard. It says this approach works without an Apple Developer Account, Xcode, or a Mac. ### Source excerpt Do you want to get an AI agent to do something to an iPhone? You could try and jailbreak the device and do some heavy software hacking, or... you could ...read more ## Xcode 27.2 Introduces an Agent- and Merge-Friendly JSON Format for Project Configuration DevFeed: [Xcode 27.2 Introduces an Agent- and Merge-Friendly JSON Format for Project Configuration]() Original publisher: [Read original article]() Author: Sergio De Simone Published: 2026-10-12T09:00:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Xcode](), [JSON](), [project layout](), [XcodeGen](), [Agent Skills]() Tags: [agents](), [ai-coding](), [ai-coding-agents](), [apple](), [build](), [development](), [git](), [ios](), [json](), [merge](), [mobile](), [news](), [xcode](), [xcode-27](), [xcode-json-project-format]() ### AI overview Apple is introducing an open source JSON format for Xcode project configuration in Xcode 27.2, replacing the traditional property-list format. The format is designed to make project files easier to read and maintain, reduce merge conflicts, and help automated tools, including AI coding agents, inspect and modify project settings. Apple also released a Swift package for encoding and decoding the format. Existing projects can be migrated, but developers should first check whether their tools support it. ### Source excerpt Apple is introducing a new JSON-based format for Xcode project configuration files, replacing the traditional property-list-based format. Available in Xcode 27.2, the new format aims to improve readability, simplify maintenance, and make project configuration easier for AI coding agents to understand and modify. By Sergio De Simone ## Getting Started with AI-Augmented Coding in iOS \[SUBSCRIBER\] DevFeed: [Getting Started with AI-Augmented Coding in iOS \[SUBSCRIBER\]]() Original publisher: [Read original article]() Author: ehabamer Published: 2026-10-11T00:00:00Z Content type: tutorial Language: en Sources: [Kodeco]() Topics: [agentic-coding](), [Expo](), [cursor](), [Claude Code](), [MSP MCP](), [React Native]() Tags: [agent](), [agentic](), [agentic-ai](), [ai](), [ai-agent](), [ai-development](), [ai-tools](), [claude](), [coding](), [cursor](), [development](), [how-to](), [ide](), [implement](), [mcp](), [model-context-protocol](), [model-context-protocol-mcp](), [multimodal-module](), [project](), [subscriber](), [swiftui](), [xcode]() ### AI overview Learn to apply agentic AI across iOS development by setting up Claude Agent in Xcode and configuring Cursor. The tutorial covers adding features to an existing SwiftUI app and connecting an external AI tool through MCP to interact with an app in the simulator. ### Source excerpt Learn how to use agentic AI throughout the iOS development process. You'll set up Claude Agent in Xcode and configure Cursor, then use both tools to add features to an existing SwiftUI app. You'll also connect an external AI tool to Xcode through its Model Context Protocol (MCP) server and use an AI agent to interact with an app running in the simulator. ## Introducing RocketTrace: Using Xcode Instruments with AI Agents DevFeed: [Introducing RocketTrace: Using Xcode Instruments with AI Agents]() Original publisher: [Read original article]() Author: Antoine van der Lee Published: 2026-10-05T07:58:25Z Content type: article Language: en Sources: [SwiftLee]() Topics: [Visual Studio Code](), [Claude Code](), [agentic-coding](), [Agent Skills](), [agentic workflows]() Tags: [agents](), [ai](), [ai-agents](), [ai-development](), [coding](), [coding-agent](), [xcode]() ### AI overview RocketTrace is a Mac app that analyzes Xcode Instruments recordings locally and provides ranked, evidence-backed findings for AI coding agents. The article describes its app, CLI, and Agent Skill workflows, then reports a benchmark in which agents using RocketTrace found more performance issues, used about six times fewer tokens, and finished about twice as fast. The author notes that the benchmark used one trace from one app, so it does not establish results for other apps. ### Source excerpt I'm super excited to introduce you to RocketTrace: a Mac app that analyzes your Xcode Instruments recordings and turns them into ranked findings that your AI agent can act on. Instead of asking Claude Code, Codex, or Cursor to dig through a raw performance trace, you give it a compact summary with the evidence it ... -> The post Introducing RocketTrace: Using Xcode Instruments with AI Agents appeared first on SwiftLee. ## iOS 27 Glass You Can Choose, Measure, and Test DevFeed: [iOS 27 Glass You Can Choose, Measure, and Test]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-26T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [iOS](), [Xcode](), [Cloud](), [builds](), [virtualization](), [toolchain](), [Server]() Tags: [animation](), [build](), [cloud](), [handling](), [ios-27](), [macos](), [sdk](), [server](), [settings](), [xcode]() ### AI overview A Codename One release update explains iOS 27 theme support, revised glass materials, tab-selection animation testing, local iPhone Duo posture support, and renewed Xcode version selection for cloud builds. It also describes separate theme generation settings, virtualization for multiple Xcode versions, and local builds using an installed Xcode version. ### Source excerpt Select the iOS 27 theme independently of Xcode, see the revised glass in motion, and explore local iPhone Duo posture support. ## Apple Shouldn't Dictate Your App's Redesign Schedule DevFeed: [Apple Shouldn't Dictate Your App's Redesign Schedule]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-25T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [App](), [Back end](), [iOS](), [Object-relational mapping](), [Xcode](), [OpenTelemetry](), [WebSocket](), [Java]() Tags: [app](), [apple](), [backend](), [java](), [jpa](), [liquid-glass](), [opentelemetry](), [orm](), [websockets](), [xcode]() ### AI overview Codename One announces a series of updates covering optional iOS 27 Liquid Glass themes, Xcode 27 builds, a JPA-inspired ORM, OpenTelemetry, WebSockets, push delivery callbacks, and native desktop themes. ### Source excerpt Adopt Xcode 27 without moving your redesign schedule. This week: Liquid Glass, JPA inspired ORM, OpenTelemetry, WebSockets, push callbacks, and native desktop themes. ## What iOS Developers Need to Change in their Apps to prepare for the iPhone Duo DevFeed: [What iOS Developers Need to Change in their Apps to prepare for the iPhone Duo]() Original publisher: [Read original article]() Author: Sergio De Simone Published: 2026-09-24T19:00:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [iOS](), [iphone](), [layout](), [Xcode](), [SwiftUI](), [navigation](), [Toolbar]() Tags: [apple](), [apple-iphone-duo-api](), [auto-layout](), [configuration](), [developers](), [development](), [ios](), [iphone](), [mobile](), [news](), [swift](), [swiftui](), [ui](), [xcode]() ### AI overview The article explains how iOS developers should adapt apps for the upcoming foldable iPhone Duo. It covers multiple displays and folded states, flexible layouts, navigation and toolbar changes, reserved regions around the fold and camera, and the use of Xcode 27.1 and standard SwiftUI or UIKit APIs. ### Source excerpt With the upcoming introduction of the foldable iPhone Duo, iOS developers will need to adapt their apps to ensure they work correctly across the new device's outer display, larger inner display, and partially folded states. Developers will also need to account changes to navigation and toolbars, camera behavior, and new reserved regions. By Sergio De Simone ## Qt Creator 20.0.2 released DevFeed: [Qt Creator 20.0.2 released]() Original publisher: [Read original article]() Author: eike.ziller@qt.io (Eike Ziller) Published: 2026-09-23T13:32:47Z Content type: release Language: en Sources: [Qt]() Topics: [Qt](), [releases](), [Xcode](), [iOS](), [Android](), [simulator]() Tags: [android](), [biz-circuit](), [biz-circuit-dev-loop](), [dev-loop](), [ios](), [qt](), [qt-creator](), [release](), [releases](), [simulator](), [upgrade](), [version](), [xcode]() ### AI overview Qt Creator 20.0.2 fixes issues with recent Android command-line tool releases and updates compatibility with Xcode 27, the iOS Simulator, and Qt 6.12.0. ### Source excerpt We are happy to announce the release of Qt Creator 20.0.2! The release fixes issues with the recent releases of the Android command line tools, and updates Qt Creator for changes in Xcode 27, the iOS Simulator, and Qt 6.12.0. ## iPhone Duo Simulator: Testing and optimizing your SwiftUI app DevFeed: [iPhone Duo Simulator: Testing and optimizing your SwiftUI app]() Original publisher: [Read original article]() Author: Antoine van der Lee Published: 2026-09-22T10:14:40Z Content type: tutorial Language: en Sources: [SwiftLee]() Topics: [iphone](), [SwiftUI](), [Xcode](), [layout](), [iOS](), [Canvas](), [ipad]() Tags: [apps](), [build](), [devices](), [how-to](), [ios](), [ipad](), [iphone](), [layout](), [optimizing](), [screen](), [simulator](), [swiftui](), [testing](), [xcode]() ### AI overview A tutorial on using the iPhone Duo Simulator in Xcode 27.1 to test SwiftUI apps across different hinge angles, displays, and poses. It explains how to install the simulator and build layouts that respond to available space rather than fixed device identifiers, orientations, or screen widths. ### Source excerpt As soon as the iPhone Duo got announced, we were all waiting for an iPhone Duo Simulator inside Xcode. We eventually got it with the first beta of Xcode 27.1. This Simulator is unlike any other and a lot of fun to explore, allowing you to fold the device into different angles while watching your ... -> The post iPhone Duo Simulator: Testing and optimizing your SwiftUI app appeared first on SwiftLee. ## Xcode 27: The Build Settings That Can Stop a Release DevFeed: [Xcode 27: The Build Settings That Can Stop a Release]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-22T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Xcode](), [builds](), [Deployment](), [iOS]() Tags: [build](), [deployment](), [ios](), [ios-26](), [release](), [watchos](), [xcode]() ### AI overview A release update for Xcode 27 builds explains how deployment floors are resolved from the selected SDK, which build hints were removed, and how launch metadata and scene lifecycle checks affect iOS builds. ### Source excerpt Deployment floors, launch metadata, and scene lifecycle in Xcode 27 builds. ## Automating App Store Screenshots DevFeed: [Automating App Store Screenshots]() Original publisher: [Read original article]() Author: Khan Academy Published: 2017-03-27T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [iOS](), [ui-testing](), [Xcode](), [Sketch](), [Mobile](), [Software Testing]() Tags: [app-store](), [design](), [engineering](), [fastlane](), [ios](), [iphone](), [mobile](), [news](), [screenshots](), [testing](), [ui-testing](), [xcode]() ### AI overview A tutorial describing how Khan Academy automated App Store and Play Store screenshots with Xcode UI tests, Fastlane, a Snapfile, and a homegrown Sketch file. The team reduced screenshot update time from about a week to about an hour. ### Source excerpt By Bryan Clark One of the more tedious design tasks is keeping your App Store promo images up-to-date. ... Read more [Next page]()