# iOS 26 Published articles for iOS 26. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Native is now the future of mobile at Shopify DevFeed: [Native is now the future of mobile at Shopify]() Original publisher: [Read original article]() Author: Simon Willison Published: 2026-09-10T21:11:15Z Content type: opinion Language: en Sources: [Simon Willison's Weblog]() Topics: [Mobile](), [React Native](), [Shopify](), [AI-assisted coding](), [Kotlin](), [Swift](), [Open Source](), [Android](), [Generative AI](), [iOS]() Tags: [ai](), [ai-2-236](), [ai-assisted-search](), [ai-assisted-search-36](), [android](), [android-14](), [coding-agents](), [coding-agents-248](), [generative-ai](), [generative-ai-1-982](), [ios](), [ios-26](), [kotlin](), [llms](), [llms-1-948](), [mobile](), [mobile-41](), [open-source](), [open-source-320](), [react](), [react-43](), [react-native](), [shopify](), [shopify-8](), [swift](), [swift-12]() ### AI overview Shopify is moving its mobile apps from React Native back to separate Swift and Kotlin codebases. The article explains that AI agents can now handle enough implementation, translation, testing, and review work to reduce the cost of maintaining separate platforms. It also notes the planned relocation or archival of Shopify's React Native libraries. ### Source excerpt Native is now the future of mobile at Shopify Shopify are moving from React Native back to separate Swift and Kotlin codebases for their native apps, for the exact reason you would expect: We decided to switch from native to React Native in 2020 for three reasons: Stop building the same features twice Allow developers to work across the stack Spend less time chasing feature parity and more time shipping value [...] Native still means building and maintaining software on two platforms, that cost has not disappeared. What changed is that agents can now do enough of the implementation, translation, testing, and review work that it's no longer the deciding factor it was in 2020. It's a well-written post, which gives full credit to React Native as a great platform for the six years they were using it. Shopify are the maintainers of three significant React Native libraries: react-native-skia, flash-list, and restyle. The first two are finding new homes; the third "has a smaller user base than our other libraries" and will be archived at the end of 2026. Via Hacker News Tags: android, mobile, open-source, ios, ai, react, generative-ai, llms, ai-assisted-search, coding-agents, swift, shopify ## Codename One Tests Statically Linked UI Against iOS 26 and Material 3 References DevFeed: [Codename One Tests Statically Linked UI Against iOS 26 and Material 3 References]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-17T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [ui](), [iOS](), [Accessibility](), [SwiftUI](), [Compose]() Tags: [accessibility](), [benchmarks](), [component](), [design](), [ios](), [ios-26](), [native](), [os](), [simulator](), [swiftui](), [test](), [ui](), [update]() ### AI overview The article explains how Codename One statically links its UI components into native apps so operating-system updates cannot replace their widget implementations. It covers native-fidelity testing against iOS 26 and Material 3, Metal-based rendering, accessibility work, and the tradeoff that Codename One must reproduce design changes itself. ### Source excerpt Codename One now tests its statically linked UI against native iOS 26 and Material 3 references, so themes can move forward without an OS update changing your shipped app. ## CLI 2.4.0: iOS 26 and more devices on Maestro Cloud DevFeed: [CLI 2.4.0: iOS 26 and more devices on Maestro Cloud]() Original publisher: [Read original article]() Author: Proksh Luthra Published: 2026-04-03T06:43:00Z Content type: release Language: en Sources: [mobile.dev - Medium]() Topics: [Command-line interface](), [iOS](), [Android](), [Cloud](), [iphone](), [WebSocket]() Tags: [android](), [api](), [apple](), [cli](), [ios-26](), [linux](), [macos](), [tests](), [update](), [websocket]() ### AI overview Maestro CLI 2.4.0 adds iOS 26 support locally and on Maestro Cloud, expands the available Apple device catalog, and introduces commands that return device values for CLI flags. It also updates device OS formatting, adds web test improvements, and includes fixes and performance improvements. ### Source excerpt You can now test across a much wider range of Apple devices and on iOS 26. ## Everything we shipped at Sketch in 2025 DevFeed: [Everything we shipped at Sketch in 2025]() Original publisher: [Read original article]() Author: Freddie Harrison Published: 2025-12-16T08:00:00Z Content type: article Language: en Sources: [Sketch Blog]() Topics: [Sketch](), [releases](), [liquid glass](), [User interface design](), [macOS](), [iOS]() Tags: [2026](), [apple](), [apps](), [auto-layout](), [icons](), [ios-26](), [keyboard](), [latest-features](), [layout](), [liquid-glass](), [macos](), [releases]() ### AI overview Sketch reviews its 2025 product work, including the Athens, Barcelona, and Copenhagen releases. The updates introduced Stacks and Frames, expanded the Command Bar, added a glass effect for iOS and macOS 26 design, and included an MCP server and broader redesign work. ### Source excerpt From Stacks and Frames, to Glass effects and a complete macOS Tahoe redesign -- here's everything we shipped at Sketch in 2025. ## SwiftUI Custom URL Schemes DevFeed: [SwiftUI Custom URL Schemes]() Original publisher: [Read original article]() Author: Keith Harrison Published: 2025-10-27T11:26:47Z Content type: tutorial Language: en Sources: [K. Harrison]() Topics: [SwiftUI](), [WebView](), [iOS](), [WebKit](), [App]() Tags: [async](), [auto-layout](), [configuration](), [how-to](), [ios](), [ios-26](), [objective-c](), [protocol](), [scheme](), [swift](), [swiftui](), [web](), [webview](), [wwdc](), [xcode]() ### AI overview This tutorial explains how to create a custom URL scheme handler for SwiftUI WebViews in iOS 26. It covers implementing URLSchemeHandler, loading local HTML resources from an app bundle, registering the handler in a WebPage configuration, and displaying the page in a WebView. ### Source excerpt Create a custom URL scheme handler for SwiftUI WebViews. Custom URL schemes Apple introduced both WebView and WebPage SwiftUI views in iOS 26. These provide similar WebKit functionality to the UIKit WKWebView APIs. This includes being able to register custom URL schemes to load local resources. Suppose I have an App that loads quotations from the local App bundle. My URL scheme uses the format: quotes://001.html There are a few steps to support a custom URL scheme: Create a custom URL scheme handler that knows how to load the local resources. Register the scheme handler in a WebPage configuration. Have the WebView load and display the web page. Let's look at each of those steps. URLSchemeHandler (iOS 26) The URLSchemeHandler is a protocol with a reply method to return an async sequence of results. The AsyncSequence expects us to either yield a URLResponse and some data or throw an error. struct QuoteSchemeHandler: URLSchemeHandler { static let scheme = "quotes" func reply(for request: URLRequest) -> some AsyncSequence< URLSchemeTaskResult, any Error > { AsyncThrowingStream { continuation in ... } } } The reply method provides us with the URLRequest. I start by extracting the URL and checking it matches our quotes scheme: guard let url = request.url else { continuation.finish(throwing: QuoteError.missingURL) return } guard url.scheme == QuoteSchemeHandler.scheme else { continuation.finish(throwing: QuoteError.invalidScheme) return } To construct the URL response I need the mime type and length of the data. I first extract the filename from the URL, determine the mime type from the file extension, and then load the data: do { let file = try filename(for: url) let mimeType = try mimeType(for: file) let data = try Data(contentsOf: file) I can then build the URLResponse: let response = URLResponse( url: url, mimeType: mimeType, expectedContentLength: data.count, textEncodingName: "utf-8" ) If nothing has gone wrong I then add the response and the data to the AsyncSequenc ## iPhone 17 Screen Sizes DevFeed: [iPhone 17 Screen Sizes]() Original publisher: [Read original article]() Author: Keith Harrison Published: 2025-10-13T09:44:39Z Content type: article Language: en Sources: [K. Harrison]() Topics: [iphone]() Tags: [apple](), [auto-layout](), [display](), [features](), [ios](), [ios-26](), [iphone](), [objective-c](), [screen](), [swift](), [wwdc](), [xcode]() ### AI overview This article compares the screen sizes and display specifications of the iPhone 17 lineup. The iPhone 17 and iPhone 17 Pro share a 6.3-inch display, the iPhone 17 Pro Max has a 6.9-inch display, and the new iPhone Air has a 6.5-inch display. It also covers display features, resolutions, safe-area insets, materials, and USB-3 transfer support. ### Source excerpt There's less variation this year with the base iPhone 17 and Pro models sharing a display. The Plus model is gone but we get a new iPhone Air. Here's what you need to know about the iPhone 17 models. The New Models in a Nutshell There's no iPhone 17 Plus model this year. Instead the iPhone 17 gets the same 6.3" display as the iPhone 17 Pro. The Pro Max keeps the 6.9" display from last year. Finally, we have the new iPhone Air with a 6.5" display. Apple continues to sell the base iPhone 16, 16 Plus, and the iPhone 16e. That gives this years models three different screen sizes: The 6.3" display in the iPhone 17 and 17 Pro has almost the same specs as the iPhone 16 Pro. That brings features such as ProMotion and the Always-on display to the base iPhone 17. The only difference I can see is an increased peak brightness of 3,000 nits (up from 2,000 nits). The Titanium frame of last years Pro models is replaced with an Aluminium unibody. The base iPhone 17 has an Aluminium frame but the iPhone Air has a Titanium frame. Support for USB-3 (10Gbp/s) transfer speeds is still limited to the Pro models. iPhone 17 The base iPhone 17 display upgrades to a spec comparable to the iPhone 16 Pro 6.3" display with ProMotion and Always-on, along with the A19 chip. A19 chip (6-core CPU, 5-core GPU with Neural Accelerators, 16-core Neural Engine) Display: 6.3" Super Retina XDR OLED with ProMotion, Always-On display, and Dynamic Island Screen resolution (points): 402 x 874 Native resolution (pixels): 1206 x 2622 (460 ppi) Native Scale factor: 3x Portrait size classes: w: Compact, h: Regular Landscape size classes: w: Compact, h: Compact The status bar is 54 points high with a top safe area inset of 62 points which gives the following safe area insets: Safe Area Insets (portrait): top: 62, bottom: 34, left: 0, right: 0 Safe Area Insets (landscape): top: 20, bottom: 20, left: 62, right: 62 Note: In landscape there's now a top safe area inset of 20 points. iPhone 17 Pro The iPhone 17 Pro is f