Mappleton

How far can documentation be compressed without losing its meaning?

Lunch Money is a beautiful little independent app for personal finances: https://lunchmoney.app/

Won't do lots of complex stuff like investment strategy and estate planning, but covers all the essentials for a personal / family budget.

Gives you a good overview of your spending, net worth over time, and lots of charts and querying functionality. Made a big difference for me. Before I was spread across a bunch of Google sheets that I rarely updated.

Can you say more about how you organised and structured it? E.g. what practices, rules, and tools you used (And any chance you have a write-up online somewhere?) I've run a few groups like this and love learning how others approach it. Haven't found a great format for writing-based discussion that works as well as in-person / zoom calls.

OA here. Loved this piece as well, and it certainly got me thinking about a set of themes that led to this essay. Robin is an exceptional thinker in this space.

OA here. Thanks for the expanded etymology. I was using https://www.etymonline.com/word/folk as my source which goes into more historical detail. But didn't want to get too carried away in the opener on etymology.

Look promising, but just logged in and poked around and couldn't figure out how to get elements on the canvas. Or do much of anything. Some of the interaction design seems quite odd and difficult to use (eg. all the sidebar accordions open on hover rather than on click. And clicking on elements in the "insert" dropdown doesn't insert them.).

Apologies for jumping to critical feedback! Rough prototypes are rough for good reason ;) Glad to see more of these GUI builders popping up and think this is a worthwhile avenue to explore. But might be worth spending a bit of time looking at interface design best practices. And/or getting a designer to come advise on the project.