Interior Shopping List Form Review

Status: draft / prototype review
Module: Project Blueprints
Source prototype: ../intake/formularz_beta_lista_zakupow_v1.html
Related: interior-shopping-list-beta.md, interior-shopping-list-data-model-ui.md

Purpose

This review captures what the first standalone HTML form prototype contributes to the Interior Shopping List Beta.

The source file is not only research text. It is a working local prototype with:

• multi-section questionnaire,
• localStorage autosave,
• JSON preview,
• JSON export,
• reset/load actions,
• mobile-friendly layout.

Prototype Role

The form should be treated as:

• discovery tool,
• beta scope questionnaire,
• early UX test,
• structured payload generator,
• bridge between client conversation and implementation backlog.

It is not yet the target product UI for managing real shopping items.

Form Sections

Section	What It Captures
Context projektu	project name, date, pilot scope, project phase, purchase type
Zakres obecnej bety	MVP size, quantity automation, desired result
Źródła danych	photos, drawings/PDF, readable labels, store detectability, quantity source
Logika produktu	multi-room products, room filters, category depth, required item fields
Interfejs formularza	simple UI, editability, result view, immediate actions
Automatyzacja i AI	OCR, assist-only AI, useful AI tasks, automation level
Finalne decyzje	whether to build next, next step, free notes

Data Fields Introduced

The form adds useful discovery-level fields that should influence the beta plan:

• single_project,
• project_phase,
• purchase_type,
• small_scope,
• scope_size,
• auto_quantity_now,
• main_result,
• has_photos,
• has_drawings,
• clear_labels,
• store_detectable,
• quantity_source,
• multi_room_product,
• room_filters,
• category_level,
• required_fields,
• result_view,
• ui_actions,
• use_ocr,
• ai_assist_only,
• ai_help,
• automation_level,
• build_after_form,
• next_step.

These are not all final product fields. Many are decision fields for discovery and MVP scoping.

Confirmed Alignment With Blueprint

The prototype confirms the earlier blueprint assumptions:

• start narrow,
• use one project or small scope first,
• keep quantities human-reviewed,
• make OCR optional in the first version,
• treat AI as assistant rather than decision-maker,
• export structured JSON,
• support later filters by room and category,
• preserve manual validation.

Differences From Product Blueprint

The form is discovery-first, while the product blueprint is item-first.

The form captures:

• project decisions,
• scope preferences,
• data source readiness,
• UX expectations,
• AI/automation appetite.

The product blueprint still needs:

• actual shopping item records,
• room records,
• source media records,
• review state per item,
• item edit screen,
• client-facing list/export screen.

Useful Product Decisions

The form suggests these MVP decisions:

• keep the first version as a single-project pilot,
• include JSON export from day one,
• keep local draft/autosave behavior,
• keep AI assist-only by default,
• make OCR a switchable capability,
• treat quantity source as an explicit field,
• ask early whether result view should be table, cards, filtered list or mixed.

Implementation Notes

The current prototype:

• stores data in localStorage,
• serializes form values with FormData,
• handles repeated checkbox values as arrays,
• adds _meta.saved_at, _meta.app_version and _meta.storage,
• exports JSON with a filename based on project_name.

This is a good temporary behavior for discovery, but production should move storage to backend/database.

Risks

• The visual style is useful for a local prototype but should not become the final design language without review.
• It has many questions; for real clients, the form may need progressive disclosure.
• It does not upload actual product photos yet.
• It does not create shopping item rows yet.
• It may mix discovery questions with future product settings.

Recommended Next Step

Turn the form into a formal Discovery Payload for the shopping-list beta.

Suggested next artifact:

• JSON Schema for the form output,
• mapping from form fields to MVP decisions,
• first test using 5-10 real products,
• comparison against interior-shopping-list-data-model-ui.md.

Backlog Additions

• define discovery payload schema,
• split discovery fields from product item fields,
• decide whether localStorage remains only for demo,
• add photo upload in next prototype,
• map required_fields to item schema validation,
• build first test with real project data.