Skip to content

Issue -12: Reusable Status / Notification Card Widget (Flutter Implementation) #115

@Surya-Raghuram

Description

@Surya-Raghuram

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


Overview

NomMetric needs a reusable Status / Notification Card widget to display important information or alerts on the Home screen.

This widget will be used to show things like:

  • Important announcements

  • Mess-related notices

  • Warnings or reminders

  • General status updates

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

This is a UI-only issue. No backend, Firebase, or API integration is required.

What You Need to Implement:

Status / Notification Card Widget

  • Create a new file inside lib/widgets/

  • File naming convention: statusCard_.dart_(example: statusCard_surya.dart)_

This avoids merge conflicts when multiple contributors submit PRs.

  • DO NOT modify main.dart or any existing screensI will integrate and test the widget myself.

Widget Requirements:

The widget should visually represent an important notification and include:

  • Reusable Icon (passed as a parameter)

  • Title text (e.g., “Important Update”)

  • Short description / message

  • Optional:

    • Status color (success / warning / error)

    • Action button (e.g., “View”, “Dismiss”)

All data should be passed via constructor — no hardcoded content as this widget should be reusable at multiple places with different content each time.

Implementation Guidelines:

  • Use StatelessWidget (preferred)

  • Clean, minimal UI

  • Fully reusable

  • No navigation logic

  • No backend / Firebase / API calls

  • Use only standard Flutter widgets:

    • Container, Card, Text, Icon, Row, Column, etc.

Submission Requirements

  1. Add your widget inside lib/widgets/ using the naming convention

  2. Do not edit existing widgets or screens

  3. Include a screenshot of the widget in the PR description

  4. Open a Pull Request

  5. PR description must start with:

Issue:#12**

Points and Completion Rules

  • Each accepted PR: 30 points

  • Multiple PRs may be merged if designs are useful

  • Issue will be closed after selected PRs are merged

Metadata

Metadata

Assignees

No one assigned

    Labels

    FrontendFor issues involving only frontend workPoints: 30good first issueGood for newcomersopen-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