Support

FLOID for Mac and floid.design

Bug reports, feature requests and questions all go to one inbox: support@floid.design. A real person reads it.

Getting started

Making something appear

Double-click open space on a schedule for a bar of default length, or press and drag across the space to draw one of an exact length. Either way the editor opens on it.

Moving it

Drag a bar sideways to change its dates, up and down to change where it sits — including across into another schedule. Moving a bar moves everything nested under it.

Nesting

Drop an item onto a bar and it becomes that bar's child, keeping the dates it already had. Drag it back out onto open space to un-nest it. There is no add task button — dragging is the whole organising model.

Linking

Hover a bar and a small dot appears just outside each end. Drag one onto another bar or milestone to draw a dependency. Which two ends you connect is the kind of link. A link never moves your work; it prints in red when the order it records is broken.

Keyboard

⌘N new project · ⌘O open · ⌘S save backup · ⌘E export · ⌘Z undo · ⌘= / ⌘- zoom · ⌘0 zoom to fit · ⌘T go to today. The full list is under Help ▸ Keyboard Shortcuts.

Files

• .floid — one schedule, for sharing.
• .floid-project — a full backup of a project.
• .png — the timeline as an image, everything expanded.
• .pptx — the timeline as one editable PowerPoint slide, honouring what you have collapsed.

On the Mac, double-clicking a .floid or .floid-project file in Finder opens it in FLOID.

Where your work is kept

In the Mac app, projects live in the app's sandbox container. On the web they live in your browser's storage for floid.design. Neither is a cloud account, so neither is backed up for you — use File ▸ Save Backup, or turn on backup reminders in Settings. Deleting the app, or clearing the site's data, deletes the projects with it.

Requirements

FLOID for Mac needs macOS 12 Monterey or later and runs natively on both Apple silicon and Intel. The web version needs any current browser.

Still stuck

Write to support@floid.design with what you were doing and what happened instead. If a project is involved, attaching its .floid-project backup makes it far quicker to reproduce.