Android-to-iOS Importer Compatibility with MapLibre, Room, and WorkManager

[fckdsko-apps]

Hi! I'm looking into using the new Android-to-iOS importer for an existing Java Android app for geological research, offline mapping, and GPS tracking.

The app uses these main dependencies:

• MapLibre Android SDK 13.4.1 — offline PMTiles, GeoJSON overlays, and interactive maps
• AndroidX Room 2.8.4 — local databases
• AndroidX WorkManager 2.11.2 — background data downloads and updates
• Android SQLite APIs — geological databases
• LocationManager and foreground services — GPS navigation and background track recording
• SensorManager — compass functionality
• Android Keystore — secure license storage

The UI is built programmatically in Java rather than XML layouts.

I'm curious how much of this the importer could realistically handle, particularly MapLibre. Would it be possible to integrate MapLibre Native for iOS while retaining most of the existing Java code?

I realize the importer is still new, so I'm not expecting everything to work out of the box. Just trying to get a sense of whether this is a reasonable approach before diving in.

Thanks!

[benitoalba]

Hi! I'd treat this as a partial port. The current importer flags MapLibre Android, Room and WorkManager as dependencies its compatibility runtime doesn't cover.

• MapLibre: You could wrap MapLibre Native for iOS behind a Codename One native interface and expose its map view as a PeerComponent. That requires a custom bridge and changes to code using the Android MapLibre API. Portable Java application logic can remain above that bridge.
• Room / SQLite: Room isn't provided, but SQLiteOpenHelper, SQLiteDatabase and cursors are supported. The compatibility layer uses one database connection, so shared database work needs serialization across tasks.
• WorkManager / foreground services: These need replacements. Android services aren't supported by the compatibility layer; use Codename One APIs or an iOS native implementation for scheduling and background tracking.
• Sensors / Keystore: Those Android APIs also need Codename One or platform-specific replacements.

Your programmatic Java UI can be reused where it stays within the supported view APIs. I'd prototype the iOS MapLibre bridge with your offline PMTiles and GeoJSON first, then test background GPS recording and persistence on a device before committing to the full migration.

[shai-almog]

Hi,
even though it's new it can handle some of the work out of the box. To set the expectations I would never expect this to be seamless and iOS porting requires a lot of effort in terms of signing etc. (we help a lot with that but there are complexities).

The TL;DR is "partly, and not MapLibre.". Today there are some gaps in the list (see below), but we're looking at addressing them and hopefully other than MapLibre we can make the rest closer to seamless.

The importer as it is today should work for: activities, fragments, views and widgets (built in XML or in code), resources, and the android.database.sqlite APIs. Your programmatic Java UI and the raw SQLite code are a good fit. Room, WorkManage, LocationManager, foreground services, SensorManager and Keystore are all good candidates to add to the tool. We're looking at them right now. We have our own solutions for all of these so you can just start porting today or wait.

MapLibre won't come across. It's a native SDK, and the importer can't seamlessly translate third-party binary libraries. Codename One has builtin support for vector mapping and lets you download map files etc. I think updating the code to use that would be the easiest/best path and would still keep your ownership of the map.

If you must use this specific library you can use a native interface that wraps MapLibre Native on iOS and the MapLibre Android SDK on Android, shown as a native peer component. Your Java code would call that one interface on both platforms. That's a painful route though.

[shai-almog]

These were all merged and should be available this weekend with version 7.0.280. The MapLibre support would still need your decision though.

[fckdsko-apps]

Woah that's incredible. Thanks for being on top of it.

…

On Sun, Oct 25, 2026, 3:36 AM Shai Almog ***@***.***> wrote: These were all merged and should be available this weekend with version 7.0.280. The MapLibre support would still need your decision though. — Reply to this email directly, view it on GitHub <#6088?email_source=notifications&email_token=CJSF27JTJSZNPDNKPLL3V6D5VW3RXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJRG42TSOJWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-19175996>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CJSF27OJUJJZWOZZ3EWZPQL5VW3RXAVCNFSNUABHKJSXA33TNF2G64TZHMZTEOJXGM2DMNZ3IRUXGY3VONZWS33OHMYTCMJRGQ3DEMVBOYBA> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CJSF27JWFGFJ3PABVLB46R35VW3RXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJRG42TSOJWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android <https://github.com/notifications/mobile/android/CJSF27PQRL4PDMEBLWEHTHT5VW3RXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJRG42TSOJWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.*** com>