Flyout guide
How to keep code snippets and notes together on Mac
A saved command is more useful when you know why you saved it. Keep the problem, the code and the result in one note so you can return to it without reconstructing the whole investigation. Here is a small example you can adapt in Flyout.
1. Write the problem before the code
Give the note a title you would recognise a week later. Add the symptom, where you saw it and what you expected. A note called “Date-only booking shifts back a day” is easier to find than “JavaScript snippet”.
Use a library note if you want to organise the investigation with folders and tags. A quick page works for temporary scratch work.
# Date-only booking shifts back a day
Observed: the booking summary shows the previous date.
Expected: a date-only booking keeps the calendar date entered.
Next check: compare the stored value with the display formatter.2. Put the snippet in a code block
On an empty line, type /code and select Code block. Paste the snippet into that block and choose its language from the block’s language control. Keep your explanation in ordinary paragraphs around it.
This example inspects the stored date value. It is text to save and run in your own development environment; Flyout does not execute it.
const storedDate = '2026-09-07';
console.log({ storedDate });
// Inspect the display formatter separately.3. Keep the next check in the same note
Below the block, type /todo for a task with a status. Mark the formatter check as in progress; move it to in review when a proposed fix needs a second look. Use /check for a simple done-or-not checklist.
Write down the actual result when you run the check. A code block records the snippet; the surrounding note records what you learned.
- [in-progress] Check the display formatter
- [todo] Test the same booking in another time zone
- [todo] Record the result and link the fix4. Keep the note beside your editor
Open Flyout with ⌥⌘N and use the pushpin at the top of the panel to keep it open. Click back into your editor and work from the note. Click the pushpin again when you want the panel to hide as you move away.
Use a reminder on the note or a selected line if the next step belongs later in the day. A task status describes progress; a reminder tells you when to return.
5. Export it or continue on iPhone
Flyout stores note content as Markdown in its local database. Export the note as Markdown when you want a file for a repository or another editor. A task marker such as - [in-progress] remains readable text; another Markdown app may not display Flyout’s status icons.
For the same library on Mac and iPhone, enable iCloud sync in Flyout on both devices using the same Apple Account. The web license includes iPhone access. Sync is optional and is separate from license activation.
When to use a different tool
Use a snippet manager or editor feature when you need text expansion, parameterised templates or code execution. Use a file-based editor when the note must already be a .md file inside your repository. Flyout fits a different step: quickly capturing a snippet with its explanation and next action in the screen-edge panel.