No Results State
Show an honest no-results state so filtered or empty datasets explain themselves instead of making the page feel broken.
Introduction
Section titled “Introduction”A no-results state is not filler. It is part of the data-display contract. When a filter, search, or empty dataset removes visible rows, the page should explain what happened so users can recover confidently instead of assuming the app failed. In Wappler, that usually means conditional display driven by the current result size, not a hard-coded empty paragraph disconnected from the actual state.
Make empty states informative
Section titled “Make empty states informative”Blank space is not an explanation.
Distinguish empty data from filtered-out data
Section titled “Distinguish empty data from filtered-out data”A brand-new dataset with no records is different from a populated dataset that currently has no matches. The message should reflect that difference whenever possible.
Connect the message to the current controls
Section titled “Connect the message to the current controls”If a search term or filter caused the empty state, the page should make that relationship obvious. Otherwise users may not connect the blank result to their own current inputs.
Leave users a way out
Section titled “Leave users a way out”Resetting filters, clearing search, or navigating to create a first record are common next steps. An empty state is stronger when it points to a useful recovery path.
Next steps
Section titled “Next steps”No-results states pair naturally with text filters, checkbox filters, and total counts that explain the current view.