Rearrange In-App Notifications Placement on Home Page Controls

Open

#1,407 opened on Apr 13, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 56/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: javascript, react-native
Domain: design, frontend, mobile

Research direction

Start by reproducing the notification placement on the home page of the Enatega Multivendor Rider/Restaurant App on iOS and Android, then locate the controls for new, processing, and delivered orders. Done means those notifications appear at the top-right of the associated control text without disrupting the home-page layout.

Written by the indexing model from the issue text.

Description

Describe the bug
In the Enatega Multivendor Rider/Restaurant App, the in-app notifications related to new orders, processing, and delivered statuses are currently positioned on the left side of the controls on the home page. This placement can cause confusion and disrupt the flow of information for users. To enhance clarity and usability, it's proposed to relocate these notifications to the top-right part of the text associated with each control.

To Reproduce

Open the Enatega Multivendor Rider/Restaurant App.
Navigate to the home page.
Observe the placement of in-app notifications related to new orders, processing, and delivered statuses.
Note that these notifications are currently positioned on the left side of the controls.
Expected behavior
In the Enatega Multivendor Rider/Restaurant App, in-app notifications related to new orders, processing, and delivered statuses should be relocated to the top-right part of the text associated with each control on the home page. This adjustment will enhance clarity and ensure a more intuitive layout for users.

Screenshots

screen-20240312-135108.mp4
Smartphone (please complete the following information):

Device: IOS & Android
Additional context
Add any other context about the problem here.

Dominant language: JavaScript
Stars: 0
Forks: 0
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing 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.