Getting started

apprenti.dev is not a learning platform with an account and a server behind it. Your apprenticeship lives in a Git repository. The app reads that repository, lets you work on it — often with no network at all — and writes your progress back to Git when you're ready. There is no application backend, so there is nothing to sign up for beyond a place to put a repository.

Get the app

Download the newest non-prerelease from GitHub Releases, or browse all versions if you need a specific build. Installing the app has the per-OS steps — these are sideloaded zips and an APK, not store listings. Then come back here to open a curriculum.

What you need

  • •A curriculum repository: either a GitHub/GitLab URL to clone, or a folder already on your device.
  • •If the repository is private, or you plan to push your own work, a personal access token for that provider.

Open a curriculum

  1. Open More.
  2. Choose one:
    • •Open local repository — pick a folder on this device that contains a curriculum manifest file.
    • •Clone repository — paste a GitHub or GitLab HTTPS URL for the repository. Public repositories clone without a token; private repositories need one.
  3. If prompted, paste a personal access token (optional). It is stored in this device's secure storage (Keychain / Keystore / platform equivalent) — never in Git, never in the local database.
  4. The app validates the repository, builds a local projection, and the Path becomes browsable.
  5. If the curriculum offers more than one written language, pick a content language here too — this is separate from your app's Appearance language setting, and it's the only place that controls which language task titles and instructions display in.

Offline-first means offline-first

Once a repository is open, everything works without a network connection: browsing the path, reading instructions, writing reflections and notes, logging work, and preparing a submission. The app keeps a fast local copy (for search, browsing, and AI indexing) that it can always rebuild from the Git repository — that copy is a convenience, not the record of truth.

When you're back online, sync is explicit: the app fetches, reconciles anything upstream changed, commits what you've done, and pushes. Nothing you write is silently lost or silently sent anywhere.

Personal folders in your fork

Your apprentice records — profile, task state, reflections, evidence, notes, work log, submissions — live only in your own personal folder in the repository. Curriculum content (tasks, resources, competencies) lives everywhere else and is shared. The app never publishes a fork on your behalf and never strips personal data automatically. If you ever copy or make a repository public yourself, remove the apprentice and mentor personal folders first — and remember that Git history can still contain old copies of those files unless you start fresh.

On GitHub specifically, a fork of a public curriculum is itself always public — there's no setting to change that afterward. See Keeping your fork private for the workaround, and how GitLab handles this differently.

Next

Once a repository is open, continue with Working through your path.

← All Docs Back to apprenti.dev