Updated October 15, 2026 for this checkout. This replaces the original UI mockup checklist. “Implemented” means the capability has code and regression coverage linked below; it does not assert that this branch is deployed or that all devices have passed qualification. See NEXT for remaining work, release gates and dated validation reports, and README for the commands used to run checks.
| Capability | Current scope | Evidence and limits |
|---|---|---|
| Walls and room geometry | Implemented: straight/curved boundaries, detected room polygons, labels and areas. | Room tests, crossing boundaries, curved rooms. Native and web area totals are not an established cross-platform guarantee. |
| Doors and windows | Implemented: wall-mounted openings, curved-wall placement and exported symbols. Each door type has its own 3D model (sliding, French and bifold glazed in metal frames; single and double wooden leaves; pocket slab slid into the wall), and the bifold plan symbol matches its 3D fold. Doors take a Frame Color (named presets or custom) that also paints wooden leaves, and single/double doors a Door Style (slab, shaker, glazed shaker, Victorian shaker, glazed Victorian shaker, fully glazed). | Curved openings, opening hit testing, browser coverage, door symbols, door models (3D leaves open to the plan symbol’s face; pocket slabs stay inside the wall). Symbol/style support is not a photorealistic product catalog. Door open state is fixed per type in 3D, and frame colour and door style are not carried by RoomPlan/package interchange. |
| Wall splitting | Straight and quadratic walls split while retaining room/group references, sloped heights and opening positions. Splits crossing an opening are rejected. | Curve and reference preservation, browser save/reopen. Curves subdivide exactly; fixed rendering facets can change the approximation and estimated area. |
| Wall endpoint dragging | A dragged wall end snaps onto a 0°/45°/90° line from the wall’s other end only within the magnet’s reach (about 15 screen px at any zoom), so the correction no longer grows with wall length. Alt/Option moves freely without magnet, grid or angle snapping; Shift forces the nearest 45° ray; a magnet join to another wall is kept. | Snap tolerance and modifiers (issue #104). The modifiers are exercised at the geometry level; a browser-level drag regression remains open. |
| Selection and history | Implemented: group/individual selection, geometry drag history, clipboard and fit selection. | Drag Undo, clipboard, fit selection. These tests cover named interactions, not every touch/device combination. |
| Room deletion | Deletes the selected room’s saved record and exclusive boundary in one undo operation. Walls and openings referenced by neighboring rooms remain; furniture remains. | Saved/detected room deletion, connected rooms and Undo/Redo. Shared boundaries use wall IDs; coincident walls imported with separate IDs are not qualified by these tests. |
| Unchanged property edits | Reapplying saved room or furniture values preserves Undo/Redo; door/window scalar updates also skip unchanged values. | Room history, furniture interactions, wall/opening updates. This does not assert equivalent handling for every item type or metadata path. |
| Canvas keyboard menus | Shift+F10/Menu opens the selection’s menu. Arrow/Home/End navigation, Enter activation and Escape/Tab dismissal are supported. Explicit Properties/material actions focus their editing controls. | Menu navigation, opening Properties, room actions. Physical assistive-technology qualification remains open. |
| Properties and annotations | Implemented: property drafts, multiline text, annotation visibility and dimension/text exports. | Property drafts, multiline notes, text exports, dimensions. |
| Floors, slabs and stairs | Implemented: floor views/elevations, slab geometry/depth, floor openings and stair symbols. In 3D an Up stair climbs from its floor to the next floor’s elevation and a Down stair descends to the floor below, keeping the same flight (260 cm when there is no such floor). Show All Floors Stacked draws the other floors, including their stairs, translucent or, with Other floors: Solid, opaque to show the whole building; a solid floor in front of the active one stops 3D clicks and placement behind it. | Floor views, stacked floor style and picking (issue #130), slab geometry, floor openings, stair geometry, stair levels and stairs between floors (issue #134), package values. Active Floor Only draws nothing below the active floor, so a Down stair or the stair from the floor below shows only when stacked. In 3D, straight flights still rise opposite to the plan’s arrow and L/U first runs climb away from their landing. Other stacked floors show walls, slabs, columns and stairs in default colours, without doors, windows, furniture or finishes; the stacked view and its style reset when leaving 3D. Common roof forms remain backlog work. |
| Furniture | Implemented: categorized catalog, placement/interactions, loaded 3D assets and fallback representations for unknown items. Properties → Height above floor lifts an item in 3D (wall-mounted TV, plant on a table; issue #131); wall art, mirrors, clocks, sconces and ceiling lights keep their previous mounting heights as defaults. | Catalog inventory, catalog source, interaction tests, model tests, unknown items, elevation and its browser check. Asset attribution/dimension curation and native visual fidelity remain work areas. |
| Local custom models | Implemented: static GLB preview, provenance, source deduplication, placement, saved references and unused-model removal. | Import guide and limits, admission tests, browser import/save, package edit return. Expanded browser, keyboard, native-return and physical-device qualification remains in progress; see the verification record. |
| Interactive 3D | Implemented: Three.js preview and walkthrough; idle rendering stops when interaction settles. | Walkthrough, viewer idle, measured idle report. Idle behavior does not establish active FPS, battery or physical-device memory budgets. |
| Plan exports | Implemented: PNG, PDF, SVG and DXF paths, including annotations and object-only plans. Wall dimension labels follow Settings → Measure walls (centreline or edge to edge); curved walls keep their centreline length. | Object-only exports, text exports, furniture DXF, 3D PNG capture, Measure-walls modes (issue #106). Formats represent different views; none implies lossless editable CAD round trips. |
| Local project storage | Implemented: IndexedDB-backed storage, legacy localStorage migration, save feedback and recovery paths. | Storage implementation, save status, library restore, project opening. Browser storage can fail or be cleared; exported backups remain useful. |
| Project and scan import | Implemented: saved project JSON, Apple RoomPlan conversion and versioned project-package ZIP exchange. Build → Import RoomPlan can also Add to this plan: the scan lands 100 cm right of the matching floor’s content with top edges aligned (missing storey levels become new floors), colliding ids are re-issued, room names are kept, and one Undo removes it. Join to another door… (door context menu or door properties) then snaps the scan onto the far side of the matching door’s wall, doors one wall thickness apart (mean of the two walls), carrying its openings, furniture, notes and dimensions; one Undo (“Joined doors”) reverts it. | RoomPlan tests, scan stitching and door join (issue #103), browser door join, package tests, browser package workflow. Use the package contract for assets, preservation rules and limits. The join needs straight door walls and walls that meet corner to corner; it does not merge the two walls into one. |
| English/Portuguese interface | Typed translation dictionaries cover Settings, library/recovery, editor controls and properties, and major 3D controls. Stored names, catalog identifiers and provider prompt values retain their original meaning. | Key/token parity, dated verification and limits. Remaining catalog text, service errors and device accessibility need further review; complete interface translation is not claimed. |
| Sibling planner interchange | Implemented: Export → Download interchange JSON and Open in OpenLandscape3D / OpenKitchen3D / OpenCatio3D write the family’s prepared RoomPlan JSON (<Project-Name>-openplan3d.json, or a #/import/v1/ link holding the whole plan). Importing a sibling’s file keeps its openkitchen3d / openlandscape3d / opencatio3d block, object attributes, defaults and plan notes on project.interchange and re-emits them verbatim, so cabinets, plants, areas and structures survive a trip through OpenPlan3D. |
Real sibling fixtures, web round trip, transfer links, format notes. Lossy: curved walls export as their chord, sloped walls as their taller end, french/garage → double, pocket → sliding, bifold → single, window types → fixed/sliding; stairs, columns, annotations, measurements, guides, entourage, background images, colours, textures, item details, floor openings (Open to floor below) and floor elevations and slab thicknesses are not exported. The retained blocks travel in project JSON and library backups, not in the native project package. |
| Handoff endpoint CORS | POST /api/handoffs answers OPTIONS with 204 and adds Access-Control-Allow-Origin for the family’s own origins only (apex and app. hosts, their Firebase Hosting sites and preview channels, localhost); never a wildcard, never credentials; Retry-After is exposed. |
Origin allow-list and route tests. Written because the sibling planners’ “Open in OpenPlan3D” preflight was answered 405 in production on October 15; the deployed endpoint still has to be re-checked after release. |
The native companion has its own source, tests and release process. Project-package exchange carries edited geometry and supported attachments between platforms; retained data is not necessarily editable or rendered identically on both sides. The package contract is the format reference. Native validation and hardware/release requirements are tracked in NEXT.
The Mac Blender render workflow and portable render experiments are separate from the interactive web preview. Their current handoff and validation are linked from NEXT; this matrix does not describe them as generally released browser features.
project.interchange in the native package, and the sibling contract questions (write-back of OpenPlan3D edits into retained blocks, a project-name slot, retained section labels).These are work areas, not assertions that every associated interaction is broken. NEXT remains the authoritative backlog. The old comparison review is historical and must not be used as a current release checklist.