Goal: help someone find the right task and understand it quickly.
A list is useful for scanning titles and short details. A table makes comparison easier. A detail view shows one record, while a form lets an authorized user enter information. Available view settings depend on the selected view and your deployed version.
In Build, select the view you want to improve. Check its title, selected table, and the fields used for its main and supporting text. A correct layout with the wrong binding can still show the wrong information.
Try a clearer title or choose which columns a table displays. Inspect View after saving. Confirm that the same record is still recognizable and that useful fields have not disappeared.
Review the app's navigation too. A menu label should tell a user what they will find. Removing a menu entry does not revoke permission to its data.
Use Appearance for the maintained theme, light/dark mode, and supported overrides. Prefer a few consistent choices over styling each screen differently. Check text contrast, long names, empty states, and narrow screens.
A frontend selects an interface within a project. The current frontend configuration reuses shared pages; it does not yet provide independently published layouts or destinations. Editing a shared page can affect other frontend definitions using it.
Next: Control access →