Skip to content
Bartosz BąkLinks
A wide Garden Planner garden with paths, seating, trees and an arbor
The browser workspace keeps spatial feedback immediate while a garden is composed in 3D.
Flagship product2026—now

Garden Planner

A browser-based 3D garden design application for arranging, saving and sharing outdoor spaces.

Open Garden Planner
Status
Active product
Role
Product direction, UX/UI, front-end architecture, 3D systems and implementation.
Core stack
React · JavaScript · Three.js · WebGL · Vite
Period
2026—now
Garden Planner showing a 2D plan beside the matching 3D garden
Both views read the same canonical project geometry; the current Plan Overlay is an inspection layer rather than a second runtime.

Context

Garden Planner turns Zafiro into a focused consumer product: an accessible browser workspace where a garden can be authored in 3D, inspected as a plan, saved locally and published without installing specialist software.

An independent browser workspace on Zafiro where people can begin with an empty garden or a starter design, author the 3D scene, inspect the same canonical geometry in a read-only 2D plan, keep local project saves and publish immutable public views with an optional detached edit copy.

Make spatial garden design approachable for an individual user without reducing the product to a flat 2D planner or exposing the complexity of a professional CAD tool and its 3D runtime.

Media narrative

Garden Planner path editor over a 3D garden with material and geometry controls
A focused path workflow exposes useful dimensions and materials without presenting a full CAD interface.
A published Garden Planner garden with camera controls and an edit-copy action
Publishing creates an immutable public view; Create your own version starts a detached editable copy.

Product decisions

  1. Keep Garden Planner an independent Zafiro consumer with its own entrypoints, UI and state, without importing Isle Lab workflows.
  2. Treat Plan Overlay as a read-only 2D view over canonical project geometry, not as a second runtime or a second source of truth.
  3. Separate the current working draft, saved project slots, immutable publishing and the detached edit-copy flow.
  4. Store geometry in metres and resolve language and display units at the UI boundary.
  5. Keep precision in the engine while presenting a deliberately consumer-first workflow rather than a CAD interface.

Engineering

  • Maintaining canonical root-plot geometry and Surface Layers across project state and rendering.
  • Keeping the read-only 2D plan and live 3D scene aligned to the same project geometry.
  • Serialising, hydrating and publishing project snapshots while preserving a read-only public route.
  • Preserving product ownership without depending on Isle Lab-specific workflows or UI.
  • Feeding starter designs and authored scenes through the product's world-data and asset pipeline.

Evidence

  1. The main MVP surfaces have complete public language packs for English, Polish, German, French and Spanish.

    Product implementation documentation

  2. The new-project flow includes Empty Garden, Family Garden, Modern Patio Garden and Natural Garden starter designs.

    Product implementation documentation

  3. The Current Editor Session is separate from the list of saved projects.

    Product implementation documentation

  4. A browser and device can currently hold up to five local saved project slots.

    Product implementation documentation

  5. Publishing creates an immutable public project link.

    Product implementation documentation

  6. The public project route is read-only and does not persist edits into the published snapshot.

    Product implementation documentation

  7. The production Garden Planner route is publicly accessible.

    Open Garden Planner

Limitations

  • Saved project slots are currently local to the browser and device rather than cloud-synchronised accounts.
  • Plan Overlay is currently a read-only inspection view; authoring remains in the 3D workspace.
  • The product is intentionally consumer-first and is not a professional CAD system.
  • Region-specific plant packs, locale-aware numeric parsing and share-link locale behaviour remain future work.