# watchOS Apple platform for building apps for the wrist. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Watch Follow-Through: Complications, Tiles, and a Companion Wear APK DevFeed: [Watch Follow-Through: Complications, Tiles, and a Companion Wear APK]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-31T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [watchOS](), [Android](), [APK](), [App]() Tags: [android](), [apk](), [release](), [watchos]() ### AI overview Codename One now generates watchOS WidgetKit complications, Wear OS complication data sources and Tiles, and a companion Wear APK alongside the phone artifact. The article also explains platform-specific rendering limits and simulator behavior. ### Source excerpt Codename One now generates watchOS WidgetKit complications, Wear OS complication data sources and Tiles, and a companion Wear APK beside the phone artifact. ## SQLite Across Every Port: One Contract, One Encrypted File Format DevFeed: [SQLite Across Every Port: One Contract, One Encrypted File Format]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-21T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [SQLite](), [Encryption](), [Android](), [iOS](), [JavaScript](), [Linux](), [simulator](), [Windows](), [tvOS](), [watchOS]() Tags: [android](), [encryption](), [ios](), [javascript](), [linux](), [simulator](), [sqlite](), [watchos](), [windows]() ### AI overview Codename One describes a unified, tested SQLite contract across its supported ports, replacing platform-dependent implementations. The update also supports encrypted database files that can move between ports and open in standard SQLCipher 4 clients, using passphrase, managed-key, or raw-key encryption. ### Source excerpt Codename One now runs the same tested SQLite contract across Android, iOS, JavaScript, Windows, Linux, watchOS, tvOS, and the simulator, with passphrase, managed-key, and raw-key encryption. ## Companion app: Changing support for Apple platforms DevFeed: [Companion app: Changing support for Apple platforms]() Original publisher: [Read original article]() Author: Bruno Pantaleão Published: 2026-07-07T00:00:00Z Content type: release Language: en Sources: [Home Assistant]() Topics: [iOS](), [macOS](), [watchOS](), [web browser](), [App](), [GitHub](), [User experience (UX)]() Tags: [announcements](), [app](), [apple](), [github](), [ios](), [macos](), [performance](), [platforms](), [update](), [ux](), [watchos](), [web-browser]() ### AI overview Home Assistant is changing Apple platform support for its Companion app. Version 2026.7.1 will be the final release supporting iOS 15, watchOS 8, and macOS 11; beginning with version 2026.8.0, the minimum versions will be iOS 16.4, watchOS 9, and macOS 12. The change will enable improved UX, stability, performance, and newer features, while older devices can still use the web frontend. ### Source excerpt We're updating which Apple platforms the Home Assistant Companion app supports, and because transparency is core to how we work, we want to be upfront about what's changing. Starting with version 2026.8.0 of the Companion app, we will no longer support iOS 15, watchOS 8, or macOS 11. The last supported version for these platforms will be 2026.7.1. Here's everything you need to know: Why we're making the change At Home Assistant, we're committed to helping you use your devices for the long haul. We know your hardware is something you rely on every day, which is why we try to keep the Companion app running on older devices for as long as possible. However, supporting older OS versions indefinitely comes at a cost, limiting our ability to adapt to modern technology. From September this year, Apple's developer tools will officially stop supporting watchOS 8 and macOS 11, making it technically difficult for us to keep building for them. With less than 1% of our users currently running these older OS versions, this update allows us to future-proof the Companion app for the vast majority of our community. By focusing our efforts on current operating system versions, we can keep our codebase maintainable for the long term. This shift removes some long-standing constraints, since older OS versions had been limiting our ability to make UX, stability, and performance improvements, including adding features such as Apple Watch complications and more advanced widgets. What this means for you A recap of what's changing: The last Companion app update for these platforms will be version 2026.7.1. After version 2026.7.1, the minimum supported versions for the Companion app will be iOS 16.4, watchOS 9, and macOS 12. Importantly, this doesn't mean your older iOS devices will become unusable. You can still control your home using the Home Assistant frontend in your device's web browser, which remains fully supported and receives regular monthly updates. The last compatible Companion ap ## Monitor watchOS and visionOS apps with Datadog RUM DevFeed: [Monitor watchOS and visionOS apps with Datadog RUM]() Original publisher: [Read original article]() Author: Jessica Manheimer; Maël Lilensten Published: 2026-07-06T00:00:00Z Content type: article Language: en Sources: [Datadog | The Monitor blog]() Topics: [real user monitoring](), [visionOS](), [watchOS](), [error tracking](), [Traces](), [SDKs](), [observability](), [User Experience](), [SwiftUI](), [iOS]() Tags: [apple](), [apple-watch](), [digital-experience-monitoring](), [error-tracking](), [net-11-preview-7](), [observability](), [real-user-monitoring](), [traces](), [user-experience](), [vision]() ### AI overview Datadog RUM extends crash reporting, error tracking, deobfuscated stack traces, and session-level observability to watchOS and visionOS apps. The article explains how teams can investigate failures and understand user interactions without a separate SDK. ### Source excerpt Monitor crashes, errors, and user sessions on watchOS and visionOS by using Datadog RUM with fully deobfuscated stack traces and no separate SDK required. ## Seamless Crash Protection That Symbolicates Native Crashes DevFeed: [Seamless Crash Protection That Symbolicates Native Crashes]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-22T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [App](), [GitHub Issues](), [Cloud](), [Disk image](), [Android](), [iOS](), [Linux](), [macOS](), [Windows](), [tvOS](), [watchOS]() Tags: [android](), [cloud](), [crash](), [data](), [github-issues](), [ios](), [linux](), [macos](), [native](), [protection](), [retry](), [storage](), [watchos](), [win32](), [windows]() ### AI overview The article describes the new com.codename1.crash client, which captures crashes on devices, removes personal data before transmission, stores reports until upload succeeds, retries failed uploads, and uses cloud-side symbolication to file deduplicated reports as GitHub issues. It covers native crash support across multiple platforms and deobfuscation of Android exceptions. ### Source excerpt The new com.codename1.crash client captures crashes on device, scrubs personal data before anything is sent, retries reliably through a storage-first queue, and lets the build cloud symbolicate native crashes and file them as GitHub issues instead of emails. ## 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! ## Native Linux, Apple Watch, A Game Builder And Crash Protection DevFeed: [Native Linux, Apple Watch, A Game Builder And Crash Protection]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-19T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Linux](), [watchOS](), [GitHub Issues](), [Java](), [Kotlin](), [Programming]() Tags: [api](), [apple](), [apple-watch](), [crash](), [desktop](), [gaming](), [github-issues](), [java](), [kotlin](), [linux](), [native](), [watchos]() ### AI overview This weekly Codename One update describes a native Linux desktop port, Apple Watch and Wear OS support, a visual Game Builder with a high-level gaming API, and crash protection that symbolicates native crashes and files them as GitHub issues. It also notes a rebuild of the build cloud and related failed builds. ### Source excerpt This week adds a native Linux desktop port, an Apple Watch and Wear OS port, a visual Game Builder with a high-level gaming API, and seamless crash protection that symbolicates native crashes and files them as GitHub issues. ## Keeping Meeting Apps Alive in the Background on iOS and watchOS DevFeed: [Keeping Meeting Apps Alive in the Background on iOS and watchOS]() Original publisher: [Read original article]() Author: Roland Published: 2026-03-26T14:55:52Z Content type: tutorial Language: en Sources: [RisingStack]() Topics: [iOS](), [watchOS](), [App](), [Artificial Intelligence]() Tags: [ai](), [apps](), [audio](), [case-study](), [code](), [examples](), [ios](), [meetings](), [pipeline](), [pitfalls](), [production](), [watchos]() ### AI overview This tutorial explains how a real-world meeting app handled reliable background recording and post-recording processing on iOS and watchOS. It covers audio interruptions, resuming recordings, AVAudioSession configuration with mixWithOthers, and background transcription and AI processing, including BGContinuedProcessingTask on iOS 26+. ### Source excerpt Building an app that records meetings, generates transcriptions, and produces AI analysation sounds straightforward - until you try to make it reliable while the user goes in and out of your app, takes calls, plays music, or checks notifications. This post walks through how we handled background recording and post-recording processing on iOS and watchOS [...] The post Keeping Meeting Apps Alive in the Background on iOS and watchOS appeared first on RisingStack Engineering. ## Top 10 Launches from Supabase GA Week DevFeed: [Top 10 Launches from Supabase GA Week]() Original publisher: [Read original article]() Author: Paul Copplestone Published: 2024-04-18T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Command-line interface](), [Database](), [Amazon S3](), [API](), [Swift](), [Embeddings](), [iOS](), [macOS](), [tvOS](), [visionOS](), [watchOS]() Tags: [ai](), [cli](), [configuration](), [database](), [development](), [embeddings](), [git](), [ios](), [macos](), [recap](), [s3](), [security](), [storage](), [swift](), [updates]() ### AI overview A recap of Supabase's top launches from GA Week, covering project bootstrapping, public database branching, Postgres index recommendations, official Swift support, security and performance advisors, AI features in Edge Functions, S3-compatible Storage, anonymous sign-ins, and the Oriole Postgres storage extension. ### Source excerpt A recap of the most important launches and updates from the week. ## Supabase Swift DevFeed: [Supabase Swift]() Original publisher: [Read original article]() Author: Guilherme Souza Published: 2024-04-15T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Swift](), [iOS](), [macOS](), [tvOS](), [visionOS](), [watchOS]() Tags: [apple](), [applications](), [auth](), [community](), [contribute](), [deep-dive](), [developers](), [development](), [features](), [guide](), [ios](), [latest-features](), [libraries](), [macos](), [platforms](), [postgres](), [release](), [sso](), [swift](), [watchos]() ### AI overview Supabase Swift libraries are now officially supported by Supabase for applications on Apple platforms, including iOS, macOS, watchOS, tvOS, and visionOS. The release adds features such as WhatsApp OTP, CAPTCHA support, SSO, simplified Storage uploads, anonymous sign-ins, and simplified OAuth. ### Source excerpt Supabase Swift is now officially supported. ## Speeding up Kotlin Multiplatform DevFeed: [Speeding up Kotlin Multiplatform]() Original publisher: [Read original article]() Author: Paul Woitaschek Published: 2022-05-18T09:10:34Z Content type: tutorial Language: en Sources: [Stories by Paul Woitaschek on Medium]() Topics: [Kotlin Multiplatform](), [build times](), [Gradle](), [iOS](), [watchOS](), [Android](), [ide]() Tags: [android](), [android-studio](), [build-times](), [gradle](), [ide](), [ios](), [kotlin](), [kotlin-multiplatform](), [kotlin-native](), [watchos]() ### AI overview This tutorial describes how YAZIO reduces Kotlin Multiplatform development overhead by selectively removing Apple targets during common development. It discusses Gradle module growth, long synchronization and IDE indexing times, and using Gradle Configuration Cache when iOS targets are absent. ### Source excerpt At YAZIO we are heavily investing into Kotlin Multiplatform and use Kotlin to share all business logic between the iOS and the Android App. Naturally this also leads to a lot of code. Since we modularize our software properly to achieve encapsulation and fast incremental build times, it also means a lot of Gradle modules. 70 modules and counting, to be more precise. And for Kotlin Multiplatform, a lot of Gradle modules means a very long Gradle Sync and IDE indexing time. We tried to mitigate some of that by switching to the latest Macbook Pros, which helped quite a bit. But with all the targets we have (1x Android, 3 x iOS, 4 x watchOS), it still takes 6 minutes for Gradle to sync after adding a new Gradle module. This is a very long time, and worse: It encourages developers to not change any build logic at all and leads to them not adding any more modules. Is moving these files into their own module really worth the six-minute wait?Selectively removing targets The idea here is simple: Fewer targets -- less sync time. We rarely need to touch the platform-specific source sets anyway and 99% of the time, we are developing solely in commonMain . This means that while developing, we can just remove the Apple targets. And it turns out: Apple targets have the most effect on sync times. This is due to the Commonizer, large native distributions and a complicated mechanism that allows you to see what's in your classpath from within the IDE. This is pretty simple to implement. First, add a new property to your gradle.properties file: https://medium.com/media/389dc8cfc03487a54eaeb6f2c62a81f9/href Now, in your build.gradle.kts file(s), simply check for that property before creating the native targets. https://medium.com/media/330ad55c6d767fbd4bfcb96822dc4639/href Et voilà -- it's not blazingly fast, but at least we can work with it. Bonus: Configuration Cache 🎉 The other big benefit that we can now make use of is Gradles Configuration Cache. With the iOS targets, Kotlin Multiplat ## Expanding Crashlytics Support for Apple Platforms DevFeed: [Expanding Crashlytics Support for Apple Platforms]() Original publisher: [Read original article]() Author: Sam Edson Published: 2021-06-02T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Crashlytics](), [Firebase](), [iOS](), [macOS](), [SDK](), [watchOS](), [x86]() Tags: [app-clips](), [app-quality](), [apple](), [ci](), [crashlytics](), [firebase](), [ios](), [macos](), [updates](), [watchos](), [xcode]() ### AI overview Firebase describes Crashlytics updates that expand support across Apple platforms, including Apple Silicon Macs, iOS, macOS, App Clips, and watchOS. The release also adds Firebase console device filtering and reports faster startup and dSYM processing in specified scenarios. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Overcast 2019.6 adds per-podcast controls, longer clips, and data-driven recommendations DevFeed: [Overcast 2019.6 adds per-podcast controls, longer clips, and data-driven recommendations]() Original publisher: [Read original article]() Author: Marco Arment Published: 2019-07-21T20:14:44Z Content type: release Language: en Sources: [Marco.org]() Topics: [App](), [recommendations](), [iOS](), [data](), [macOS](), [watchOS]() Tags: [app](), [data](), [ios](), [macos](), [recommendations](), [update](), [watchos]() ### AI overview Overcast 2019.6 adds per-podcast download, streaming, and auto-delete controls, increases clip-sharing to 90 seconds, and replaces Twitter recommendations with an in-app data-driven recommendation engine. ### Source excerpt Today's Overcast update (2019.6) brings some great new features. But first, I need to set low expectations for iOS 13, watchOS 6, and macOS Catalina updates this fall. Halfway through the summer, I've made much less progress than expected, having been overwhelmed by the required OS changes, my own technical and design debts, and unusually rough betas. Rather than shipping a big iOS update, a standalone Watch app, and a Mac app on day one, these will probably come incrementally over the next year. Fortunately, I haven't stopped improving the app in the meantime. Per-podcast customization, longer clips You can now set download-vs.-stream and auto-delete behavior per podcast, one of the most frequently requested features over the last few years. (Sorry it took so long -- it required a lot of server-side work for uninteresting reasons.) I've also raised the clip-sharing length limit to 90 seconds. When I debuted this feature, I had to guess how it would be used and received, and 60 seconds seemed like a good limit. In practice, that's sometimes a bit too short to capture a complete thought. 90 seconds should be better -- most clips won't need to be that long, but it'll be nice to have the headroom when you need it. "Suggestions for You" replacing Twitter Overcast has had a Twitter-powered social-recommendations feature since version 1.0 in 2014, which made sense at the time: I didn't have any popularity data to generate recommendations from, and social networks were nicer places to be than they are today. But after five years, only 10% of active users have connected a Twitter account in Overcast, and only 0.2% of new podcast subscriptions have actually been added via Twitter recommendations. Not only was the feature not providing much value to the 10% of people who enabled it, but the other 90% of Overcast's customers haven't been getting personalized recommendations at all. In the meantime, I've accumulated five years of popularity data, so I tried writing my own recomme ## iOS Meetup DevFeed: [iOS Meetup]() Original publisher: [Read original article]() Author: https://twitter.com/timonus (Tim Johnsen) Published: 2015-09-09T00:00:00Z Content type: article Language: en Sources: [Flipboard]() Topics: [watchOS](), [iOS](), [App]() Tags: [apple](), [apple-watch](), [apps](), [community](), [developers](), [event](), [hiring](), [ios](), [video](), [watchos]() ### AI overview Flipboard hosted a Palo Alto iOS Developers meetup focused on developing apps for watchOS 2. The event included a talk by Ben Morrow, a presentation about Flipboard's WatchKit app, and a complete video recording. ### Source excerpt Flipboard was honored to host a meetup of the Palo Alto iOS Developers group about developing apps for watchOS 2 at our office in Palo Alto last week. Ben Morrow, writer of the Happy Watch blog and host of several Apple Watch hackathons, gave a talk deep diving into various aspects of watchOS 2. We also gave a short talk sharing a bit of the story about how we built our WatchKit app and what we've got in store for watchOS 2. A photo posted by Flipboard (@flipboard) on Sep 3, 2015 at 11:29am PDT We'd like to thank Mike Suprovici and the community for giving us the oppourtunity to host this event. Here's a complete video of the meetup P.S. We're hiring!