KMPToolkit

A collection of small, independent Kotlin Multiplatform libraries (Android + iOS) — haptics, audio record/playback, local scheduling, secure key-value storage, permissions, notifications, raw accelerometer readings, and a database-agnostic transactional uploader. Each module is published as its own artifact — take only what you need — and the whole suite is released together on a single version, so two KMPToolkit artifacts on one classpath can never come from different releases.

Every artifact solves exactly one problem and depends on as few others as possible. You add kmptoolkit-haptics without pulling in an uploader engine, a notification system, or Compose. See docs/01-architecture.md for the principles every module follows (no bundled DI framework, no hardcoded consumer identifiers, no user-facing text) and why.

See docs/README.md for the full documentation index and the recommended reading order.

Add the BOM to align every module on one version, then pull in only what you use:

dependencies {
    implementation(platform("io.github.jamal-wia:kmptoolkit-bom:<version>"))
    implementation("io.github.jamal-wia:kmptoolkit-logging")
}

KMP module resolution needs platform() at every source set that declares the dependency, not just commonMain — see KT-58759 if a version fails to resolve on a specific target.

class UserRepository(private val loggerFactory: LoggerFactory) {
    private val log = loggerFactory.logger("UserRepository")

    suspend fun loadUsers(): List<User> {
        log.i { "loading users" }
        return emptyList()
    }
}

// production
val repository = UserRepository(createLoggerFactory())

See docs/00-getting-started.md for a from-scratch walkthrough, and each module's own docs/<module>/02-getting-started.md for a runnable example.

• docs/README.md — full documentation index and recommended reading order
• docs/01-architecture.md — cross-cutting principles and why they exist
• CHANGELOG.md — release history
• CONTRIBUTING.md — how to contribute
• LICENSE — MIT