Blocks

Blocks are complete screens built from Pyzed’s components, in the spirit of shadcn/ui’s blocks: open one, run it, copy the code into your app and change what you need. Each block is a single runnable file in examples/blocks/, tested in CI in light and dark themes, so the code on these pages always works with the current Pyzed.

LoginA split sign-in screen for Python desktop apps.

DashboardAn analytics dashboard in Python.

SettingsA settings page for Python desktop apps.

Data tableA data table with filters in Python.

ChatA team chat UI in Python.

File explorer and IDEAn IDE layout in Python, like a modern code editor.

Onboarding wizardA multi-step onboarding wizard in Python.

Music playerA music player UI in Python.

Kanban boardA kanban board in Python.

How to use a block

1. Open its page and look at the screenshot in light and dark (switch the site’s theme).
2. Run it: python examples/blocks/<name>.py, or copy the Code section into a file.
3. Keep what you need. Blocks are ordinary pz.App classes: their pieces are methods (sidebar(), header()…) that return widgets, so you can lift one into your own app as is.

Make them yours

• Theme. Set theme = "Gruvbox Dark" (or any theme) on the app, or derive one with your brand color: pz.themes.get("One Dark").with_accent("#e11d48"). Every block uses theme tokens ("accent", "panel", "text_muted"…), never fixed colors for its surfaces.
• Data. The sample data is at the top of each file. Replace it with a database query, an HTTP call or files; slow work goes in a coroutine so the window never blocks (see Async).
• Components. When a piece grows its own state, turn it into a pz.Component so it shows up in Pyzed Design’s toolbox too.
• AI. With the MCP server connected, ask your agent: “Start from the dashboard block and make it show our GitHub issues”. It can read every block with read_example("blocks/dashboard").