Shared Kotlin Multiplatform libraries for Coderwise apps, published to Maven Central under the com.coderwise.libs group. Consumers need only mavenCentral() — no credentials.

All modules target Android · iOS (arm64, sim-arm64) · JS · Desktop (the map modules additionally target Wasm/JS) and publish under com.coderwise.libs. "Latest" is the newest version on Maven Central.

The sample/ directory holds an unpublished demo app for the map libraries that runs on all five platforms (Android, iOS, Desktop, JS, Wasm/JS) — see its README for run commands.

A library manifest merges into every consumer, so a permission declared here is a permission declared for every app that depends on the module — including apps that never ask the user for it, but must still justify it on their store listing. An app using only rememberCameraPermissionState would ship ACCESS_FINE_LOCATION; an app that registers locationModule in DI without resolving a LocationProvider would ship both location permissions.

So :permissions and :location declare none. The consuming app declares what it actually uses — the KDoc on each remember*PermissionState and on LocationProvider names the Android permission and any Info.plist key it needs.

Migration: :permissions before 0.4.0 and :location before 0.2.0 declared ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION. Apps that relied on that merge must add them to their own manifest when upgrading — without the declaration Android denies the request without prompting, and LocationProvider returns Result.failure(SecurityException).

StoreKit 2 is Swift-only — Product and Transaction are Swift types built on Swift concurrency, which Kotlin/Native's Objective-C interop cannot see — so the module ships no iOS store logic. It exposes a StoreKitBridge protocol that the consuming iOS app implements in Swift and hands over with installStoreKitBridge(bridge) before anything resolves Billing.

An app that never calls it still runs: Billing.isAvailable reports false and every call is inert, which is what keeps the simulator — where there is nothing to buy — working without one. Android needs no such step; androidContext() is the only thing Play Billing takes from the app.

Each module is versioned and released independently, via the vanniktech maven-publish plugin (Central Portal upload, GPG signing, sources/javadoc jars).

The release tag is the single source of truth for the version. Tag a module release as <module>-v<version>; the publish workflow parses it, passes -PlibVersion, and publishes only that module:

git tag utils-v0.4.0    && git push origin utils-v0.4.0     # → com.coderwise.libs:utils:0.4.0
git tag map-core-v0.1.6 && git push origin map-core-v0.1.6  # → com.coderwise.libs:map-core:0.1.6

Note: the publish workflow runs on a macOS runner (required for the iOS Kotlin/Native targets), which bills GitHub Actions minutes at 10×. Validate locally with publishToMavenLocal first; publish deliberately.

The same workflow also accepts a manual workflow_dispatch (module + version inputs). It needs these repo secrets (same values as the other coderwise repos — com.coderwise namespace is already verified): MAVEN_CENTRAL_USERNAME, MAVEN_CENTRAL_PASSWORD, SIGNING_KEY_ID, SIGNING_PASSWORD, GPG_KEY_CONTENTS.

Local, keyless (publishes as 0.0.0-LOCAL unless -PlibVersion is given):

./gradlew :utils:publishToMavenLocal

Drop it in as a top-level folder with a build.gradle.kts (settings.gradle.kts auto-includes it). Mirror :utils: apply the vanniktech plugin, read the version from libVersion (default 0.0.0-LOCAL), set coordinates("com.coderwise.libs", "<name>", …). Release it with a <name>-v<version> tag — no workflow changes needed.

:utils originated in coderwise/maps-mobile (published through 0.2.0) and was extracted here; com.coderwise.libs:utils coordinates are unchanged, so consumers required no edits beyond the version bump. The :database, :settings, :location, :permissions, :map-core, and :map-engine modules were added here to share infrastructure across the *.mobile apps. :imagepicker was extracted from coderwise/cards-mobile (where it lived as :libs:imagepicker); its package moved from com.coderwise.cards.libs.imagepicker to com.coderwise.libs.imagepicker. :logger was extracted from coderwise/miles.mobile (:libs:logger) the same way, moving from com.coderwise.mileson.libs.logger to com.coderwise.libs.logger; its iOS log file name became a parameter of enableDeviceVisibleLogging, having been a hardcoded mileson.log. :billing came out of coderwise/miles.mobile (:libs:billing) by the same route, moving from com.coderwise.mileson.libs.billing to com.coderwise.libs.billing; nothing about it was app-specific beyond the doc comments, which named the one product MilesOn sells. rememberShareTextLauncher (utils 0.5.0) came from the same repo's :libs:share, which had grown as a better-behaved copy of shareText; the module was deleted there in favour of this one. Both APIs now share the platform code, so shareText inherited the iPad popover anchor that its own iOS implementation was missing.