# native Published articles for native. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## What's New in Apollo Client 4.3 DevFeed: [What's New in Apollo Client 4.3]() Original publisher: [Read original article]() Author: Jerel Miller Published: 2026-09-15T12:01:05Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [apollo-client](), [GraphQL](), [TypeScript](), [Cache](), [Code generation]() Tags: [apollo-client](), [cache](), [codegen](), [graphql](), [native](), [typescript]() ### AI overview Apollo Client 4.3 adds native custom scalar support, type-safe cache access, and improved TypeScript handling for incremental GraphQL data. The release also updates generated types and data-state narrowing for deferred fields. ### Source excerpt Apollo Client 4.3 is here: native custom scalar support, type-safe cache access, and more consistent @defer and @stream behavior. See what's new and upgrade today. ## Native Drag and Drop Meets Cross-Device Continuity DevFeed: [Native Drag and Drop Meets Cross-Device Continuity]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-15T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Java](), [Persistence](), [Framework](), [payload](), [LineageOS](), [Processes](), [browser]() Tags: [android](), [apis](), [browser](), [java](), [native](), [payload](), [persistence](), [process](), [screen](), [state]() ### AI overview Codename One adds cross-device continuity and native drag-and-drop through shared Java APIs. The article explains how to save reconstructible application state, restore it after account verification, and transfer it between devices and applications. ### Source excerpt Drag files into another application and pick up a task on another device. Codename One adds native drag and drop and cross-device continuity through shared Java APIs. ## Pick One Contact Without Asking for the Address Book DevFeed: [Pick One Contact Without Asking for the Address Book]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-09T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [API](), [Android](), [iOS](), [Code](), [App]() Tags: [android](), [api](), [code](), [contactpicker](), [ios](), [native](), [permission](), [privacy]() ### AI overview ContactPicker lets Codename One applications request selected contact fields through a system-owned picker without broad address-book permission. The article describes platform differences, limited fallback behavior, manual-entry handling, and more precise permission detection. ### Source excerpt ContactPicker lets a Codename One application request selected contact fields through the system picker without broad address-book permission. ## A Dialog Can Now Be a Native Desktop Window DevFeed: [A Dialog Can Now Be a Native Desktop Window]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-05T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [dialog](), [Accessibility](), [Operating system](), [macOS]() Tags: [accessibility](), [bug](), [can](), [code](), [component](), [desktop](), [dialog](), [keyboard](), [macos](), [native](), [release]() ### AI overview Codename One adds an option for dialogs to open as native modal desktop windows while retaining lightweight in-window dialogs. The release also fixes top-level window ownership and updates focus, input routing, repainting, popup behavior, and accessibility handling across separate windows. ### Source excerpt Codename One dialogs can stay inside a secondary window or become native modal windows, while sheets, popups, overlays, tooltips, HTML, and accessibility now resolve the correct top level. ## VoIP, VPN, and the Build System Behind Them DevFeed: [VoIP, VPN, and the Build System Behind Them]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-04T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Virtual Private Network](), [cross-platform](), [API](), [iOS](), [Android](), [Java](), [Framework](), [Extension]() Tags: [android](), [apis](), [build](), [build-system](), [extension](), [integration](), [java](), [native](), [packages](), [platform](), [signing](), [vpn]() ### AI overview Codename One adds native call-management and VPN APIs for iOS and Android. Its builders generate the required platform services, frameworks, permissions, delegates, and separately signed extension targets based on the Java packages an application uses. ### Source excerpt Codename One adds native call management and VPN APIs, while its builders generate the platform services, frameworks, permissions, and extension plumbing only when an application uses them. ## Knights of Fiona Review: A VR JRPG That Struggles to Satisfy Different Players DevFeed: [Knights of Fiona Review: A VR JRPG That Struggles to Satisfy Different Players]() Original publisher: [Read original article]() Author: Mike Johnson Published: 2026-09-03T17:00:48Z Content type: opinion Language: en Sources: [UploadVR]() Topics: [Virtual reality](), [immersive web]() Tags: [native](), [review](), [vr-gaming]() ### AI overview This review examines Knights of Fiona, a co-op Japanese role-playing game for VR. It finds that the game brings familiar JRPG elements to virtual reality but struggles to satisfy the different player types it targets, with short combat missions, limited town exploration, and uneven environments contrasted with strong music. ### Source excerpt Knights of Fiona is the best example yet of a native VR JRPG, but it tries to be a jack of all trades for two different audiences, ultimately not fully satisfying either. ## One App, More Than One Native Window DevFeed: [One App, More Than One Native Window]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-28T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [App](), [Windows](), [Linux](), [Java]() Tags: [app](), [capture](), [desktop](), [linux](), [monitor](), [native](), [screen](), [state](), [windows]() ### AI overview Codename One now supports multiple native desktop windows, each with its own component tree, focus owner, animation list, repaint region, native peers, and text editing. The main Form remains the application's primary surface, preserving existing mobile and single-window behavior. ### Source excerpt Codename One now supports multiple native desktop windows with independent component trees, paint surfaces, focus, modality, monitor geometry, and input routing while Form remains the application's main surface. ## App Intents: One Java Declaration for Siri, Spotlight, and Shortcuts DevFeed: [App Intents: One Java Declaration for Siri, Spotlight, and Shortcuts]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-27T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Java](), [App](), [Android](), [iOS](), [Maven]() Tags: [android](), [app](), [build](), [bytecode](), [ios](), [java](), [maven-plugin](), [native](), [shortcuts](), [spotlight]() ### AI overview Codename One App Intents use Java annotations to generate reflection-free handlers for Siri, Spotlight, Shortcuts, Android launcher shortcuts, and internal application commands. The article explains build-time validation, entity parameters, routing, and concurrent handler execution. ### Source excerpt Codename One App Intents generate reflection-free handlers for Siri, Spotlight, Shortcuts, Android launcher shortcuts, and an application command layer from Java annotations. ## Native Async/Coroutine Reads in RocksDB DevFeed: [Native Async/Coroutine Reads in RocksDB]() Original publisher: [Read original article]() Author: Josh Kang Published: 2026-08-24T00:00:00Z Content type: release Language: en Sources: [RocksDB]() Topics: [rocksdb](), [Coroutines](), [C++](), [IO](), [API]() Tags: [async](), [asynchronous](), [blog](), [c-plus-plus](), [coroutine](), [io](), [native](), [rocksdb](), [thread]() ### AI overview RocksDB introduces experimental asynchronous Get and MultiGet APIs backed by native C++ coroutines. The APIs can suspend storage-bound reads, allowing a small executor to run other ready tasks and maintain more storage queue depth without one blocked application thread per read. The feature targets throughput for I/O-bound point lookups rather than reducing individual device-read latency. ### Source excerpt A point lookup that misses RocksDB's block cache can spend most of its time waiting for storage. The traditional way to keep more reads in flight is to add threads. That works, but each outstanding read parks a thread, carries a stack, and adds context-switching overhead. RocksDB now has experimental asynchronous Get and MultiGet APIs backed by native C++ coroutines. When a read reaches storage, RocksDB can suspend the request, let its read-executor worker run another ready task, and resume the request when the filesystem reports completion. A small executor can therefore maintain more storage queue depth without requiring one blocked application thread per read. These APIs are available in RocksDB 11.10.0. This is primarily a throughput feature for I/O-bound point lookups. It does not make an individual device read faster. Its benefit comes from keeping the device busy and using CPU threads for runnable work. The API surface RocksDB exposes the new read path through two public interfaces: DB::GetAsync and DB::MultiGetAsync return immediately on the native path and report completion through AsyncCallback::OnComplete. CoroDB::CoGet and CoroDB::CoMultiGet return lazy folly::coro::Task objects. CoGet produces a Status; CoMultiGet fills the same per-key values and statuses as synchronous MultiGet. The callback APIs suit applications that do not expose Folly tasks at their boundaries. The CoroDB APIs let coroutine-based callers await RocksDB directly, avoiding an application-side callback-to-Baton adapter and its extra completion handoff. Native execution requires RocksDB to be built with Folly and USE_COROUTINES=1. Neither interface requires ReadOptions::async_io. That flag continues to control the older internal async-I/O optimizations for synchronous MultiGet and iterators. The task APIs are lazy: no read begins until a task is awaited or started. Both interfaces take pointer and reference parameters, so keep the DB, column-family handles, ReadOptions, keys and their ## How to store and refresh session tokens correctly with the WorkOS iOS SDK DevFeed: [How to store and refresh session tokens correctly with the WorkOS iOS SDK]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-18T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [iOS](), [SDK](), [Authentication](), [JSON Web Tokens]() Tags: [apple](), [auth](), [authentication](), [concurrent](), [guide](), [how-to](), [ios](), [jwt](), [native](), [plist](), [rotation](), [sdk](), [storage](), [tokens](), [tutorial]() ### AI overview This tutorial explains how to store and refresh session tokens with the WorkOS iOS SDK. It recommends storing access and refresh tokens in the Keychain, persisting each rotated refresh token, and distinguishing terminal refresh failures from transient network or concurrency-related failures. ### Source excerpt A practical guide to Keychain storage, refresh token rotation, and terminal vs. transient failures on iOS ## App Hardening: One Obfuscation Pipeline Across Every Port DevFeed: [App Hardening: One Obfuscation Pipeline Across Every Port]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-15T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [obfuscation](), [cross-platform](), [Encryption](), [Security](), [Reverse Engineering](), [App]() Tags: [android](), [app](), [cross-platform](), [encryption](), [hardening](), [ios](), [javascript](), [native](), [obfuscation](), [platform](), [r8](), [reverse-engineering](), [security]() ### AI overview Codename One App Hardening applies one pre-build protection pipeline to a merged cross-platform application before it is split into Android, iOS, JavaScript, Windows, Linux, and desktop builds. It supports renaming, eligible string encryption, selected control-flow transformations, verification, and crash-report retracing, while acknowledging that reverse engineering cannot be made impossible. ### Source excerpt Codename One App Hardening applies class and member renaming, string encryption, and platform-safe control-flow transforms before one application becomes Android, iOS, JavaScript, or native desktop output. ## Scanning bus stop codes with ML Kit and Vision in the GalwayBus Compose Multiplatform app DevFeed: [Scanning bus stop codes with ML Kit and Vision in the GalwayBus Compose Multiplatform app]() Original publisher: [Read original article]() Published: 2026-08-06T23:00:00Z Content type: tutorial Language: en Sources: [John O'Reilly]() Topics: [compose-multiplatform](), [ML Kit](), [Android](), [cameraX](), [iOS](), [Code](), [ui]() Tags: [android](), [apple](), [camera](), [camerax](), [code](), [compose-multiplatform](), [ios](), [ml-kit](), [multiplatform](), [native](), [ocr](), [on-device](), [platform](), [recognition](), [ui]() ### AI overview This tutorial explains how the GalwayBus app scans six-digit bus stop codes using on-device ML Kit on Android and Apple's Vision framework on iOS. Camera preview, matching logic, and UI are shared through Compose Multiplatform, while platform-specific implementations handle camera access and OCR. Recognized six-digit runs are matched exactly to stops, and overlapping recognition requests are avoided by dropping newer frames. ### Source excerpt Every bus stop in Galway has a plate with a 6-digit stop code printed on it. We recently added a "Scan" tab to the GalwayBus app that lets you point the camera at that plate and jump straight to the stop's departures. The text recognition runs entirely on device (ML Kit on Android, Apple's Vision framework on iOS), with the camera preview, matching logic and UI all living in the shared Compose Multiplatform code. ## Pure Codename One Text Editing Without Native Overlays DevFeed: [Pure Codename One Text Editing Without Native Overlays]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-27T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [ui](), [Code]() Tags: [component](), [formatting](), [gif](), [image](), [jpeg](), [native](), [port]() ### AI overview A new semantic port contract lets Codename One handle text painting, selection, rich editing, clipboard formats, and bidirectional layout while platform ports provide keyboard and input-method events. The opt-in path supports text composition, undo and redo, selection geometry, and multi-format clipboard content without a visible native field. ### Source excerpt A semantic port contract lets Codename One own text painting, selection, rich editing, clipboard formats, and bidirectional layout while the platform supplies keyboard and IME operations. ## 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. ## ESPHome 2026.7.0: Native toolchains by default DevFeed: [ESPHome 2026.7.0: Native toolchains by default]() Original publisher: [Read original article]() Author: Jesse Hills Published: 2026-07-15T00:00:00Z Content type: release Language: en Sources: [ESPHome - Smart Home Made Simple - Blog]() Topics: [esphome](), [toolchains](), [ESP32](), [Modbus](), [Security](), [ESP-IDF](), [SDK]() Tags: [2026](), [esp-idf](), [esp32](), [esphome](), [modbus](), [native](), [release](), [releases](), [security](), [toolchains]() ### AI overview ESPHome 2026.7.0 makes native ESP32 and nRF52 toolchains the default, adds security infrastructure including NVS encryption and OTA downgrade protection, and introduces a transport-agnostic provisioning component. The release also overhauls Modbus and includes performance, memory, LVGL, Ethernet, ESP-NOW, Zigbee, and component updates. ### Source excerpt ESPHome 2026.7.0 makes native toolchains the default on ESP32 and nRF52, adds EN18031 security groundwork, and overhauls Modbus. ## Codename One Adds a Pure-Vector MapView and Pluggable Native Map Providers DevFeed: [Codename One Adds a Pure-Vector MapView and Pluggable Native Map Providers]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-27T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Framework](), [Google Maps](), [Code]() Tags: [api](), [code](), [framework](), [google-maps](), [maps](), [native](), [vector]() ### AI overview The article describes a Codename One mapping update that adds a pure-vector MapView and a NativeMap using platform map providers behind a shared API. The vector engine uses Mapbox Vector Tiles, existing drawing pipelines, pluggable tile sources, and MapLibre-subset JSON styling. ### Source excerpt A pure-vector MapView rendered through Graphics plus a NativeMap whose provider is wired by a build hint, not code. ## Funding Open Source Without The Bait And Switch: Analytics, Native Maps, TV And More DevFeed: [Funding Open Source Without The Bait And Switch: Analytics, Native Maps, TV And More]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-26T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Open Source](), [GNU General Public License](), [API](), [Android](), [iOS](), [Code]() Tags: [analytics](), [android](), [api](), [ios](), [maps](), [native](), [open-source](), [source]() ### AI overview A Codename One release post describes new analytics, native and vector maps, Apple TV and Android TV support, rich text and code editors, and device integrity APIs. It also explains the project's funding model, including GPL licensing with the Classpath Exception and paid build-cloud capacity. ### Source excerpt A privacy-first analytics API, vector and native maps, Apple TV and Android TV, rich text and code editors, and device integrity APIs, plus how we fund the project without the usual open source bait and switch. ## 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! ## Java To Native Linux App: One 5MB Binary, x64 And Arm DevFeed: [Java To Native Linux App: One 5MB Binary, x64 And Arm]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-20T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Linux](), [Java](), [App](), [Arm](), [OpenGL]() Tags: [arm](), [glibc](), [java](), [linux](), [native](), [port]() ### AI overview This article explains Codename One's native Linux desktop port. ParparVM translates Java and Kotlin bytecode to C, which is compiled into a self-contained ELF binary without requiring a JVM on the target machine. It describes the GTK-based rendering stack, native integrations, packaging approach, dependencies, and support for x64, arm64, and musl-based Alpine Linux. ### Source excerpt The new native Linux port compiles your Java to a single self-contained ELF through ParparVM and GTK3, with no JVM on the target machine. It runs on an ancient universal glibc, supports musl for Alpine, and ships for both x64 and arm64. ## 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. ## Codename One Adds Cross-Platform Printing and Apple Wallet Issuer Provisioning DevFeed: [Codename One Adds Cross-Platform Printing and Apple Wallet Issuer Provisioning]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-16T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [API](), [cross-platform](), [iOS](), [Extension]() Tags: [api](), [cross-platform](), [extensions](), [ios](), [native](), [release](), [xcode]() ### AI overview This release adds a cross-platform printing API that sends documents to the native print system and reports whether the handoff was completed, cancelled, or failed. It also adds iOS build hints that generate Apple Wallet issuer-provisioning extensions, while card data is provided through the app and encrypted pass payloads are produced by the issuer backend. ### Source excerpt A new cross-platform printing API hands PDFs and images to the native print dialog on every port, and iOS builds can now generate Apple Wallet issuer-provisioning extensions from build hints with no native code. ## Codename One Compiles Java and Kotlin Apps to Native Windows Executables Without a JVM DevFeed: [Codename One Compiles Java and Kotlin Apps to Native Windows Executables Without a JVM]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-15T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Java](), [Windows](), [win32](), [Arm]() Tags: [binaries](), [compilation](), [desktop](), [java](), [native](), [win32](), [windows]() ### AI overview Codename One's new Windows port uses the ParparVM pipeline to compile Java and Kotlin bytecode into standalone native Win32 executables without bundling or installing a JVM. The build targets both x64 and arm64 Windows systems. ### Source excerpt The new native Windows port compiles your Java to a standalone Win32 executable through ParparVM, Direct2D, and DirectWrite. No JVM, no bundled runtime, a 5MB hello world, and both x64 and arm64 from one build. ## The Future of KMP's iOS Interop - Daniel Bertoldi DevFeed: [The Future of KMP's iOS Interop - Daniel Bertoldi]() Original publisher: [Read original article]() Published: 2026-06-12T00:00:00Z Content type: comparison Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [Swift](), [Objective-C](), [Compiler](), [multiplatform]() Tags: [compare](), [experimental](), [interop](), [ios](), [kmp](), [kotlin](), [kotlin-multiplatform](), [native](), [objective-c](), [production](), [skie](), [swift](), [swift-export]() ### AI overview This comparison examines Kotlin Multiplatform iOS interoperability through Kotlin's experimental Swift Export and the Objective-C bridge enhanced by SKIE. It compares their generated output, capabilities, limitations, and tradeoffs. ### Source excerpt Kotlin's new Swift Export feature promises to eliminate the Objective-C middleman and generate native Swift APIs directly from your KMP code. But with SKIE already solving many of the same pain points in production today, which approach should your team bet on? We break down the capabilities, limitations, and tradeoffs of both. [Next page]()