20 Jul 2026 Release
20 Jul 2026 Release
Status and People field fidelity, Create Form sections with an optional stepper, richer URL prefill, Board layouts with drag-and-drop, Details polish components (Metric Card, Media Gallery, Status Timeline, Unique ID Chip, Select badges), and reliability fixes for hidden-screen navigation, Board drag writes, publish recovery, locale-aware number input, datetime time zones, and Page Content display.
Earlier updates For Everyday chrome screens and published-app look & layout, see the 19 Jul 2026 Release. For form URL prefill (v1), desktop submit placement, Page Content TOC, and builder nav rail, see the 18 Jul 2026 Release.
What’s new at a glance
Status + People fidelity
Notion Status colors and People chips in lists/Details; People writeback
Form sections + stepper
Group Create Form fields; optional step-by-step Next/Back/Submit
Prefill v2
Prefill Date, Multi-select, People, and Relation from the URL
Board list view + DnD
Kanban columns from Status/Select grouping; drag cards to update Notion
Hidden screen navigation fix
Screens off “Show in navigation” still open from buttons, links, and form actions
Trust and reliability fixes
Publish recovery, locale number parsing, datetime time-zone write-back, clearer sync/reload copy, and Page Content recovery states
See Bug fixes below
Status looks like Notion.
People chips write back.
Long forms can step.
Board columns + drag to update.
Details show metrics, media, timeline, and IDs.
Hidden screens stay reachable.
Publishing and write-back are more forgiving.Overview guide For a single walkthrough of Board + Details polish, start with Board Layouts and Details Polish.
Features
1. Status and People field fidelity
Notion Status option colors now flow into list tags and Details chips. People / Owner values render as chips (avatar when available). New People create/update fields default to multi-select. Editing Owner in the app writes back to the Notion People property.
Where to verify Open a List with Status tags, open Details for Status + Owner chips, then edit Owner on an Update Form and confirm Notion updates.
Guide: Status and People Field Fidelity
2. Create Form sections + optional section stepper
Add Section components to group fields under titles such as Basics and Details. Optionally enable the section stepper so end users move one section at a time with progress text, Next, Back, and Submit on the final step. Mobile keeps progress readable and actions in a footer so controls do not cover fields.
Guide: Organize Create Forms with Sections and an Optional Stepper
3. Prefill Create Forms from a URL (v2)
URL prefill on Create Forms now also supports:
Date
opening_date=2026-09-15
Multi-select
tags=Patio,Delivery
People
owner=user@example.com
Relation / Page selector
location=<recordId>
Text, long text, number, toggle, and single-select continue to work as before. Prefill still applies when fields live inside later stepper sections.
Guide: Prefill Create Forms from a URL
4. Board list view + drag and drop
List screens can use Board as a view type (alongside List, Grid, and Calendar). Columns come from grouping on a Status or Select field. When that field is writable for Board updates, makers and end users can drag a card between columns to write the new Status/Select value back to Notion. Tap still opens Details.
Where to verify Set List → Appearance → Board, group by Status, drag a card in preview and in the published app, then confirm Notion.
Guides:
Overview: Board Layouts and Details Polish
Deep dive: Board List View
5. Metric Card
New Metric Card view component for number, formula, or rollup fields — shows a large, scannable KPI on Details (for example Score 92).
Guide: Metric Card
6. Select option badges
Notion Select option colors appear on list tags and Details chips (for example Priority P1), consistent with Status color fidelity.
Guide: Select Option Badges
7. Media Gallery
New Media Gallery view component for Notion Files & media — thumbnail grid with lightbox. Viewing only; uploads still use Create/Update file or image components.
Guide: Media Gallery
8. Status Timeline
New Status Timeline view component — horizontal lifecycle of Status options with the active status highlighted. Read-only display; change Status via Board drag, Update Form, or multi-row update.
Guide: Status Timeline
9. Unique ID Chip
New Unique ID Chip view component for Notion Unique ID properties — compact monospace chip (for example RST1).
Guide: Unique ID Chip
Bug fixes
Hidden screens open again from buttons and links
Show in navigation is display-only for chrome (bottom / side / top nav). A regression incorrectly removed hidden screens from route registration, so buttons and form actions that navigated to those screens did nothing.
After this fix:
Hidden screens stay out of navigation menus
Buttons, links, redirects, and form actions can still open them
Access control / personalization is unchanged — hiding from nav is not a security boundary
Docs: Screen Navigation Visibility
Mobile section stepper overlap
On phone-sized Create Forms with the section stepper enabled, step labels and Next / Back could overlap form fields. Progress now sits above the content and actions stay in a compact footer aligned with form padding.
Board card drag persistence
Dragging a Board card between columns now persists through a single-record update on List layouts, so Status/Select changes from drag-and-drop save reliably even when the screen does not use multi-row update. The backend now recognizes writable Board grouping fields for single-card Status/Select updates, and the frontend keeps the Board card state in sync after the drag.
Publish after a sync wait no longer fails when the builder state remounts
Publishing could fail after a data sync or builder remount if the application temporarily disappeared from local builder state before the publish request was assembled. In some cases this surfaced as a generic publish failure or a stale update conflict.
After this fix:
Publish waits for the same app to return after the sync wait
If needed, the builder rehydrates the same app from the API before publishing
Publish no longer reuses a stale pre-sync update payload
The confirmation popup stays mounted until a valid publish request is ready
This is especially helpful for large apps where a data sync, app save, and publish can overlap.
Locale-aware number input and URL prefill
Number fields now normalize common locale formats before validation and write-back. This makes number entry more forgiving for makers and end users who type values with commas, periods, or spaces based on their locale.
Examples now handled more consistently include:
1,51.51,234.561.234,561 234,56
This applies across the frontend conversion path and backend validation/coercion path, including create/update form submissions and URL-prefilled number values.
Datetime write-back preserves Notion time zones more safely
Datetime fields now prefer the IANA time zone name from Notion when one is available, rather than relying only on offset mapping. This reduces DST-sensitive write-back problems where a datetime could drift when converting between Notion, NotionApps, and the user’s local browser zone.
Date-only fields remain date-only. Datetime fields keep using date/time visibility and now carry a more stable time-zone value through write-back.
Page Content empty and retry states
Page Content display has clearer loading, empty, and retry states. When Notion page content is not available yet, users should see a more understandable recovery path instead of a confusing blank area.
Clearer “Sync from Notion” wording
The builder copy now distinguishes between:
Sync from Notion: manually pulls the latest Notion records and property changes into the builder
Automatic Data Reload: refreshes published apps on a schedule
Refresh app data: refreshes live app records for end users
This replaces the older, overloaded “Reload Data” wording in the builder tour and related UI copy.
Refresh guidance after deploy or asset-load failure
The forced refresh message now explains that NotionApps may need a page refresh when the browser fails to load the latest assets, or when a new version has been deployed. This should make blank-screen recovery clearer for makers and users.
Internal build reliability
The locale-number regression script was adjusted so staging and production build pipelines can treat it as a module. This was an internal packaging fix to keep the release build clean.
Documentation for this release
Board Layouts and Details Polish (overview)
Board List View
Metric Card
Select Option Badges
Media Gallery
Status Timeline
Unique ID Chip
Status and People Field Fidelity
Organize Create Forms with Sections and an Optional Stepper
Prefill Create Forms from a URL
Screen Navigation Visibility
Recommended learning path
Board Layouts and Details Polish (overview)
Re-test any screen that uses Show in navigation off with a button action — Screen Navigation Visibility
Availability notes
Status colors / People chips: available after Publish on apps that already use Status and People properties
Form sections + stepper: Create Form screens; enable the stepper in Behaviour after adding Section components
Prefill v2: Create Form only; requires Publish after mapping URL parameter names
Board: List screens only (not reference-list comps); requires grouping; drag writes need a writable Status/Select grouping field
Metric Card / Media Gallery / Status Timeline / Unique ID Chip: add on Details (view) screens; opt-in components — existing apps unchanged until you add them
Select badges: appear when Select/Status option colors are synced from Notion and shown as tags/chips
Hidden screen button navigation: frontend fix; no maker configuration change required beyond Publish / refresh
Publish recovery: frontend fix; no maker configuration change required
Locale-aware number input: frontend and backend fix; no maker configuration change required
Datetime time-zone write-back: frontend and backend fix; no maker configuration change required
Page Content recovery states and clearer sync/reload copy: frontend fix; no maker configuration change required
List / Grid / Calendar and Automation Work Queue behavior unchanged unless you opt into Board or the new comps