iiitl / iiitl/Tap2Eat

[feat]: Add "No Order History" empty state on History page

Open
#7 8 comments 0 reactions 0 assignees View on GitHub
easy feat ui-ux
Dominant language
Kotlin
Stars
0
Forks
7
PR merge metrics
No merged PRs in 30d

Description

When a user has no past orders, `History.kt` displays a completely blank screen. There is no message, no illustration, and no guidance on what to do next. For a first-time user or someone who has never placed an order, a blank screen is confusing and feels like a broken experience.

A well-designed empty state turns a dead end into an opportunity — it reassures the user that the app is working correctly, explains why nothing is showing, and gives them a clear next step to take.

## Current Behavior

When `History.kt` loads and there are no past orders to display, the screen is entirely blank. No message, no graphic, no call to action.

## Expected Behavior

When there are no past orders, a friendly empty state is displayed in the center of the screen containing:
- An illustration or icon representing an empty order history.
- A short, friendly message such as *"No orders yet!"* with a subtitle like *"Your past orders will appear here."*
- A button that navigates the user back to the menu so they can place their first order.

The empty state is hidden as soon as at least one order exists.

## Acceptance Criteria

- [ ] When the order history is empty, a friendly empty state UI is displayed in the center of the screen.
- [ ] Screenshots of the empty state and the normal order history view are both attached to the PR.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading History.kt and tracing how the History page distinguishes an empty order list from the normal order history view. Check the existing navigation path back to the menu and available UI assets or patterns. Done means the centered empty state appears only with no orders, includes the requested guidance and menu action, and both empty and populated views are shown in PR screenshots.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
mobile
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.