Consistent form fields
Improvements
-
Forms across PropChain (name, contact details, address, property and sale details, invites and party roles, password change) now share the same set of building-block fields, so the same piece of information looks and behaves identically wherever you enter it.
-
Editing one field in a form now keeps every other field's latest value, so changes made earlier in the same form are no longer lost when another field is edited.
-
Work in progress on the new and edit stage forms, your party details, adding a listing, editing a team member and the billing checkout is now kept in the page address, so refreshing the page (or sharing the link) no longer loses what you've entered.
-
Changing a team member's role no longer risks the edit window closing while you work.
-
The "create a new chain" page keeps your answers in the page address more reliably: filling in several fields quickly no longer loses earlier answers, and the page no longer reloads from the server on every change.
-
The listing link you enter on the "create a new chain" page is now kept when you refresh.
-
Reusable building blocks that lived inside PropChain (form fields, address and password inputs, the "add to home screen" guide, the cookie banner, credenza dialog and more) now live in the shared design system, so future Land Your Home apps get the same look and behaviour.
-
The notification bell, status editor, availability badge, licence usage bars and "request update" buttons are now built from reusable design-system components, with PropChain only supplying the data.
-
Animations now respect the "reduce motion" setting on your device: slides and movement are skipped, CSS animations and transitions become instant, and the animated hyperspeed, liquid and floating-line backgrounds and the highlighter draw-in stay still.
-
API request bodies are now validated with Zod 4's strict object schemas, which behave the same as before: unknown fields are still rejected.
Fixes
- Fixed typos in field labels and hints ("Visbility", "curency").
- Push notifications: the test notification now goes to your own subscribed devices, and turning notifications off for a device only removes that device. Previously these could act on another user's most recent subscription.
- The chain and transaction view switchers no longer briefly render a different layout on mobile when the page first loads.
- The cookie banner no longer leaves a pending timer behind when it closes, and the highlighted-text and hyperspeed backgrounds clean up their listeners and observers when removed from the page.
- Icon-only buttons (menu, add licence, revoke licence, customise permissions, delete chain link, add transaction, and the "add to home screen" close buttons) now have names, so screen readers announce what they do.
- Hover and theme-toggle animations (the theme switcher icons, bento cards and the holographic QR card) now animate only the properties that actually change, which keeps them smoother. Date, money and relative-time formatting reuse one formatter instead of creating a new one on every call.
- Buttons that wait on a request (accept an invite or request, revoke a party, update your status, mark a notification read, turn push notifications on or off) no longer get stuck disabled if the request fails.
- The chain and stage board views, the address book and API key scope checks use faster lookups, which helps with large chains and long lists.
- Pages that load data when you open them (chain access checks, team members, stage owners and dependencies, availability badges, licence bars) no longer show stale results if you navigate or switch between items quickly.
- Pages that need several pieces of data (transaction and stage pages, settings, onboarding, new chain, the partner admin screen, chains) now load them at the same time instead of one after another, so they open faster. Sending an invite also looks up the invited account while the email is being sent.
- The example stage cards on the marketing site (home page diagrams and showcases) and the clock in the phone mockup now work out the current time in your browser after the page loads, so they no longer risk a mismatch between the server-rendered page and what your browser shows.
- The password strength meter updates in the same render as you type instead of a beat later, a notification marked read elsewhere now shows as read straight away, and adding a listing resets the form and closes the section as soon as it is saved.
- The design service and pricing cards, the flow/kanban view switcher and the data tables on the address book, invites, requests, licences and team members screens now share one implementation each, so they look and behave the same everywhere.
- Email links built by the email button now open correctly in your mail app (the subject and message are encoded once, with spaces as %20, and empty fields are left out). The auth and marketing sites now share the same email button, copy button, password strength meter and requirement tick as the rest of the apps.
- Editing the app in development keeps your form state when a form component file changes: form schemas, status helpers and country helpers now live in their own files, and the chain and transaction flow views have proper names.
- Chain and transaction flow views, the kanban chain view, the cookie banner and the animated grid and floating-line backgrounds now declare everything their effects depend on, so they no longer risk working with stale data after a change.
- Declining an invite from the email link now asks you to confirm on a page first. Previously, simply opening the link (including email security scanners and link previews) declined the invite straight away.
- The cookie banner now stores your choice from your browser instead of through a server action, so nothing on the server can be triggered without a visit.
- The animated hyperspeed background compiles one shader per distortion style, and the liquid background disconnects its observers on cleanup.
- Animated components (animated grid, shiny button, animated beam and list, fade-in, glow line, aurora text, gradual spacing) load only the animation features they use, so pages that include them ship less JavaScript.
- The password field's show/hide button, the partner socials on the services page and a handful of other icon-only controls now announce what they do to screen readers.
- The sign-in, sign-up, one-time-code, password reset and email confirmation pages wrap their search-parameter handling in a loading boundary, so they render reliably during static builds.
- Several marketing and install-prompt components no longer redefine child components on every render, and shared form, chart, toggle group and dialog contexts no longer re-render everything under them on each update.
- The chain access list and the stage dependency picker use lookups instead of repeated searches, and the lists of invited parties are no longer re-sorted in place.
- The example QR card image declares its size so browsers fetch an appropriately sized file, and a failed diagram library load on the docs site now shows an error instead of staying on the loading message.

