Margaret-Petersen / Margaret-Petersen/uber-eats-clone-using-react-native
Show “No Restaurant/Store Available” Message When Category Has No Content
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
Yes. Currently, when a user opens a category that has no restaurants or stores listed, the page remains blank, giving no feedback or context. This can confuse users, making them think the page is broken or still loading.
Describe the solution you'd like
A friendly message such as “No Restaurant/Store Available” should be displayed when there’s no content for a selected category. This will inform users that the category exists, but currently has no available listings.
Describe alternatives you've considered
Users may try reloading the page or navigating away, thinking it’s an error, but this is not user-friendly or informative.
Additional context
Adding this message will improve the overall user experience by providing clarity and ensuring that the interface communicates the state of the content effectively. Optionally, a small icon or illustration could be included to enhance the visual appeal.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the React Native screen that renders restaurant or store listings for a selected category, then inspect how empty content is currently handled. Add an empty-state message for categories with no listings, optionally with the described visual treatment. Done means the message appears instead of a blank page while populated categories continue to show their listings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- frontend, mobile
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100