Must specify from how far customer can order form a restaurant. We see a zone but I do not think it is functional in Enatega Multivendor.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- javascript, react-native
- Domain
- mobile
Research direction
Start by reproducing the ordering flow in the application or website and inspect how the restaurant zone feature affects restaurant listings and order eligibility. The work is done when the maximum order distance is defined, enforced by the zone feature, and made clear to customers.
Written by the indexing model from the issue text.
Description
Issue: Must specify from how far customer can order form a restaurant. We see a zone but I do not think it is functional.
Description:
There is a lack of clarity regarding the maximum distance from which a customer can place an order from a restaurant. Although there is a zone feature, it's unclear if it functions or how far customers can order from a restaurant.
Impact:
User Uncertainty: Users may feel unsure about how far they can place an order from a restaurant based on their location.
Ordering Efficiency: The absence of a clear maximum order distance may lead to inefficiencies in the ordering process.
Steps to Reproduce:
Access the application or website.
Explore the restaurant listings to place an order.
Observe that there is no clear information about the maximum distance from which a customer can place an order.
Expected Resolution:
You should define and communicate the maximum order distance for customer orders. If a zone feature is in place, ensure that it functions effectively and makes it easy for users to determine if their location falls within the permissible distance for ordering from a restaurant. This clarity will improve the user experience and help customers place orders more efficiently.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from raymondjames090/uber-eats-app-clone-using-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2069 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2003 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raymondjames090/uber-eats-app-clone-using-react-native#2002 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#1979 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
raymondjames090/uber-eats-app-clone-using-react-native#1978 ·
All issues in raymondjames090/uber-eats-app-clone-using-react-native
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100