# SwiftUI Published articles for SwiftUI. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## SwiftUI Agent Skill: Install and use with AI coding tools DevFeed: [SwiftUI Agent Skill: Install and use with AI coding tools]() Original publisher: [Read original article]() Author: Antoine van der Lee Published: 2026-09-14T11:49:33Z Content type: article Language: en Sources: [SwiftLee]() Topics: [SwiftUI](), [Agent Skill](), [ai-coding](), [Code quality](), [context window](), [Command-line interface]() Tags: [agent-skill](), [ai-coding](), [ai-development](), [cli](), [code-quality](), [context-window](), [installation](), [open-source](), [swiftui]() ### AI overview This article introduces an open-source SwiftUI Agent Skill for AI coding tools. The skill helps agents build or refactor SwiftUI views, improve generated code quality, and load focused references only when they are relevant to a task. It also explains installation, updates, and compatibility considerations for the skills command-line tool. ### Source excerpt A SwiftUI Agent Skill that helps you build better views or refactor existing ones. It's the reality we're in today, and I honestly can't live without it anymore myself. Several skills helped me improve the code quality produced by agents, and I'm happy to introduce you to my open-source skill for SwiftUI. Before reading this ... -> The post SwiftUI Agent Skill: Install and use with AI coding tools appeared first on SwiftLee. ## Moving from XCTest to Swift Testing \[FREE\] DevFeed: [Moving from XCTest to Swift Testing \[FREE\]]() Original publisher: [Read original article]() Author: renan.dias Published: 2026-09-11T18:41:42Z Content type: tutorial Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [Swift Testing](), [Unit testing](), [Xcode](), [agentic-coding](), [SwiftUI](), [iOS]() Tags: [agentic](), [agentic-ai](), [app](), [apple](), [article](), [free](), [how-to](), [ios](), [swift-testing](), [swiftui](), [testing](), [xcode]() ### AI overview A tutorial on migrating unit tests from Apple's XCTest framework to Swift Testing. It explains common testing scenarios, Swift Testing's newer syntax and constructs, and how Xcode's Agentic Coding can assist with the migration while working on a SwiftUI coffee-ordering app. ### Source excerpt Swift Testing is Apple's replacement for the objective-C XCTest unit testing framework. Discover how to migrate your existing XCTest suites over to Swift Testing, including how to get some assistance from Xcode's agentic AI tooling. ## Every animation was one rename away from breaking a live show DevFeed: [Every animation was one rename away from breaking a live show]() Original publisher: [Read original article]() Author: Whatnot Engineering Published: 2026-09-10T16:31:01Z Content type: tutorial Language: en Sources: [Whatnot Engineering]() Topics: [iOS](), [Swift](), [Code](), [SwiftUI]() Tags: [animation](), [code](), [ios-app-development](), [software-development](), [swift](), [swiftui]() ### AI overview This engineering post explains how a designer's property rename could silently break a production iOS animation because Swift code referenced asset properties through string literals. It describes replacing hand-written bindings with generated animation binding code from asset files so the compiler can enforce the contract and reduce reliance on tribal knowledge. ### Source excerpt Seth Sandler There's a bug we never shipped, and it kept me up anyway. Here's how it goes: a designer renames a property from purchaseCount to purchase_count inside an animation file. Every place our Swift code references that property is a string literal. The build stays green. Code review passes; nothing in the diff even mentions animations. And the celebration animation at the heart of our live auctions silently stops firing, in production, in front of a live audience. Nothing stood between us and that outcome except everyone remembering to be careful. And the strings were only the most visible tripwire. Driving our animation runtime correctly also meant knowing things the compiler never checks: call order, load timing, which properties were designer-internal and untouchable, how not to leak memory. Every engineer touching an animation had to know all of it, and every new animation was another chance to get it wrong. If you've done animation work on iOS, some version of this unease is familiar. This post is the story of how we defused it: by generating the entire animation binding layer from the asset files themselves, so the compiler enforces the contract and the generated code encodes the nuance. The methodology isn't specific to our stack, our vendor, or our app. If your code talks to any designer-owned asset through string literals and tribal knowledge, you can build this too. Why hand-rolled animation code collapses Our first instinct, like every iOS team's, was to build the animations ourselves. SwiftUI has withAnimation. Core Animation has CAKeyframeAnimation. We'd shipped complex UI before. How hard could it be? The animation we were building wasn't a loop. It was state-driven: it needed a user's avatar, their name, a running count that ramps up the visuals, and different behavior depending on who's watching. Each input changes the intro, the escalation, the outro. In native Swift, that decomposed into: State explosion. A @State for the image, a @Binding ## jetc.dev Newsletter Issue #330 DevFeed: [jetc.dev Newsletter Issue #330]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-09-08T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [compose-multiplatform](), [Compose](), [tvOS](), [Android](), [Testing](), [SwiftUI](), [JavaScript](), [TypeScript](), [Ktor]() Tags: [2026](), [android](), [compose-multiplatform](), [dev](), [ios](), [newsletter](), [swiftui](), [testing](), [typescript]() ### AI overview Newsletter Issue #330 covers Compose Multiplatform support for Apple tvOS, lessons from Android foldables for potential foldable iPhone development, testing and recomposition issues, image-loading test techniques, animated number transitions, and related Compose tools and libraries. ### Source excerpt Apple TV! Apple foldables! Microsoft Office! And other topics not necessarily involving gigantic firms! ## Migrating Doximity's iOS Newsfeed to SwiftUI Without Disrupting Users or Development DevFeed: [Migrating Doximity's iOS Newsfeed to SwiftUI Without Disrupting Users or Development]() Original publisher: [Read original article]() Author: Doximity Published: 2026-09-04T10:50:00Z Content type: tutorial Language: en Sources: [Doximity]() Topics: [iOS](), [SwiftUI](), [Development](), [App]() Tags: [app](), [architecture](), [bridge](), [development](), [incremental](), [ios](), [migration](), [swiftui]() ### AI overview This article describes Doximity's incremental migration of its iOS Newsfeed from UIKit to SwiftUI. The team moved one section at a time, kept UIKit and SwiftUI compatible, continuously measured behavior, and made each step reversible. The feed's server-driven card and section architecture, with state and logic managed in The Composable Architecture, provided the migration boundary. ### Source excerpt The Newsfeed is one of the most-used features in the Doximity iOS app. It is the first thing many users see when they open the app. For doctors checking in between patients or residents catching up during a break, it has to be fast and efficient. Those expectations defined success for the migration. Feature work had to continue, analytics had to remain reliable, and the experience had to remain familiar to users even as the underlying implementation changed. We approached the migration less like a rewrite and more like a controlled rollout. We moved one section at a time, kept the UIKit and SwiftUI implementations compatible, measured behavior continuously, and made each step reversible. The technical bridge enabled the migration, but this incremental approach reduced the risk to the product. The Newsfeed brings several types of content together in a single scrolling experience. Here are a few examples of the different cards users may encounter: The Architecture Behind the Newsfeed Before discussing the migration, it helps to understand the architecture that made our incremental approach possible. The Newsfeed is not one large custom view. It is a server-driven list built from cards, with each card assembled from smaller sections. The server controls the composition of the feed. It tells the app which cards should appear, which sections belong inside each card, and the order in which those sections should render. The iOS app owns the rendering and behavior of each known section type. This separation makes the feed flexible. Rather than relying on a fixed set of hardcoded card types, the server can compose cards from reusable sections such as headlines, authors, summaries, media, polls, and social actions. By combining and ordering those sections differently, the server can create different card layouts without requiring a new implementation in the app. This is roughly what the model looks like: Server-driven feed response Newsfeed ├─ Card │ ├─ Section: author │ ├─ S ## MVVM in SwiftUI: Using view models without overengineering DevFeed: [MVVM in SwiftUI: Using view models without overengineering]() Original publisher: [Read original article]() Author: Antoine van der Lee Published: 2026-08-31T13:10:23Z Content type: tutorial Language: en Sources: [SwiftLee]() Topics: [SwiftUI](), [Code]() Tags: [code](), [developers](), [how-to](), [swiftui]() ### AI overview This tutorial explains how to use the MVVM architectural pattern in SwiftUI. It describes separating views from presentation state and actions through view models, while emphasizing that view models should be introduced when they provide meaningful organization or testability rather than added to every view. ### Source excerpt MVVM in SwiftUI separates a view's presentation from the state and actions behind it. A view model exposes the values a view displays and handles work such as loading, validation, or deletion, while the view remains focused on rendering. SwiftUI already provides powerful tools for state management, so not every view needs a view model. I ... -> The post MVVM in SwiftUI: Using view models without overengineering appeared first on SwiftLee. ## Consuming SKIE Flows in SwiftUI - Gustavo Fão Valvassori DevFeed: [Consuming SKIE Flows in SwiftUI - Gustavo Fão Valvassori]() Original publisher: [Read original article]() Published: 2026-08-29T00:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [SwiftUI](), [Kotlin](), [Swift](), [Extension]() Tags: [boilerplate](), [community](), [extensions](), [interop](), [kmp](), [kotlin](), [kotlin-multiplatform](), [libraries](), [open-source](), [skie](), [swiftui]() ### AI overview This tutorial explains how to consume Kotlin Flows in SwiftUI using SKIE. It covers enabling SKIE extensions in Gradle and collecting StateFlow values through an async collect approach, a modifier, or a view wrapper to reduce repetitive UI-layer code. ### Source excerpt SKIE already makes the interop between Kotlin and Swift smooth, but SwiftUI adds a layer of complexity. We've included a series of extensions in SKIE to enable easy KMP usage from SwiftUI ## @StateObject vs. @ObservedObject: The differences explained DevFeed: [@StateObject vs. @ObservedObject: The differences explained]() Original publisher: [Read original article]() Author: Antoine van der Lee Published: 2026-08-24T14:05:36Z Content type: article Language: en Sources: [SwiftLee]() Topics: [SwiftUI](), [iOS](), [Code]() Tags: [code](), [framework](), [ios](), [model](), [observedobject](), [propertywrapper](), [published](), [rebuilds](), [stateobject](), [swiftui]() ### AI overview This article explains the difference between SwiftUI's @StateObject and @ObservedObject property wrappers. Use @StateObject when a view creates and owns an ObservableObject, and use @ObservedObject when the object is supplied by another view. It also explains how inline object creation can reset view models, contrasts these wrappers with the ObservableObject protocol, and recommends the Observation framework for new code targeting iOS 17 and later. ### Source excerpt @StateObject and @ObservedObject both connect an ObservableObject to a SwiftUI view. The key difference is ownership: use @StateObject when the view creates the object and @ObservedObject when the view receives it from elsewhere. Choosing the wrong wrapper can cause your model to be recreated whenever SwiftUI rebuilds a view. I made this mistake myself because both wrappers initially appeared to produce the same result. ... -> The post @StateObject vs. @ObservedObject: The differences explained appeared first on SwiftLee. ## Watch Apps: One Codebase, Two Real Applications DevFeed: [Watch Apps: One Codebase, Two Real Applications]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-22T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [SwiftUI](), [Android](), [media3](), [SQLite](), [API]() Tags: [android](), [api](), [apk](), [apple](), [apple-watch](), [asynchronous](), [files](), [release](), [sqlite](), [state](), [swiftui](), [watchos]() ### AI overview Codename One can build Apple Watch companion applications and Wear OS applications from a shared watch entry point. The article explains separate application runtimes and storage, platform-specific rendering, and asynchronous communication for live messages, replicated state, and file transfers. ### Source excerpt Codename One now builds Apple Watch companions and standalone Wear OS products from one watch entry point, with a portable asynchronous API for messages, state, and files. ## Add native AuthKit sign-in to your iOS app with the WorkOS iOS SDK DevFeed: [Add native AuthKit sign-in to your iOS app with the WorkOS iOS SDK]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-10T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [iOS](), [pkce](), [SDKs](), [Swift](), [SwiftUI](), [Mobile](), [browser]() Tags: [authorization](), [browser](), [guide](), [ios](), [mobile](), [pkce](), [sdk](), [sign-in](), [swift](), [swiftui](), [tutorial]() ### AI overview A step-by-step tutorial for adding native AuthKit sign-in to a SwiftUI iOS app using the WorkOS iOS SDK and its PublicClient. It explains configuring redirect URIs, adding the SDK, and starting a PKCE flow without embedding an API key or client secret in the app. ### Source excerpt A step-by-step guide to PKCE-based sign-in with the WorkOS iOS SDK's PublicClient. ## 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. ## Building Native Apple Watch Apps with Codename One DevFeed: [Building Native Apple Watch Apps with Codename One]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-21T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [watchOS](), [SwiftUI](), [Code](), [iOS](), [Android](), [Java](), [Kotlin]() Tags: [android](), [apple](), [code](), [ios](), [native](), [pipeline](), [swiftui](), [watchos]() ### AI overview This article explains how Codename One supports Apple Watch and Wear OS applications from a shared Java or Kotlin codebase. It describes the watchOS port's dedicated Core Graphics backend, SwiftUI shell, generated watch application target, and handling of watch-specific input and UI constraints. ### Source excerpt The new native Apple Watch port runs real Codename One UI on watchOS through a dedicated Core Graphics backend inside a SwiftUI shell, while Wear OS rides the existing Android pipeline. The same code base, branched with CN.isWatch(), reaches both platforms, seamlessly! ## WWDC 2026 Viewing Guide DevFeed: [WWDC 2026 Viewing Guide]() Original publisher: [Read original article]() Author: Keith Harrison Published: 2026-06-15T09:16:45Z Content type: tutorial Language: en Sources: [K. Harrison]() Topics: [Swift](), [SwiftUI](), [Xcode](), [WebAssembly](), [gRPC](), [MLX](), [NumPy](), [Testing]() Tags: [2026](), [apple](), [auto-layout](), [comparison](), [ios](), [ios27](), [macos27](), [objective-c](), [swift](), [swiftui](), [webassembly](), [wwdc](), [xcode]() ### AI overview A guide to planning and watching WWDC 2026 sessions, highlighting platform themes and selected updates in Swift, SwiftUI, Xcode, WebAssembly, gRPC, and MLX. ### Source excerpt My WWDC 2026 viewing guide to help you plan the sessions you want to watch. Where Do I Start? The two big themes for the year are again Liquid Glass and Apple Intelligence. Start by watching the Platforms State of the Union (SOTU) for a summary of what's new this year. If you only have five minutes try the SOTU recap. You don't have to learn everything new today! There are over 100 sessions and a lot of new stuff to learn. You may feel like you're getting left behind. Don't let it overwhelm you. You've got time. Don't burn yourself out trying to keep up. Watching The Sessions I watch the videos using the Apple Developer app. It's available on macOS and iOS. The video player supports from 0.5x to 2x playback, most videos have transcripts and summaries, and allow copying of the onscreen sample code. You can also watch on YouTube. There are a lot of sessions, but many are short (15-20 minutes). There's no padding and Apple's engineers get to the point quickly. Swift Swift 6.4 is here with some quality of life improvements: What's new in Swift Condense long @available attributes with anyAppleOS, @diagnose to control compiler deprecation warnings. Double-colon module selector. Standard Library task cancellation shield, dictionary mapKeyedValues, new FilePath type. XCTest interop with Swift Testing. Subprocess 1.0. New ProgressManager. @C attribute for Swift-C interop. Compile to WebAssembly. New @inline(always) and @specialized attributes. Iterable protocol for noncopyable elements. Build real-time apps and services with gRPC and Swift gRPC Swift package to generate and deploy network code for remote procedure call services. Explore numerical computing in Swift with MLX NumPy-like API. Examples of computing the Mandlebrot set, heat distribution, and curve fitting. SwiftUI Liquid Glass changes and some welcome improvements: What's new in SwiftUI Liquid Glass is now mandatory. Minimal menu icons by default. Resize live previews in Xcode. Prominent tab role. Toolbar visibil ## How The New York Times Games Team Delivered Accessible, Cross-Platform Dark Mode DevFeed: [How The New York Times Games Team Delivered Accessible, Cross-Platform Dark Mode]() Original publisher: [Read original article]() Author: The NYT Open Team Published: 2026-04-16T15:35:45Z Content type: article Language: en Sources: [New York Times]() Topics: [Dark Mode](), [Mobile](), [Android](), [iOS](), [Jetpack Compose](), [ui](), [Design system](), [XML](), [pull-requests](), [SwiftUI](), [Objective-C]() Tags: [accessible](), [android](), [collaboration](), [cross-platform](), [dark-mode](), [design](), [design-system](), [engineering](), [ios](), [jetpack-compose](), [pull-requests](), [swiftui]() ### AI overview The New York Times Games team describes implementing accessible, brand-consistent dark mode across its mobile app. The work coordinated design and engineering across Android and iOS, including XML and Jetpack Compose screens, legacy and modern interfaces, shared assets, external libraries, and testing. ### Source excerpt Bringing accessible, brand-consistent dark mode to life in The New York Times Games app through cross-platform design and engineering collaboration.Illustration by Allie Sullberg By Vanessa Johnson, Daniel Falokun, Michael Ingber and Oleksandr Zabiiako The Games Mobile App introduced dark mode back in October. This seamless implementation was a collaborative effort, requiring careful planning and management of design, cross-platform coordination, and engineering work across both legacy and modern user interface systems. The process to implement dark mode across the app included consideration on the visuals, colors, and icons that are mode specific to maintain legibility and brand consistency. The New York Times Games team is excited to have delivered this feature before the end of 2025, and thrilled to be able to roll out a feature that continues to make our app accessible for all. Development Work on Mobile On the development side, the mobile and web engineers synchronized assets which were colors, fonts, and images to ensure that hybrid screens showed the correct styles and colors. This was possible since our design system across mobile was constructed in a way that encouraged consistency and scalability across platforms. With clear and easy to follow designs supported by our internal design system, Android and iOS could ensure consistency on both platforms. Screens in dark mode From an Android perspective, it required separate approaches for XML (Extensive Markup Language) based screens which use an imperative, hierarchical approach and Jetpack Compose screens that use a more modern declarative approach. XML and Jetpack Compose are different ways the UI can be constructed. To ensure dark mode compatibility, all features were revisited to make sure they were adapted, especially the additions that were being worked on during the dark mode project. Another aspect of this development was updating external libraries that required making pull requests, creating a versi ## Когда данных от Apple недостаточно: собираем метрики производительности UI DevFeed: [Когда данных от Apple недостаточно: собираем метрики производительности UI]() Original publisher: [Read original article]() Author: hurmavbatone (hh.ru) Published: 2026-01-26T14:02:45Z Content type: tutorial Language: ru Sources: [HeadHunter RU]() Topics: [iOS](), [SwiftUI](), [ui]() Tags: [apple](), [fps](), [ios](), [swiftui](), [tag-b92bf5906bbd](), [tag-c6d5400b7d88](), [tag-cb5ff012b3f0](), [ui](), [uikit]() ### AI overview An iOS developer from hh.ru describes building custom UI performance metrics collection after Apple's default data proved insufficient for investigating user-reported freezes and slowdowns. The article discusses the company's SwiftUI- and UIKit-based applications and metrics such as Hitch Rate, Hang Rate, and FPS. ### Source excerpt Привет, Хабр! Меня зовут Виталий Барабанов, я iOS-разработчик в hh.ru. Недавно мы столкнулись с проблемой: пришёл фидбэк от пользователей о тормозах и фризах в мобильном приложении. Но чтобы установить их причину, нам не хватило данных, которые по дефолту собирает Apple. Что делать в такой ситуации? А запилить собственный сбор метрик: с какой угодно фильтрацией, сбором любой информации, интеграцией со своей аналитикой и наблюдением в дебаг-панели! В статье я хочу поделиться с Хабром, как мы это сделали, сколько времени потратили и как интерпретировали результаты. Читать далее ## 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 ## Rafinad: сахар для UI-тестирования iOS-приложений DevFeed: [Rafinad: сахар для UI-тестирования iOS-приложений]() Original publisher: [Read original article]() Author: almazrafi (hh.ru) Published: 2025-05-26T08:35:00Z Content type: tutorial Language: ru Sources: [HeadHunter RU]() Topics: [iOS](), [Open Source](), [ui]() Tags: [dsl](), [ios](), [open-source](), [source](), [swift](), [swiftui](), [tag-e932065bc8da](), [ui](), [ui-3e41457d883f](), [ui-5cd5d1ae7fcb](), [uikit](), [xctest](), [xcuitest]() ### AI overview The article introduces Rafinad, an open-source project from hh for UI testing of iOS applications. It explains why the company is revisiting its older testing approach and demonstrates common UI-test implementations, including explicit element identification and shared identifier sources. ### Source excerpt Мы в hh очень любим UI-тесты, ими покрывается практически вся функциональность наших приложений, и даже backend-разработчики прогоняют тесты мобильных платформ перед развертыванием своих фич. Однако наши механизмы UI-тестирования разрабатывались более 8 лет назад и с тех пор почти не изменились. Кто-то скажет, что старые решения прошли проверку временем и что "работает -- не трогай"... Возможно, и так. Но сейчас мы внедряем новую дизайн-систему, а новые компоненты требуют адаптации всех тестов -- не лучшее ли время для перемен? Поэтому мы пересмотрели наши подходы к UI-тестированию и теперь готовы поделиться наработками с сообществом в виде open-source проекта -- Rafinad. В этой статье расскажем, что он умеет и как им пользоваться. Читать далее ## Apple Intelligence DevFeed: [Apple Intelligence]() Original publisher: [Read original article]() Published: 2024-09-20T00:00:00Z Content type: article Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [iOS](), [AI Development](), [SwiftUI](), [Swift](), [ChatGPT](), [Front end]() Tags: [ai](), [ai-apis](), [apple](), [chatgpt](), [git](), [ios](), [program](), [swift](), [swiftui](), [vision]() ### AI overview A program description for an eight-week course on integrating Apple Intelligence into iOS apps. The curriculum covers Genmoji, Siri integration, Apple machine-learning models for translation and computer vision, and third-party tools such as ChatGPT, with prerequisites in SwiftUI, networking, concurrency, APIs, Git, and GitHub. ### Source excerpt Discover the multitude of ways to integrate Apple Intelligence into your apps, from creating amazing user experiences through Genmoji and deep integration with Siri, through leveraging Apple's ML models for translation and computer vision, to building on third-party tools such as ChatGPT. ## Droidcon NYC 2024 App Update - Tadeas Kriz DevFeed: [Droidcon NYC 2024 App Update - Tadeas Kriz]() Original publisher: [Read original article]() Published: 2024-09-13T00:00:00Z Content type: release Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [compose-multiplatform](), [Android](), [iOS](), [App](), [multiplatform]() Tags: [android](), [compose](), [compose-multiplatform](), [design](), [droidcon](), [features](), [google-play](), [ios](), [kotlin](), [kotlin-multiplatform](), [push-notifications](), [swiftui](), [update]() ### AI overview Touchlab describes updates to the Droidcon NYC 2024 Android and iOS apps, including a Compose Multiplatform venue map, push notifications for attendee messaging, background schedule updates, and Material 3 theming. It also previews a universal Droidcon app for future events. ### Source excerpt We've updated the Droidcon NYC 2024 app with a new design and features. The app now uses Material 3 theming, and includes push notifications for in-conference messaging. ## Getting Started with SwiftUI DevFeed: [Getting Started with SwiftUI]() Original publisher: [Read original article]() Published: 2024-06-20T00:00:00Z Content type: tutorial Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [SwiftUI](), [iOS](), [User Interfaces](), [User interface design]() Tags: [apple](), [badge](), [course](), [getting-started](), [guide](), [how-to](), [ios](), [learning](), [swiftui](), [user-interface](), [user-interfaces]() ### AI overview A beginner learning path that introduces SwiftUI, Apple's declarative user interface framework for iOS development. It covers views, view hierarchies, custom views, adaptive interfaces, and navigation. ### Source excerpt This course introduces the fundamental concepts of SwiftUI, Apple's declarative user interface framework for building iOS applications. You'll delve into the world of SwiftUI, learning how to create responsive user interfaces with ease. The course covers essential topics such as views, hierarchies and navigation providing a solid foundation for developing iOS apps. ## Networking & Concurrency in SwiftUI DevFeed: [Networking & Concurrency in SwiftUI]() Original publisher: [Read original article]() Published: 2024-06-20T00:00:00Z Content type: tutorial Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [iOS](), [SwiftUI](), [Concurrency](), [networking](), [JSON](), [Optimization](), [Programming]() Tags: [concurrency](), [course](), [http](), [ios](), [json](), [memory](), [networking](), [performance](), [programming](), [swiftui]() ### AI overview A beginner-oriented learning path covering networking and concurrency in SwiftUI for iOS development. It teaches network protocols, HTTP requests and responses, URLSession, JSON parsing, asynchronous programming, multithreading, performance optimization, and memory management. ### Source excerpt In this course, you'll delve into the fundamentals of networking and concurrency in iOS development. You'll gain a thorough understanding of network communication protocols, asynchronous programming techniques, and best practices for building high-performance iOS apps. This course is designed for beginners who want to gain confidence in the intricacies of networking and concurrency in the context of iOS development. ## Beginning iOS & Swift DevFeed: [Beginning iOS & Swift]() Original publisher: [Read original article]() Published: 2024-06-20T00:00:00Z Content type: tutorial Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [iOS](), [Swift](), [SwiftUI](), [User Interfaces](), [Xcode](), [Data Management](), [Persistence](), [Programming](), [networking](), [Optimization]() Tags: [apple](), [apps](), [building](), [developer](), [guide](), [ios](), [program](), [programming](), [swift](), [swiftui](), [tools](), [ui](), [user-interfaces](), [xcode]() ### AI overview A 15-week Kodeco program for learning iOS app development with Swift, SwiftUI, and Xcode. It covers user interfaces, navigation, data management, persistence, networking, and performance optimization through structured content, projects, and mentor feedback. ### Source excerpt The Kodeco Beginning iOS & Swift program provides a comprehensive learning experience guided by experienced industry professionals. Gain the in-demand skills you need to excel in building modern iOS apps using Apple's revolutionary UI framework, SwiftUI. You'll begin with an introduction to Apple's Swift programming language, Xcode, and version control. Once you have the fundamental concepts you will learn SwiftUI and craft captivating user interfaces. You'll effortlessly guide users through your apps with built-in navigation tools. As the program progresses you'll navigate your way towards the power of data management, including passing data, state management, and data persistence for dynamic apps. Take a step further with networking and performance optimization techniques, ensuring your apps run smoothly. With the help of your mentor you can progress with confidence, ensuring you have a firm grasp of each concept. This program provides you with the tools to maximize your learning potential towards becoming a sought after iOS developer. ## Sharing & State Management in SwiftUI DevFeed: [Sharing & State Management in SwiftUI]() Original publisher: [Read original article]() Published: 2024-06-20T00:00:00Z Content type: tutorial Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [SwiftUI](), [data](), [Persistence](), [User Interfaces]() Tags: [course](), [data](), [learning](), [persistence](), [swiftui](), [techniques](), [user-interfaces]() ### AI overview A SwiftUI learning path covering data flow, data binding, state management, and data persistence techniques using SwiftData and UserDefaults. ### Source excerpt In this course, you will delve into the intricacies of data flow and data binding in SwiftUI, gaining an understanding of how to seamlessly transfer information between different views. You will also explore state management strategies and data persistence techniques. ## Publishing a Kotlin Multiplatform Android, iOS, and macOS app with GitHub Actions DevFeed: [Publishing a Kotlin Multiplatform Android, iOS, and macOS app with GitHub Actions]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2024-05-21T00:00:00Z Content type: tutorial Language: en Sources: [Posts on Marco Gomiero]() Topics: [GitHub Actions](), [Kotlin Multiplatform](), [CI/CD](), [Android](), [compose-multiplatform](), [iOS](), [macOS](), [GitHub](), [Jetpack Compose](), [SwiftUI](), [Open Source]() Tags: [android](), [ci](), [compose-multiplatform](), [github](), [github-actions](), [ios](), [jetpack-compose](), [kotlin-multiplatform](), [macos](), [open-source](), [swiftui]() ### AI overview This article introduces a series of posts about using GitHub Actions CI to publish the FeedFlow Kotlin Multiplatform app to Google Play, the iOS and macOS App Stores, and GitHub Releases. FeedFlow targets Android, iOS, and macOS, using Jetpack Compose, Compose Multiplatform, and SwiftUI. ### Source excerpt It's been almost a year since I started working on FeedFlow, an RSS Reader available on Android, iOS, and macOS built with Jetpack Compose for the Android app, Compose Multiplatform for the desktop app, and SwiftUI for the iOS app. To be faster and "machine-agnostic" with the deployments, I decided to have a CI (Continuous Integration) on GitHub Actions to quickly deploy my application to all the stores (Play Store, App Store for iOS and macOS, and on GitHub release for the macOS app). [Next page]()