The screens every mobile app needs and most teams build last. A grouped settings screen, a search screen with filtered results, and an empty state that tells users what fills it. Copy any design and paste it into Bolt, Lovable, or Replit. Each one is a single HTML file.
Why do settings and empty states matter?
They are where new users get stuck. An empty list with one line of grey text is a common place to lose someone before they see what the product does, and a settings screen nobody can navigate generates support requests.
What should an app settings screen include?
The account at the top, then short groups named for what a user is trying to do. Showing the current value on each row saves a tap, since most visits to settings are checks and not changes.
How should search results be organized?
Split by type when you search across more than one kind of thing. A single list mixing people, files, and messages makes the user do the sorting, and most give up and search again.
Do these work for iOS and Android?
Yes. Every screen is designed at 375 by 812 and works as a reference for any mobile stack, including React Native, Flutter, SwiftUI, or a progressive web app.