Comparison 1 / 16
This comparison shows a tab-model difference: v5 uses Map, List, Survey, and Activity, while the current PWA uses Map, Activity, Survey, and History.
Building panel over Map, with Map/List/Survey/Activity still visible.
Selected building panel with Map/Activity/Survey/History navigation.
This comparison shows a map-encoding difference: v5 separates status and building type in the legend and markers, while the current PWA shows status chips and a MapLibre building list below the map.
Status glyphs, building-type icons, and separate Status/Type legend rows.
MapLibre view with status chips, footprint counts, and a building list below.
This comparison shows a list-structure difference: v5 has a dedicated List tab with search, filters, Nearby first, and grouped rows, while the current PWA keeps the building list inside the Map view.
Dedicated List tab with search, status filters, Nearby first, and group headings.
Building list appears below the Map instead of in a separate List tab.
This comparison shows a building-panel density difference: v5 keeps the header to name and address, while the current PWA puts status, authority, type, group, and local-survey metadata near the top of the panel.
Name and address lead the sheet; details move into directions, status, and reference sections.
Header area includes status, authority, type, group, and local-survey metadata.
This comparison shows a survey-entry difference: v5 opens a location survey directly from the Survey tab, while the current PWA asks the canvasser to start working at the selected building before recording a building survey.
Survey tab starts as a ready-to-fill location survey when no building is attached.
With a building selected, Survey asks the canvasser to start working there first.
This comparison shows an upload-status placement difference: v5 puts saved-on-phone and upload details inside Activity, while the current PWA shows local upload status in History.
Activity includes day stats, upload details, group controls, and feed filters.
History carries the local upload status and current-device survey records.
v5 uses a full-screen person and partner picker with button options. The current PWA uses a team setup panel with a fixed canvasser field, partner dropdown, and Continue to Map.
People are selected from button groups before the canvass starts.
Team setup appears in the canvass shell with a partner dropdown.
v5 shows a custom location prompt before the map. The current PWA fake-data path opens the map without a location prompt.
Location use is explained in a modal before the canvasser continues.
The local fake-data path enters the Map view after team setup.
v5 shows a first-run coaching overlay with the core field loop. The current PWA enters the Map view without a matching overlay in this path.
Three field-loop reminders appear over the map.
The same local path shows the map and building list directly.
v5 uses a compact fixed banner with save status, campaign area, and session label. The current PWA uses a larger header with campaign details, progress, team controls, and map status chips.
Save status and canvass context sit in a two-row app banner.
Progress, team controls, map counts, and upload status appear above the map.
v5 includes an experimental Nearby control and simulated user location. The current PWA map view has no matching Nearby control in this local fixture.
Nearby is toggled on and the map shows a simulated user location.
The map shows status filters and a building list, without Nearby mode.
v5 shows another pair on the building marker with floor text. The current PWA shows a shared-worker marker and initials chip after a local work area starts.
Pair presence appears as a blue tag with the current floor.
Shared work appears as a marker and initials chip tied to the selected building.
v5 keeps the team note behind a collapsed building-note link. The current PWA shows the note textbox directly in the selected-building panel.
The note action is collapsed under Building Status.
The building note textarea is visible in the main panel flow.
v5 opens a short building-linked survey with a context card and unlink control. The current PWA opens the full resident survey with canvass context and Back/Clear actions.
Building context is shown in a blue card with an unlink control.
The resident survey opens with the current canvass context and full form.
v5 shows a Survey in progress return bar above the tab bar after leaving a draft. The current PWA shows the active building card and survey controls inside the flow.
A persistent return bar points back to the building-linked survey draft.
The active building and survey controls remain inside the current survey flow.
v5 asks before completing a building while another pair is active. The current PWA shows active work-area controls and status buttons for the local worker.
A confirmation appears before completing a building with another pair present.
The selected building shows active local work-area controls and status buttons.