Lithic documentation

Lithic is an outliner with a planner attached. You write in one nested list of rows, and the same rows are what you schedule — into a day, a week, a month, a month or a year. There is no second app for the plan and no copy of the task in it: a planner pane is a view of the document you are already looking at.

The idea it is built around: a thought and the time you gave it are the same object. Move the row, and the plan moves. Reschedule it in the calendar, and the document says so.

Use it

• Documents and rows — the outline, what a row can be, and the keyboard.
• Planning a day and a week — periods, timeboxes, the panes, projects, and what "untimed" means.

On a phone

Lithic is a different shape below a tablet's width: one screen at a time, with a bar at the bottom that switches between Document, Agenda and Planner. It opens on the agenda, because a phone is what you have with you while the day is happening. Your browser's back gesture moves back a screen.

Each screen is a real address, so a link you send yourself opens where you left off.

Install it to your home screen. In Safari on an iPhone, tap Share and then Add to Home Screen; in Chrome on Android, the menu offers Install app. It opens full-screen, without the browser's own bars — which is about 90 px of a phone screen given back to the document.

Once it is installed, a reload without a connection opens the app rather than the browser's error page, and the documents you had open come back. Creating and moving things still needs the connection.

What a finger can do to a row: swipe right to archive it and left to delete it, press and hold the left margin for indent, outdent and the two moves — and hold, then drag, to move the row somewhere else. While you are typing, the row grows a second line carrying those four moves and a ✓ to tick it off; it goes when the keyboard goes. The ⋯ opens the row's whole menu as a sheet from the bottom.

The planner offers Day and Month on a phone. A week of seven columns is 49 px each on a 390 px screen, which holds a weekday and nothing else; the agenda's week view is the week, as a list.

Build on it

• API — authentication, access tokens, errors, pagination, webhooks, and pages as Markdown.
• API reference — every endpoint, generated from the OpenAPI document the server emits.
• Markdown specification — the canonical dialect a page serializes to. A document has a dialect of its own; the documents page covers it.

What state is this in?

Pre-1.0, and one thing is worth knowing before you sign up rather than after.

Calendars from elsewhere are mirrored, and the mirror stays read-only. Connect a Google or Microsoft 365 account, an ICS/webcal subscription or a CalDAV server, and those events appear in the planner beside your own rows. Nothing is sent back until you switch a calendar on for writing yourself. After that, a task with a day and a start time can be published to that calendar as an event, and on Google and Microsoft 365 a meeting can be renamed, moved or deleted from here. The limits are firm: a subscribed calendar can never be written to, nothing repeating and nothing all-day can be changed from here, and the tick you put on a meeting stays yours. See Planning for the window, how current it is, and what is deliberately not mirrored.

Everything else on these pages exists and works: writing, nesting, tasks, priorities, headings, notes, links, tags, the archive, repeating tasks, files on a row, planning across year, month, week and day, projects with their tasks, the day, week, month, agenda, period and projects views, multi-pane layouts, search across documents (Ctrl/Cmd + K) and inside the open one (Ctrl/Cmd + F), Markdown copy and paste, downloading a document as Markdown, and the API. Signing up gives you your own workspace.

What is still missing is named where it matters: no file import — a document downloads as Markdown, but nothing reads one back in — and rich text beyond links flattens when it leaves as Markdown.

In another language

Every page here exists in English and German; the switch is in the top bar. The API reference is the exception: its endpoint descriptions come straight from the server's route table and stay English in both.