proomt

Search

Search posts, papers, and topics

All posts

CodeName OneShai Almog5 min readintermediate

App Intents: One Java Declaration for Siri, Spotlight, and Shortcuts

Read on codenameone.com

Summary

Codename One adds @AppIntent annotations that let a static Java method be exposed as a Siri, Spotlight, or Android shortcut. The build‑time processor generates native declarations, a reflection‑free dispatch table, and validates the intent metadata. Handlers can be headless, accept typed parameters, return results, and be invoked internally via Intents.invoke(). Entities enable system‑driven disa…

  • Static @AppIntent methods are compiled into native intent declarations for iOS (App Intents, Spotlight) and Android launcher shortcuts; no runtime reflection is used.
  • The Maven bytecode processor validates phrases, entities, and routes at build time, preventing silent failures.
  • Headless handlers run without a UI thread, can use storage/networking, but must respect a platform‑enforced timeout and cooperative cancellation.
  • Entity classes expose @EntityId, @EntityTitle, and @EntityQuery methods so the OS can search and let users pick an object before the handler runs.

Cross‑platform mobile apps often need to expose functionality to OS‑level services (Siri, Spotlight, Android shortcuts). Codename One’s annotation‑driven approach eliminates duplicated native code, ensures compile‑time safety, and lets the same Java logic serve as a voice command, search result, or…

6/10
api designarchitectureandroidiosjava

Related reading

  1. VoIP, VPN, and the Build System Behind Them

    Codename One’s new builder pipeline can automatically generate the native plumbing required for VoIP call integration, managed VPN profiles, and packet‑tunnel extensions on iOS and Android. By inspecting which Java packages an app imports, the builder adds the necessary frameworks, entitlements, services, and even a separate signed Network Extension for iOS, letting developers keep their signalin…

    CodeName Onecodenameone.com10 min

  2. App Hardening: One Obfuscation Pipeline Across Every Port

    Codename One adds a cloud‑side hardening step that runs on the merged JAR before it is split into Android, iOS, JavaScript, and desktop binaries. It can rename symbols, encrypt string literals, and insert opaque‑predicate control‑flow guards at configurable levels (off → standard → aggressive → paranoid). The transforms are selective per platform to avoid breaking optimizers, and a mapping is kep…

    CodeName Onecodenameone.com6 min

  4. Android 17 Without the Last-Minute Scramble

    CodeName One prepared for Android 17 (API 37) by addressing platform changes proactively, including fixing version number parsing and implementing the new system-rendered location button. They also added robust PEM key parsing and explicit task removal to simplify common security operations for app developers.

    CodeName Onecodenameone.com8 min

  5. Tapjacking Protection: Rejecting Android Touches Behind an Overlay

    Codename One adds tapjacking protection to its Android runtime. It detects fully or partially obscured MotionEvents, offers four policies (OFF, REPORT, BLOCK, STRICT), can block the entire gesture, and on Android 12+ can request the system hide overlay windows. The API is exposed via `DeviceIntegrity.setTapjackingProtection` and a listener for state changes. iOS has no overlay threat, so the feat…

    CodeName Onecodenameone.com3 min

  6. Put App Documents in the System File Browser

    Codename One adds a read‑only DocumentProvider API that lets apps publish a virtual file tree to iOS Files and Android’s storage picker. The tree is defined with `DocumentNode` objects, can include remote‑only entries, and is shared via an App Group container. The iOS extension runs in a separate process, so the model is serialized and read independently; Android uses the same model inside the ap…

    CodeName Onecodenameone.com4 min