Skip to main content
The last step of first-run setup offers to open the sample project. Take it. It is the fastest way to understand how FlowDeck works, and it costs you nothing — it is a separate repository in its own folder, with no remote, that never touches your own projects. Declined it, or want it back later? Open File ▸ Add Project… (⌘O) and use the “You can also try out the sample project” link under the three tiles.

​
What you get

A small iOS weather app, in a real git repository, already configured: a scheme, a dedicated simulator, and a saved destination. Build and Run work on the first click. Nothing asks you to configure a project before you can try anything. It opens on a pinned Welcome screen with four steps. Work through them in order and you will have built the app, read a diff, followed a failing test, and executed a plan.

​
The sessions

The sample is a tour, not filler. Each session is named after real work and opens the panel that suits it, so you see the app arranged the way it would be for that job. Main Session is the main checkout, with its own conversation walking through the app’s layout and what to know before changing it. It is a real session — you can work in it. One session carries uncommitted changes on purpose, so the Changes tab has something in it the moment you open it.

​
It is a real project

Everything you can do to your own code, you can do here: edit files, build, run on the simulator, run the tests, commit, and ask the agent to change something. The repository is local only — there is no remote and nothing to push — so you can be as destructive as you like.
The sample project lives at ~/.flowdeck/sample-project with its own dedicated simulator named FlowDeck Sample Project. It is separate from every project you add yourself.

​
After the tour

Add your own project with ⌘O whenever you are ready — New App to scaffold one, Local folder to open what you already have, or GitHub to clone it. The sample stays where it is; there is nothing to finish or dismiss.