[FEATURE]: implementation of the screen expenses

Open
#37 1 comment 0 reactions 0 assignees View on GitHub

@4555jan is already working on this.

Since Mar 10, 2026.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
dart, flutter
Domain
frontend, mobile

Research direction

The issue describes implementing the add expense screens from the selected Figma design, but names no files, entry points, or tests. Start by locating the app's expense screens and reviewing the referenced design. Done means the add expense screens match the design; the issue gives no acceptance details, and its only comment is 241 days old.

Written by the indexing model from the issue text.

Description

enhancement
Feature and its Use Cases

i would like to implement add expense screens from the figma design that was selected
please assign this to me

Image
Additional Context

No response

Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
Dominant language
Dart
Stars
20
Forks
39
Avg merge
3d 12h
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from StabilityNexus/Zplit

All issues in StabilityNexus/Zplit

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.