# Building LogHue based on what actually annoys me

```yaml
url: "https://forg.to/articles/building-loghue-based-on-what-actually-annoys-me"
title: "Building LogHue based on what actually annoys me"
excerpt: "I shipped three updates to LogHue over the last two weeks: notes folders, public note sharing, and more flexible tasks. None of them are big on their own. But together they say something about how I'm building this product now, and it's worth writing…"
author: "Abdulroqib Oladipo"
author_url: "https://forg.to/@abdulroqib"
published: 2026-09-25
updated: 2026-10-18
read_time_minutes: 4
cover_image: "https://res.cloudinary.com/dxkpmcrel/image/upload/v1790350526/forg/articles/nkpo1johofssnlfnnuvb.png"
```

## TL;DR

I shipped three updates to LogHue over the last two weeks: notes folders, public note sharing, and more flexible tasks. None of them are big on their own. But together they say something about how I'm building this product now, and it's worth writing…

## Content

I shipped three updates to LogHue over the last two weeks: notes folders, public note sharing, and more flexible tasks. None of them are big on their own. But together they say something about how I'm building this product now, and it's worth writing down.

## **The flat list problem**

Notes in LogHue used to just sit in one long list. I don't scroll through it, I search. But that only works when you know exactly what you're looking for. Glance at the list and it just looks unorganized, nothing tells you at a glance where anything is or what it belongs with.

The fix is straightforward: folders. Collapsible, so you can tuck away what you're not using. Anything you don't file stays at the top level, so nothing forces you to reorganize your whole workflow just to use the feature.

It's not a clever feature. It's just something that was genuinely missing.

## **Sharing without overthinking it**

The second update is public note sharing. Turn it on for a note, get a link, share it. Turn it off, the link stops working and only you can see it.

I went back and forth on how complicated to make this. Access controls, expiring links, view counts. While working through it, I was told the real gap in my plan was that the link never changed once it existed. I didn't think it mattered at first. Then Claude explained properly: without a way to regenerate it, an old link stays tied to the note forever. So say you share a note with someone, later decide they shouldn't have access anymore, and turn sharing off. Then you forget you ever shared it, or you update the note with something you don't want that person to see, and turn sharing back on. The same old link still works. They can still open it.

That's the kind of gap that doesn't show up until someone's data is already exposed. So I added a regenerate button. The old link doesn't die automatically, some people will genuinely want it to keep working, but now you get the choice: regenerate it and the old one stops working, or leave it as is.

Past that, I kept the rest simple: off by default, and the whole decision lives with the person who wrote the note. If I add more later, it'll be because people actually ask for it or I actually need it myself, not because I assumed they would.

## **Tasks that reflect how time actually works**

The third change took the longest to get right. Tasks in LogHue only ever had a deadline, a single point in time. That's fine for a to-do item. It's not fine if you want your calendar to show you when you're actually busy versus when you're free.

So, tasks can now have a start time and an end time, not just a due point. And for recurring tasks, you can choose which days reminders actually fire. Every day. Weekdays only. Weekends. Or you pick the exact days, like every Monday and Thursday.

I'd shelved this idea months ago because I assumed nobody needed it. Feedback from someone who lives in their calendar made it obvious I was wrong. The calendar is a lot more useful now that it reflects real blocks of time instead of just a scattering of deadlines.

## **Why this matters more than the features themselves**

I use LogHue heavily myself, and it's no longer just me. Every one of these three updates still came from something that genuinely got in my way while using my own product, not from guessing what a hypothetical user might want.

It's a slower way to build. But I trust the output more, because I know exactly why each piece exists.

If you're using @loghue, I want to hear what's still getting in your way. That's the next thing I'll fix.

loghue.com

## Links

- Article: https://forg.to/articles/building-loghue-based-on-what-actually-annoys-me
- Author: https://forg.to/@abdulroqib
- Forg: https://forg.to

---
Published on [Forg](https://forg.to), a social network for people who create and ship on the internet.
_HTML version: https://forg.to/articles/building-loghue-based-on-what-actually-annoys-me_