Skip to content

Issue 6-Bottom Navigation Skeleton (Flutter Implementation) #43

@Surya-Raghuram

Description

@Surya-Raghuram

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


Overview

NomMetric needs a Bottom Navigation bar in the home screen to switch between core sections of the app.
In this issue, you will implement a reusable bottom navigation widget that can later be integrated into the main app flow.

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

Bottom Navigation Widget

  • Create a new file inside lib/widgets/
  • File naming convention: bottomNav_<your_name>.dart (e.g., bottomNav_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 navigation section should have 3 tabs:

  • Home
  • Menu
  • Profile

Each tab can navigate to a placeholder screen

Each tab should switch the visible widget/content when tapped, no real data is required.


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:#6

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