A budgetting/finance app
  • Swift 94.4%
  • Makefile 5.6%
Find a file
2026-10-31 01:00:12 -06:00
Packages/waterline-core feat: initialize modules under waterline-core as part of #1 2026-10-31 01:00:12 -06:00
waterline (init) 2026-10-30 10:28:46 -06:00
waterline.xcodeproj feat, dependency: Add GRDB, add WaterlineCore as deps to root project, 2026-10-30 23:54:12 -06:00
waterlineTests (init) 2026-10-30 10:28:46 -06:00
waterlineUITests (init) 2026-10-30 10:28:46 -06:00
.gitignore (init) 2026-10-30 10:28:46 -06:00
Makefile feat, dependency: Add GRDB, add WaterlineCore as deps to root project, 2026-10-30 23:54:12 -06:00
README.md (feat): Add readme 2026-10-30 22:55:54 -06:00

Waterline Design Document

What is it?

This is coming from a budgetting app that I used a few years ago but fell to becoming a subscription service. The way that the app worked is that you provided all your recurring income and expenses ("I get paid X amount on the 1st and 15th of the month", "I get paid Y amount every Friday", "I have these patreon subscriptions that bill on X day of the month for Y value"). The app takes all of these values and generates a daily expense number (or your "Waterline" for branding purposes). Users log each time they spend money over the course of the day which detracts from their waterline, this number can go negative. Any unspent balance from day N rolls to day N+1 and so on. For large expenses they should be able to be broken up across multiple days (distributing a $300 purchase across the next 7 days rather than all at once).

Design Goals

  1. This app should be local-first, working entirely without an internet connection
  2. When connected to the internet, a user should be able to point at a remote server URL (we can have defaults but a self-hosted option is also good) that syncs when reconnected

Building / Deploying

tbd