Get a grip
A personal work calendar for schoolwork: tests, homework and every other
assignment in one month view, with a running list of what is due next.
No accounts, no build step. It is three files – index.html, styles.css,
app.js – and two self-hosted typefaces. Tasks are saved in the browser's
own storage, so nothing about your coursework leaves your device unless you ask
it to: there is an optional server in api/ that keeps two devices in step and
feeds your calendar app, and the rest works with no server at all.
Two halves
The welcome hands over to a choice: Schoolwork or Money. The choice is
remembered for the session, so a reload puts you back where you were, but a
fresh launch asks again -- they are separate errands, and which one you are on
is not a setting.
Money runs on a surface of its own, dark in both themes, and the bar and the
footer come with it: a ledger is read at a glance at the top of the hour, the
figures want to glow rather than sit on paper, and a page that is dark in the
middle and warm at both ends reads as two apps stacked. Every contrast pair is
measured by tools/check-contrast.mjs and the ramp by the dataviz validator;
nothing in here was chosen by eye.
It opens with the time of day and your name, and then the dashboard, in the
order the questions actually get asked:
what have I got, where did it go, how fast is it going. The
statement, the setup and the month in detail are folded away underneath,
because nobody opens a money app to re-read last Tuesday.
The balance
The first figure on the page is what is in the account, and it is never a sum
of what has been imported -- a CSV reaching back ninety days does not know what
the account held ninety days ago. It comes from whoever actually knows, in this
order: the bank, through the connection; the statement's own closing balance
(mBank's Saldo końcowe footer, or the newest row's running balance),
rolled forward over anything dated after it; or nothing at all, said plainly.
Where it came from is always printed beside it, because "1 842,10 zł at the
bank" and "1 842,10 zł as at 28 September" are different claims.
Watching it is the only kind that is useful on a device you own: the figure is
compared with the one you were shown last time and the difference leads the
card. Nothing is polled -- a balance changes when a transaction arrives, and
that is already an event here.
Where it went, and how fast
Categories are drawn as bars in one hue, light to dark: the colour means
"bigger", which five different colours could not say. Every bar carries its own
figure, its share of the month and what it was last month, so the colour is
decoration and the number is the data; tap one and it opens to show who was
actually paid. Past a budget the bar leaves the ramp, and the words beside it
change too.
The rate card is four weeks of daily columns with a dashed line across them at
what a day may cost if the month is to fit inside the money coming in. The
window never reaches further back than the data goes: counting the days before
a statement starts as zeros would understate the rate by a quarter and turn an
overspending month into a comfortable one. Under it a verdict --
sustainable, tight, spending faster than it comes in, or not enough to
tell yet -- with a mark, a word and the arithmetic spelled out. Income is the
median of the complete months rather than the mean, so one transfer from a
grandparent does not become a monthly salary.
Money moved to your own account is not spending and is left out of both;
cash withdrawals are not, because the money has left the account and where it
went afterwards is not something a statement knows.
One transaction, up close
The biggest single payments in a month are usually the ones somebody else was
covering, and a day-to-day budget with a 620 zł concert ticket sitting in
it reads wrong all month. The rules cannot know which is which -- only the
person who spent it can -- so every row in every list of transactions opens,
and moving one out of the month is one tap.
Opening a category now lists the payments inside it, biggest first, rather
than a summary by payee: the one worth moving is a single row, and a total
hides it. Each row carries what it is and what it cost, and taps through to
the detail -- the amount, the dates, which side of the plan it is on, what it
was linked to if anything, and whether it came from mBank or from a CSV.
Two things can be changed there, and both are marked as yours so the automatic
passes leave them alone: move it outside the plan, which takes it off the
budget and out of the daily rate without deleting anything, and the
category, which from then on is ignored by the rules rather than
overwritten by them on the next import.
Money saved
Saved, here, means money that came in and did not go out again. It is not a
separate account and the app will not pretend it is one -- the proof is the
balance, which is why the two sit on the same page. The box adds the shape of
it: a figure for the run, a row per month, and which months kept something.
External money is on neither side of it.
The count starts at the month it was first asked for and runs from there.
Months before it are neither counted nor shown: what was spent before there
was a plan to spend it against is history, and a running total carrying it
forward is a running total nobody can read. The start month is remembered, so
the figure keeps growing rather than resetting every time the calendar turns
over.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
