# KaMP Kit indexes documents instead of build commands, and says so in its own sanity check > A Kotlin Multiplatform starter app from Touchlab whose README contains not one command, only links into a docs folder, and which answers a failed build by telling you that your configuration is wrong. The repository also publishes no releases. **touchlab/KaMPKit** — KaMP Kit by Touchlab. A collection of code & tools designed to get your mobile team started quickly w/Kotlin Multiplatform - Repository: https://github.com/touchlab/KaMPKit - Website: https://touchlab.co/ - Stars: 2,455 · Forks: 211 - Language: Kotlin - License: Apache-2.0 - Published: 2026-09-28 · Updated: 2026-09-28 · Language: en - Canonical page: https://hysenlabs.com/projects/touchlab-kampkit ## The premise is that what you find elsewhere about KMP is out of date The About section states the problem the kit exists to solve: the KMP ecosystem moved quickly, which left a lot of old or conflicting documentation, blog posts and tutorials, and the primary stumbling block for the teams Touchlab worked with was simply getting started. A paragraph headed as a very important message then says the kit is there because what you find from Google about KMP is likely to be outdated or conflicting with the configuration here, and recommends reaching out directly if you hit problems. Support means the Kotlin Community Slack channel #touchlab-tools, or a direct support request to Touchlab. One issue is open on the repository. ## Clone and build is a link, not a command Section two of the walkthrough is titled Clone and Build and contains no commands at all. It points at docs/APP_BUILD.md and says that by the end of that document you should be able to build and run both the Android and the iOS app. There is not a single fenced code block anywhere in the file. The requirements do live in the README: JVM 17, the Android SDK with the latest stable Android Studio 2023.3 or newer or IntelliJ 2024.1 or newer, and a Mac with Xcode 15 or newer for the iOS build, with a separate document for iOS developers at docs/DETAILED_DEV_SETUP.md. The rest follows the same pattern, an architecture walkthrough at docs/GENERAL_ARCHITECTURE.md and a Kotlin debugging note at docs/DEBUGGING_KOTLIN_IN_XCODE.md. Past the build the walkthrough becomes a code tour, with the instruction to read the app code and libraries, change something and recompile to see how it works. ## A failed build is defined as your configuration being wrong The Sanity Check section is the bluntest paragraph in the file. It says that if you cannot build, you need to get help, and that the sample is configured to run out of the box, so a failure means something is wrong with your build setup or config rather than with the sample. The ask that follows is to reach out so the config or the troubleshooting docs can be improved, and the alternative mentioned is the Kotlin Slack group. Read as a whole, the three sections put the burden on the reader: the docs elsewhere are stale, this sample works out of the box, and if it does not, the gap is in your environment. That is a defensible position for a vendor-maintained reference project, and it does mean a first failure has nowhere local to go. ## Three modules at the root and an .idea directory in the repository The top level holds app/, shared/ and ios/, which is the platform story in three directories, alongside the Gradle pieces: gradlew, gradlew.bat, a gradle directory, build.gradle.kts, settings.gradle.kts and gradle.properties. Also present are .editorconfig, .github/, .gitignore, CONTACT_US.md, README.md, LICENSE.txt and two loose images, kampkit.png and tl2.png, which nothing in the file refers to. Two entries stand out. The .idea directory is a JetBrains project folder kept in version control, and the licence is a file named LICENSE.txt rather than the plain LICENSE name most tooling looks for, next to a metadata licence of Apache-2.0. Support has its own file too: CONTACT_US.md sits at the root beside the README, and the Slack channel is the other route. ## The 2023 update replaced the ViewModel bridge with SKIE A section headed as a 2023 update records the one architectural change the file calls out. KaMP Kit was updated for Touchlab's SKIE tool, which removed a good deal of the boilerplate around sharing a ViewModel, and Kotlin sealed classes can now be used as Swift enums in the iOS side. The detailed write-up is a migration case study hosted on Touchlab's own site under touchlabpro.touchlab.dev, not a document in this repository's docs folder, so the record of the most significant change to the sample lives somewhere a clone does not bring with it. Anyone comparing against an older checkout would have to follow that link to find out what changed underneath. ## Started as a minimal sample in 2020 and now sold as a best practice model The intro says the kit began in early 2020, when there were few sample apps and starting was not trivial, and that it was meant as a minimal sample. It then says the KMP situation has improved considerably since, that barriers to entry have been removed, and that the project now intends to be less about getting started and more a best practice model. Two things stayed behind from the earlier framing. The audience section still expects little to no KMP experience from native mobile developers and their managers, and a section called selling KMP is still in the file, with three links about building a business case and convincing a manager to run a pilot. ## A cut introduction is still linked, and scope is limited on purpose The background education part links docs/WHAT_AND_WHY.md as the original version of that intro, cut because it was pretty long, so the file points at a document for the section it removed. Next to it sits a general introduction to KMP recorded at Oredev in November 2019, which dates the resource list. The scope section is equally direct about the other side: no broad guides, no advanced tutorials, and no support for fixing anything outside the starter app, because the scope is intentionally limited to keep focus. Two workflow badges sit at the very top for the Android and iOS pipelines, and the repository publishes no releases. ## Conclusion Use it when the question is whether a Kotlin Multiplatform setup is worth a trial on your team, since that is the evaluation the project is built to support, and read the docs folder rather than the README before planning anything. Two limits are stated in the file itself: it is not a guide to advanced topics and it offers no support for anything outside the starter app. Pin your own commit, because no release is published, and expect the interop layer to have moved, since the ViewModel bridge was replaced by SKIE in 2023 and its write-up lives off the repository. ## FAQ ### What does KaMP Kit include? Three things: a starter app, which is a native mobile KMP app with a small functional feature set, educational resources on KMP and Kotlin/Native, and integration guides for putting shared code into an existing application. Broad guides and advanced tutorials are out of scope. ### What do I need to build KaMP Kit? JVM 17, the Android SDK with the latest stable Android Studio 2023.3 or newer or IntelliJ 2024.1 or newer, and a Mac with Xcode 15 or newer for the iOS build. ### Is KaMP Kit useful if I already know Kotlin Multiplatform? The audience section says you should have little to no experience with KMP, and the project targets native mobile developers on Android or iOS plus engineering managers for native mobile teams. It adds that some of what follows the setup may still be useful with experience. ### What is SKIE in KaMP Kit? A Touchlab tool the project moved to in 2023. It removed a good deal of the ViewModel sharing boilerplate, and Kotlin sealed classes can be used as Swift enums in the iOS code. ### How do I get help with KaMP Kit? Through the Kotlin Community Slack in the #touchlab-tools channel, or by contacting Touchlab directly about support options. The sanity check section says that a build which fails means your own setup or config is at fault. ### Where are the build instructions for KaMP Kit? In docs/APP_BUILD.md, which the clone and build step links to instead of showing commands. The iOS specific setup is at docs/DETAILED_DEV_SETUP.md and the architecture walkthrough is at docs/GENERAL_ARCHITECTURE.md. ## Sources - [Issues](https://github.com/touchlab/KaMPKit/issues) - [License: Apache-2.0](https://github.com/touchlab/KaMPKit/blob/main/LICENSE) - [Project website](https://touchlab.co/) - [README](https://github.com/touchlab/KaMPKit/blob/main/README.md) - [touchlab/KaMPKit on GitHub](https://github.com/touchlab/KaMPKit) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/touchlab-kampkit