Features
Feature requests across all Halfmoon products
Recurring Household BillsOwenMy flatmate and I use Kettle for holidays and it's the only thing we've both stuck with. We'd use it all year if it could carry rent, broadband and the energy bill on a repeat.Support Team We've given this a proper look and the answer is no, so here it is with the reasoning. Kettle is built around a group that forms, spends and settles up. Everything in it assumes an ending: the balances resolve, somebody pays, the group closes. Household bills never do that. A total that never settles needs different maths, different reminders and a different idea of what finished means, and adding it would make the holiday case worse to serve a case we're not good at. One thing that works better than it sounds: a flat group you settle at the end of each month. Same numbers, and it keeps everyone square as you go.
KettleAuto-Push FixesAnonymousif crag can see the problem it may as well fix it and commitSupport Team We're going to say no, and it's worth saying why rather than leaving it open. Crag reviews. The moment it also writes to your branch, the thing reviewing the code and the thing changing it are the same thing, and the review stops being independent. That's the whole value of it. It'll keep offering the fix as a diff you apply in one click. Same number of keystrokes, no conflict of interest.
CragGenerate the CodeAnonymousBramble already knows the spacing, the colours and the hierarchy. Give me the React component and skip the handover entirely.Support Team We have prototyped this twice and we are not going to ship it. Here is the honest reason rather than a vague one. A design file knows what something looks like. It does not know what the component is called in your codebase, which of your primitives it should be built from, what it does when the data is empty, or which of those forty pixel values is a real decision and which is a nudge somebody made at five o'clock. The code that comes out is plausible, ignores your design system, and takes longer to correct than to write. Both of our prototypes were faster to throw away. What we are doing instead is the part that is actually true: spacing and colour handed over as your tokens rather than as numbers, so the translation step that goes wrong is gone. That is in progress now.
Bramble
KettleAuto-Push FixesAnonymousif crag can see the problem it may as well fix it and commitSupport Team We're going to say no, and it's worth saying why rather than leaving it open. Crag reviews. The moment it also writes to your branch, the thing reviewing the code and the thing changing it are the same thing, and the review stops being independent. That's the whole value of it. It'll keep offering the fix as a diff you apply in one click. Same number of keystrokes, no conflict of interest.CragGenerate the CodeAnonymousBramble already knows the spacing, the colours and the hierarchy. Give me the React component and skip the handover entirely.Support Team We have prototyped this twice and we are not going to ship it. Here is the honest reason rather than a vague one. A design file knows what something looks like. It does not know what the component is called in your codebase, which of your primitives it should be built from, what it does when the data is empty, or which of those forty pixel values is a real decision and which is a nudge somebody made at five o'clock. The code that comes out is plausible, ignores your design system, and takes longer to correct than to write. Both of our prototypes were faster to throw away. What we are doing instead is the part that is actually true: spacing and colour handed over as your tokens rather than as numbers, so the translation step that goes wrong is gone. That is in progress now.Bramble