About tourkit

tourkit is an open-source product tour and onboarding walkthrough library for React and React Native. A tour is a TourConfig array holding plain data, with no imports from any renderer. @tourkit/react draws that array in the DOM and @tourkit/native draws the same array with Reanimated and SVG, so one definition covers a web app and a mobile app.

Why it exists

Every other library in this space targets one platform. A team shipping both a web app and a React Native app has to write the onboarding twice, in two libraries with different concepts, and keep the two copies saying the same thing as the product changes. tourkit moves the tour into data that both renderers read, so the copy, the ordering and the conditional logic live in one reviewable file.

The engine, @tourkit/core, has no dependencies and knows nothing about React, the DOM or React Native. That is what makes a second renderer possible, and it is why the headless path exists for anyone who wants to draw the overlay themselves.

Status

Alpha, at version 0.2.0. All five packages are published on npm. The web renderer is verified in Chromium through an end-to-end suite. The React Native renderer builds and typechecks against the shared steps file, and its pure geometry layers are unit tested, but it has not yet been verified on a physical device. The optional @tourkit/ai package has no verified live model call. Those limits are stated in the repository rather than smoothed over, because a pre-1.0 library that overstates its coverage costs its users more than it gains.

Licence and maintenance

MIT licensed, copyright 2026 tourkit contributors. The source, the issue tracker and the release history are all on GitHub. Packages are published to npm under the @tourkit scope. There is no company behind it, no hosted service, no account to create and no telemetry. The optional AI feature calls a model from your own backend using your own key; nothing is proxied through tourkit infrastructure.

How this site is built

The documentation is markdown committed in the same repository as the library, and the code samples on those pages are mirrored into a typechecked example package in CI, so the docs cannot drift away from the API. This site renders that markdown with Next.js, and its own product tour is built with @tourkit/react.

Elsewhere