How the three apps work together

Leadsheet.app is three apps around one document: Write to author, Library to organise, version and share, View to read and perform. A song is its neumaRk text — the three apps are simply the ways you write it, keep it and read it. This page follows a song as it moves between them, and points to where each thing really lives.

One song, three lenses

The same song looks different depending on the app you're in:

App	What you do with the song	The boundary
Write	author and edit the NRK text, hear it played back, export it	the only place you edit and the only place with audio
Library	organise it, tag it, place it in books/playlists, share it, manage roles and versions	where you share and manage who can do what; you rename here or from Manage document in Write
View	read it, transpose it for your instrument, export a PDF	read-only: it never changes the stored song, and it has no audio

Keeping these boundaries in mind avoids the most common confusion: to correct a note you go to Write, not View; to press play you're in Write; to share you're in Library (to rename, also in Write, from Manage document).

The document's life — Write → Library → View

The typical journey of a song, and where each step happens:

1. Author (Write). You write the neumaRk text and the score preview updates as you type. When you Save, the song lands in the cloud and becomes an entry in your Library. Write never overwrites a stored version silently — see how saving and versions work in Write.
2. Organise & share (Library). The saved song now has a title, tags and a place among your songs, books and playlists. Here you rename it (Write can too), decide who can open it (roles) and create a share link (Links & sharing).
3. Read & perform (View). Whoever receives the link — or opens a public song, a .nrk file or a collection — reads it in View. They can transpose it for their instrument or export a PDF without altering the stored song.

The loop can close on itself: a reactive share lets a View reader follow your Write edits live (below).

Moving between the apps

You don't switch apps from a menu: you click a link, and how you click decides where it opens — same tab, a fresh tab, or an already-open tab you want to reuse. The three gestures (and why the modifier is the Z key) are described once on the ecosystem overview.

A couple of everyday cases:

• Keep one reading tab. You have View open on a stand. From the Library you Z+click another song and the same View tab swaps to it — no second tab, no reload of the app.
• Fix something you're reading. View can't edit, so open the song in Write (from View's toolbar, or Z+click), correct it and save. Hard and reactive link holders get the update; fly link holders keep the older snapshot.

Sharing across the apps

A share link is where a song leaves your hands, so the kind of link matters more than anything:

• a fly link carries the whole song inside the link (opens offline, no account, perfect for a QR code) but is a frozen snapshot you can't recall;
• a hard link is a reference to the saved song — always current, and access you can grant or revoke;
• a reactive link is a hard link that updates live, for rehearsals and lessons.

What each one carries, how it behaves over time and who can open it is on the dedicated page: Links & sharing. Links are created from the Library (with a QR code); a fly link can also be generated from Write.

Roles across the apps

Who can do what with a song travels with it everywhere. You manage roles in the Library (invite by email, remove, transfer the creator role, and people can resign a role they were given); in Write the role you hold shows up as a badge. The full list — Creator, Owner, Collaborator, Viewer, Subscriber — and how the Library groups them (Creator / Can modify / View only) is on Roles.

A few things worth remembering: transferring the creator role is irreversible for you (you lose all control of the song); resigning leaves someone else's content, while deleting is the creator removing their own; and subscribing to a public song gives you reading access, not the right to edit.

Versions, seen from every app

"Version" means two different things — keep them apart:

• Save history — the song's own versions as you save it: a working draft becomes stable, and a Release locks a stable version. This belongs to the save model in Write / Library.
• In-file arrangements — several variants living inside one song (the %% versions of the neumaRk text). The reader chooses which one to show; the picker (the v badge) works in both Write and View, and remembers your choice per song. This is a language feature — see neumaRk.

Common cross-app tasks

You want to…	Do this
Share for a gig with no wi-fi	a fly link + QR: it opens offline and without an account (it's a snapshot, later edits won't reach it)
Let a bandmate edit too	Library → Manage roles → invite as Collaborator (a role, not a link)
Have everyone follow your edits live	a reactive link; in Write you take the Lead so your saves appear in everyone's View
Open a song in View but keep your current View tab	Z+click the link
Correct a wrong note you spotted in View	open it in Write, fix, save

In short

• Write authors and edits (and is the only place with audio); Library organises, shares and manages roles and versions (and is where you rename, besides Write's Manage document); View reads and performs, read-only.
• You move between them by clicking links — the gesture decides the tab.
• A song travels through a link; the kind of link decides whether it's a frozen copy, a controlled reference, or a live one.
• Roles decide who can do what, everywhere; versions come in two flavours (save history and in-file %% arrangements).