Skip to content

Issue 5: Meal Card Widget UI (Flutter Implementation) #35

@Surya-Raghuram

Description

@Surya-Raghuram

Type: Open-for-All (Flutter Development)
Points: 20


Overview

NomMetric needs a Meal Card Widget to display individual meals in the app.
In this issue, you will implement a reusable Flutter widget that can later be used in the Meal screen or lists.

This issue is open-for-all — multiple contributors can submit PRs, and the best designs may be merged into the project.

This is a UI-only issue. No backend integration or Firebase required. Focus on clean, reusable Flutter code.


What You Need to Implement

Meal Card Widget

  • Create a new file inside lib/widgets/
  • File naming convention: mealCard_<your_name>.dart (e.g., mealCard_surya.dart)

    This helps avoid merge conflicts when multiple contributors submit PRs.

  • DO NOT implement the widget in main.dart, it will raise a merge conflict, i will implement these widgets and test them individually.

The widget should have the following placeholder structure:

  • Meal name (Text widget)
  • Meal time / type (Breakfast / Lunch / Dinner)
  • Optional placeholder image or icon
  • Minimal styling (card, padding, border radius)

The goal is to create a modular widget that can be reused in the Meal list screen later.


Implementation Guidelines

  • Use StatelessWidget or StatefulWidget if needed
  • Keep the UI clean and minimal
  • No real data is required; placeholders are fine
  • Use only standard Flutter widgets (Container, Card, Text, Image/Icon, Column, Row, etc.)
  • Do not implement any backend, Firebase, or API logic yet

Submission Requirements

  1. Add your widget inside lib/widgets/ using the file naming convention above.
  2. Include a screenshot of your widget in the PR description (or attach it in the PR) to help visualize your design.
  3. Do not edit main.dart, I will implement and check the widget myself.
  4. Open a Pull Request
  5. PR description must start with:
    Issue:#5

Points and Completion Rules

  • Each successful PR merged for this issue: 20 points
  • Multiple PRs may be merged if designs are accepted
  • The issue will be closed after all selected PRs are merged

Metadata

Metadata

Assignees

No one assigned

    Labels

    Points: 20open-for-allAny one can work on it without getting assigned, every PR can merge

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions