# tvOS tvOS is an Apple platform for building apps and games, with development resources, tools, frameworks, and APIs. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Build Setup: Targets, Source Sets and buildSrc for tvOS in a Compose Multiplatform Fork DevFeed: [Build Setup: Targets, Source Sets and buildSrc for tvOS in a Compose Multiplatform Fork]() Original publisher: [Read original article]() Author: Sajid Ali Published: 2026-09-14T04:24:43Z Content type: tutorial Language: en Sources: [ProAndroidDev - Medium]() Topics: [compose-multiplatform](), [tvOS](), [Kotlin Multiplatform](), [Gradle]() Tags: [apple](), [build](), [compiler](), [compose-multiplatform](), [gradle](), [gradle-plugin](), [ios](), [jetbrains](), [multiplatform](), [source]() ### AI overview This tutorial explains the build setup for adding tvOS support to a Compose Multiplatform fork. It covers Kotlin Multiplatform targets, source-set organization shared between iOS and tvOS, and the build-layer work used to identify missing modules and dependencies. ### Source excerpt Compose Multiplatform on tvOS This series: Compose Multiplatform on tvOS My Journey Making Compose Multiplatform Work on tvOS, and What I Learned Build Setup: Targets, Source Sets and buildSrc for tvOS in a Compose Multiplatform Fork (this post) Rendering (coming soon) Siri Remote input (coming soon) Siri Remote trackpad (coming soon) Screen density and text input (coming soon) Porting tv-material (coming soon) The Gradle plugin and third-party libraries (coming soon) Maintaining the fork (coming soon) Building a real app on it (coming soon) Part 1 was why this fork exists. This one is the build layer, and it comes before any Compose code, because in Kotlin Multiplatform a target is not a flag you flip at the end. It decides which source sets compile, which dependencies resolve, which klibs get published, which linker flags get passed. Until the build knows about tvosArm64, nothing tells you what is missing. So the first commits were build files. Once the targets were on, the compiler listed what was missing, module by module, and I worked through that list. Source set layout on the tvos branch I started on a branch called tvos, based on upstream. Back then JetBrains called iOS "uikit" in this repository and the source set was uikitMain. Because tvOS is also UIKit underneath, it made sense to have a common source parent for both iOS and tvOS. But iOS was already being called uikit, so I chose uiKitCommonMain as the source set name and moved all the UIKit files there, keeping only the iOS specific files in uikitMain and putting the tvOS specific files in a new source set, tvosMain. The problem with this approach was how to keep up with upstream. I tried a symlink to the uikit source set, and then overriding the tvOS files in a separate target. The override worked but complicated the process. At that time my goal was to make it runnable on tvOS however possible, so we would have a proof of concept. So I did a lot of hacks in the tvos branch to make it runnable, and af ## 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! ## 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. ## Apple TV And Android TV: One Codebase, And CSS @media For The Living Room DevFeed: [Apple TV And Android TV: One Codebase, And CSS @media For The Living Room]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [tvOS](), [Android](), [CSS](), [Android APK]() Tags: [android](), [apk](), [apple](), [css](), [ui]() ### AI overview The article describes Codename One support for Apple TV and Android TV from a shared codebase. It covers runtime TV detection, CSS @media styling, Android TV APK generation, and a separate tvOS target built from the same project. ### Source excerpt TV becomes a real form factor: CN.isTV(), runtime device-tv/device-watch CSS @media, an Android TV APK via android.tv, and a tvOS Metal target. ## 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. ## Vibe coding with the incident.io API DevFeed: [Vibe coding with the incident.io API]() Original publisher: [Read original article]() Author: Tom Wentworth Published: 2025-08-05T16:42:14Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [Vibe coding](), [Claude Code](), [API](), [incident](), [tvOS]() Tags: [api](), [apple](), [claude-code](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [outage](), [post-mortem](), [real-time](), [slack-incident](), [vibe-coding](), [xcode]() ### AI overview The article describes how a marketer used Claude Code and vibe coding to build a working Apple TV incident command center dashboard powered by the incident.io API. The app presents incident data for conference rooms or offices and supports themed visual displays. ### Source excerpt This post explores how a basic idea turned into a working Apple TV dashboard powered by the incident.io API. Using Claude Code and a "vibe coding" approach, the app was built in a few hours, complete with real-time incident data, dual themes (including a Wargames-inspired view), and no Swift experience :) ## 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. ## Multiplatform Settings 1.0.0 DevFeed: [Multiplatform Settings 1.0.0]() Original publisher: [Read original article]() Author: Russell Wolf Published: 2023-01-15T03:12:17Z Content type: release Language: en Sources: [DEV Community 👩💻👨💻: Russell Wolf]() Topics: [kotlin-multiplatform-libraries](), [Kotlin Multiplatform](), [Kotlin](), [Library](), [Android](), [iOS](), [macOS](), [tvOS](), [watchOS](), [Windows](), [Web]() Tags: [android](), [coding](), [community](), [development](), [engineering](), [inclusive](), [ios](), [kotlin](), [kotlin-multiplatform](), [kotlin-multiplatform-libraries](), [kotlinmultiplatform](), [library](), [macos](), [release](), [software](), [watchos](), [web](), [windows]() ### AI overview The author announces version 1.0.0 of Multiplatform Settings, a Kotlin Multiplatform library for persisting simple, unstructured key-value data. The release commits to maintaining non-experimental APIs until a possible 2.0 release and compares the library's platform-API interoperation with Google's preview multiplatform DataStore library. ### Source excerpt Today, I've released version 1.0.0 of Multiplatform Settings. That means I'm committed to maintaining the current API surface of everything not marked as experimental until there's a 2.0 release (which I don't currently have plans for). If you need to save simple, unstructured key-value data in your multiplatform apps, I hope you'll consider using it. A lot of you already are! russhwolf / multiplatform-settings A Kotlin Multiplatform library for saving simple key-value data Multiplatform Settings This is a Kotlin library for Multiplatform apps, so that common code can persist key-value data. A Korean translation of this readme is available separately, maintained by @wooram-yang Table of contents Usage Implementation Summary Creating a Settings instance Platform constructors Factories No-arg module Settings API Listeners Testing Other platforms Experimental API Experimental Implementations Serialization module Coroutine APIs DataStore Make-Observable module Adding to your project Building License Usage The Settings interface has implementations on the Android, iOS, macOS, watchOS, tvOS, JS, WasmJS, JVM, and Windows platforms. Implementation Summary The following table shows the names of implementing classes and what platforms they're available on. Class Backing API Platforms KeychainSettings2 Apple Keychain iOS, macOS, watchOS, tvOS NSUserDefaultsSettings1 User Defaults iOS, macOS, watchOS, tvOS PreferencesSettings1 java.util.prefs.Preferences JVM PropertiesSettings java.util.Properties JVM SharedPreferencesSettings1 android.content.SharedPreferences Android StorageSettings Web Storage (localStorage) JS, WasmJS RegistrySettings2 Windows Registry MingwX64 DataStoreSettings3 androidx.datastore.core.DataStore Android, ... View on GitHub Some History Multiplatform Settings was one of the first Kotlin Multiplatform libraries ever released, with the first version published on May 28, 2018. I called that first version 0.1-alpha, though I would later drop the alpha from the ve ## An Approach for Migrating From Objective-C to Swift DevFeed: [An Approach for Migrating From Objective-C to Swift]() Original publisher: [Read original article]() Author: Steve Barnegren Published: 2022-01-13T00:00:00Z Content type: tutorial Language: en Sources: [Steve Barnegren]() Topics: [Objective-C](), [Swift](), [interoperability](), [iOS](), [tvOS](), [generics](), [Code]() Tags: [apple](), [enums](), [generics](), [interoperability](), [ios](), [objective-c](), [optional](), [swift](), [types](), [with]() ### AI overview This article shares lessons from transitioning a large iOS and tvOS application from Objective-C to Swift. It explains why simply adding new Swift code produced limited progress and caused Swift code to be constrained by Objective-C interoperability. ### Source excerpt It feels like Swift is pretty ubiquitous across the Apple ecosystem now, but there's a lot of Objective-C out there. The larger and older the app, the more likely that there's still a bunch of Objective-C powering various bits behind the scenes. ## Announcing the Firebase Crashlytics SDK Beta! DevFeed: [Announcing the Firebase Crashlytics SDK Beta!]() Original publisher: [Read original article]() Author: Shobhit Chugh Published: 2020-02-18T00:00:00Z Content type: news Language: en Sources: [Firebase Blog]() Topics: [Crashlytics](), [Firebase](), [SDKs](), [Google Analytics](), [iOS](), [macOS](), [tvOS](), [GitHub]() Tags: [analytics](), [android](), [app-quality](), [apple](), [crash-reporting](), [crashlytics](), [firebase](), [github](), [guide](), [ios](), [latest-release](), [launch](), [legacy](), [macos](), [news](), [reporting](), [sdk](), [sdks](), [updates]() ### AI overview Firebase announces the Firebase Crashlytics SDK in beta. The SDK removes Fabric dependencies, aligns package names, API design, and initialization with other Firebase SDKs, supports Apple platforms including Mac Catalyst, and is open source. Integration with Google Analytics provides crash-related insights and reporting features. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Home streaming my games in 4K DevFeed: [Home streaming my games in 4K]() Original publisher: [Read original article]() Published: 2019-12-23T00:00:00Z Content type: article Language: en Sources: [Robin Ward]() Topics: [Streaming](), [pc](), [GPU](), [cpu](), [tvOS](), [Xbox](), [App](), [NVMe]() Tags: [apple-tv](), [controllers](), [devices](), [fps](), [gpu](), [pc](), [ssd](), [streaming](), [xbox]() ### AI overview The author describes streaming PC games to home televisions instead of building a second gaming PC. The article covers the Steam Link setup on an Apple TV 4K, including Xbox One controller pairing issues, and begins evaluating 4K performance. ### Source excerpt I have two 4K TVs at home, one in the bedroom and one in my living room. Both have consoles attached. One has a PS4 Pro and one has a Nintendo Switch and both are great. However, I also have a gaming PC in my office, which is quite powerful compared to any home console Mine is equipped with a RTX 2080 TI GPU, and a 9900K processor, so it can play pretty much any new game at 4K with a solid 60 fps on high settings.