Features
Feature requests across all Halfmoon products
Spacing as TokensElleOur engineers work in tokens. Handing them 12px when the token is space-2 means someone translates it by hand, and last sprint someone got it wrong.Support Team Handing over a number that someone then has to translate back into a token is a good way to put it, Elle. We're on it.
BrambleUnder ReviewNotes in Our LanguageYunOur engineering team is in Poland and reads English fine, but the headings and the boilerplate would be better in Polish. The measurements do not need translating, obviously.Support Team The distinction you have drawn is the useful part: the scaffolding is ours to translate, the content is yours and should be left alone. That makes this much smaller than it first sounds. Looking at it.BrambleUnder ReviewSettle Without LeavingJosieKettle tells me I owe Nadia £42.30 and then I go to my bank, type it in and come back to mark it paid. Three apps for one number.Support Team Reasonable, and it is the most-asked thing we have not committed to. Being straight about why we are still thinking: handling money means regulation, and half-doing that is worse than not doing it. We are looking at handing off to whatever people already use to pay each other, so the amount and the reference are filled in and the marking-as-paid happens on the way back.
KettleUnder ReviewReview a Whole BranchAnonymousI want one review across every commit on my branch before I open the pull request, not a separate one per file as I go.Support Team Sensible, and it is a different job from the per-file review rather than a bigger one: things worth saying about a branch are usually about how the changes fit together. Thinking it through before we commit to it.
CragUnder ReviewSplit by ItemNadiaFour of us ate. One of us had three courses and most of two bottles of wine. Splitting evenly isn't the answer, and doing it by hand rather defeats the point of the app.Support Team That's exactly the case where an even split stops being fair. In progress now.KettleIn ProgressExplain the FindingMeeraSome findings I understand at a glance. Some I read three times and still cannot tell whether it matters. A sentence on why it was flagged would settle most of them.Support Team In progress. Each finding gets a short why, and where the reasoning depends on something elsewhere in the file it will link to that line rather than describing it.CragIn ProgressA Running TotalFridaHalfway through a week away I want to know what the trip has cost so far, not what I owe. Those are different numbers and only one of them is on screen.Support Team They are different numbers and you are right that only one is shown. Planned: the group gets a spend-so-far figure alongside the balances, with a per-person breakdown behind it.KettlePlannedWarn Before LowFfionI dig bait on a spring low and I keep missing it by an hour because I have to remember to check. A notification an hour before low water at my station would solve it entirely.Support Team Having to remember to check an app that already knows the answer is the app's fault. In progress.
TidelineIn ProgressSwell with TidesJonasTides tell me when I can get out. Swell tells me whether it's worth it. Both in the menu bar and I'd stop checking two apps every morning.Support Team This has come up a few times now and it fits what Tideline is for, so we're planning it rather than filing it. We'll post here when it moves.TidelinePlannedOur Rules, Not YoursRaviWe have a written style guide our team actually follows. Crag doesn't know about it, so it flags things we've decided are fine and misses the things we care about. A file in the repo it reads would do it.Support Team Planned, and it is the right shape: a file in the repo, reviewed like any other file, rather than settings in an account somebody left the company with. Rules will be able to loosen as well as tighten, because half of what a team writes down is which warnings not to bother with.CragPlannedLink Back to FramesAndersThe notes describe a screen but there is no way back to it. Engineers paste the text into a ticket and then spend ten minutes hunting for the frame it came from.Support Team Planned. Each section carries a deep link to the exact frame, and the links survive being pasted into Linear and GitHub, which is where they need to work rather than where they are generated.BramblePlannedWater TemperatureIwanSwell tells me whether it's worth going. Water temperature tells me what I need to wear, and at the moment that's a third site every morning.Support Team Planned. It sits naturally beside the swell work rather than being a separate job, so it should follow shortly after it. Worth saying now: buoy coverage is thinner than tide station coverage, so some places will get a nearby reading rather than a local one, and it will say which buoy and how far away rather than pretending.TidelinePlannedRecurring 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.KettleDeclinedAuto-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.CragDeclinedGenerate 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.BrambleDeclinedUnused ComponentsSofiaabout 200 components in our library and no idea which ones are deadSupport Team Knowing what's safe to delete is the hard half of keeping a library tidy. Looking into it.BrambleCompletedSee Who Owes WhatTomasSix of us, four weeks, ninety-odd expenses. The list is accurate and completely unreadable. I want one line per person and nothing else.Support Team Accurate and unreadable is a fair description of that screen. Working on it.KettleCompletedOnly the DiffLenaOn an old file it reviews the whole thing and I get forty findings about code I didn't touch. I want to know about the twelve lines I changed.Support Team Being told about a decade of somebody else's decisions when you fixed a typo is a good way to get an extension uninstalled. Agreed.CragCompleted
BrambleUnder ReviewNotes in Our LanguageYunOur engineering team is in Poland and reads English fine, but the headings and the boilerplate would be better in Polish. The measurements do not need translating, obviously.Support Team The distinction you have drawn is the useful part: the scaffolding is ours to translate, the content is yours and should be left alone. That makes this much smaller than it first sounds. Looking at it.BrambleUnder ReviewSettle Without LeavingJosieKettle tells me I owe Nadia £42.30 and then I go to my bank, type it in and come back to mark it paid. Three apps for one number.Support Team Reasonable, and it is the most-asked thing we have not committed to. Being straight about why we are still thinking: handling money means regulation, and half-doing that is worse than not doing it. We are looking at handing off to whatever people already use to pay each other, so the amount and the reference are filled in and the marking-as-paid happens on the way back.KettleUnder ReviewReview a Whole BranchAnonymousI want one review across every commit on my branch before I open the pull request, not a separate one per file as I go.Support Team Sensible, and it is a different job from the per-file review rather than a bigger one: things worth saying about a branch are usually about how the changes fit together. Thinking it through before we commit to it.CragUnder ReviewSplit by ItemNadiaFour of us ate. One of us had three courses and most of two bottles of wine. Splitting evenly isn't the answer, and doing it by hand rather defeats the point of the app.Support Team That's exactly the case where an even split stops being fair. In progress now.KettleIn ProgressExplain the FindingMeeraSome findings I understand at a glance. Some I read three times and still cannot tell whether it matters. A sentence on why it was flagged would settle most of them.Support Team In progress. Each finding gets a short why, and where the reasoning depends on something elsewhere in the file it will link to that line rather than describing it.CragIn ProgressA Running TotalFridaHalfway through a week away I want to know what the trip has cost so far, not what I owe. Those are different numbers and only one of them is on screen.Support Team They are different numbers and you are right that only one is shown. Planned: the group gets a spend-so-far figure alongside the balances, with a per-person breakdown behind it.KettlePlannedWarn Before LowFfionI dig bait on a spring low and I keep missing it by an hour because I have to remember to check. A notification an hour before low water at my station would solve it entirely.Support Team Having to remember to check an app that already knows the answer is the app's fault. In progress.TidelineIn ProgressSwell with TidesJonasTides tell me when I can get out. Swell tells me whether it's worth it. Both in the menu bar and I'd stop checking two apps every morning.Support Team This has come up a few times now and it fits what Tideline is for, so we're planning it rather than filing it. We'll post here when it moves.TidelinePlannedOur Rules, Not YoursRaviWe have a written style guide our team actually follows. Crag doesn't know about it, so it flags things we've decided are fine and misses the things we care about. A file in the repo it reads would do it.Support Team Planned, and it is the right shape: a file in the repo, reviewed like any other file, rather than settings in an account somebody left the company with. Rules will be able to loosen as well as tighten, because half of what a team writes down is which warnings not to bother with.CragPlannedLink Back to FramesAndersThe notes describe a screen but there is no way back to it. Engineers paste the text into a ticket and then spend ten minutes hunting for the frame it came from.Support Team Planned. Each section carries a deep link to the exact frame, and the links survive being pasted into Linear and GitHub, which is where they need to work rather than where they are generated.BramblePlannedWater TemperatureIwanSwell tells me whether it's worth going. Water temperature tells me what I need to wear, and at the moment that's a third site every morning.Support Team Planned. It sits naturally beside the swell work rather than being a separate job, so it should follow shortly after it. Worth saying now: buoy coverage is thinner than tide station coverage, so some places will get a nearby reading rather than a local one, and it will say which buoy and how far away rather than pretending.TidelinePlannedRecurring 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.KettleDeclinedAuto-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.CragDeclinedGenerate 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.BrambleDeclinedUnused ComponentsSofiaabout 200 components in our library and no idea which ones are deadSupport Team Knowing what's safe to delete is the hard half of keeping a library tidy. Looking into it.BrambleCompletedSee Who Owes WhatTomasSix of us, four weeks, ninety-odd expenses. The list is accurate and completely unreadable. I want one line per person and nothing else.Support Team Accurate and unreadable is a fair description of that screen. Working on it.KettleCompletedOnly the DiffLenaOn an old file it reviews the whole thing and I get forty findings about code I didn't touch. I want to know about the twelve lines I changed.Support Team Being told about a decade of somebody else's decisions when you fixed a typo is a good way to get an extension uninstalled. Agreed.CragCompleted