Decide Data Models for Zplit App.

Open
#19 62 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
dart, flutter, sql
Domain
database, mobile

Research direction

Read the discussion on this issue, starting with the proposed payer-debtor-amount-total-currency structure and the offline data transfer idea. The issue does not identify code files, tests, or a settled model; first clarify the data model and synchronization requirements with maintainers. Done means the team has agreed on the model and its representation for transfer between devices.

Written by the indexing model from the issue text.

Description

discussion good first issue

This issue will track discussions related to finalizing the data models for the application. As this is a purely offline application, we will use a SQL Database offline to store all data. To transfer this data between devices, the currently ideated architecture will involve encoding any data to transferrable strings and then decoding on the receiving device.

One Data Structure proposed by Bruno is:
Payer-Debtor-Amount-Total-Currency-Description-Category-Location(optional)-Date and Time

Example for a $100 Transaction paid by X and split between X,Y and Z:
If X creates a record for this, the following transactions will be created by X and then later synchronised with Y's device:
X-Y-33-100-USD-Dinner-XYTrip-20S 40E-2025-12-03 18:00
X-Z-33-100-USD-Dinner-XYTrip-20S 40E-2025-12-03 18:00

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.