Platform and feature matrix

CrossFly is a multi-module Gradle project: the UI and logic live in core (neutral), and each launcher (lwjgl3, android, ios, web) only handles the OS bootstrap. The same Java code runs on all four targets.

Platform detection

if (Device.platform.isDesktop()) { ... }   // WINDOWS/LINUX/MACOS
if (Device.platform.isMobile()) { ... }     // ANDROID/IPHONE/IPAD
if (Device.platform.isIOS()) { ... }

Platform: JAVA · WINDOWS · LINUX · IPHONE · ANDROID · IPAD · MACOS.

Support matrix by feature

Feature	🖥️ Desktop	🤖 Android	🍎 iOS	🌐 Web
Render UI	✅	✅	✅	✅
Camera / barcode	⚠️¹	✅	✅	❌
GPS / location	❌	✅	✅	❌
Bluetooth BLE	⚠️	✅	✅	❌
Biometrics	⚠️	✅	✅	❌
Native maps	✅	✅	✅	❌
`WebContainer`	✅	✅	✅²	❌³
Vibration	❌	✅	✅	❌
Voice (TTS/STT)	⚠️	✅	✅	❌
File persistence	✅	✅	✅	❌⁴
HTTP	✅	✅	✅	⚠️⁵

✅ supported · ⚠️ limited/varies · ❌ stub (does nothing useful)

Camera on desktop varies by OS (e.g., Mac ARM may return null).
WKWebView with restricted evaluateJavaScript (iOS).
createWebView() returns null on the web (Web).
Device.homeFolder is null on the web.
HTTP on the web has restrictions (CORS, no sockets) — Utils.getRemoteFile returns null.

Golden rule for portability: every device feature may not exist on a given target. Check before using it (Device.platform, createWebView() != null, null return) — see Native integration.

Which page to read

Target	Page
🖥️ iterate fast	Desktop (LWJGL3)
🤖 Android phone	Android
🍎 iPhone/iPad	iOS (RoboVM)
🌐 browser	Web (TeaVM)
wire code to the OS	Native integration
package and publish	Build and distribution