HN user

kasparnoor

64 karma
Posts3
Comments20
View on HN

I think the symptom is a self repeating loop that gets worse. they watch the short form content, which makes them more and more addicted to it. So breaking out of it, may get some of that attention span back. I already feel mine starting to return a bit. Been reading more books lately and just feeling a bit happier

That's an interesting angle on the parental control, by the way.

1) it's already been live for about a month, so definetly not a week long project 2) I use the app myself every day to reduce screentime so I'm highly motivated to keep the app up to date. When the platforms change DOM elements, or try to distrupt Dull from working I am also disrupted, so I work quickly to fix all bugs 3) There is a 7 day free trial for anyone to test out if it's a "scam". It's not.

A Safari extension could handle some of it, but Dull also does usage tracking, time limits, quiet hours, and grayscale mode which all need to live at the app level. The filtering itself could be an extension, but the broader goal is reducing how much time you spend there, not just hiding elements. For example we added a feature in today's update that let's you choose what is the intention of opening app. Like if intention is to open DMs then you open just to DMs. Another way of reducing distractions.

Fair question. The honest answer is I don't know if Instagram or YouTube will try to shut this down. They haven't so far, but that doesn't mean they won't. They can try to come after me:) But seems like they are the ones losing in court currently for making their own apps so addicting. Wouldn't be a good look to come after such apps.

The subscription model exists partly because of this — if it stops working, you stop paying. The lifetime option is a bet on my part that I can keep maintaining it. If I can't, that's on me. But since this is an app I use daily myself I am extremely motivated to fix every bug and keep the app excellent and all filters working.

Hi HN, I built ShipNative to make “clone, configure, ship” realistic for Expo/React Native projects.

The focus is on a clean TypeScript base, sensible defaults, and docs that don’t assume you already know the exact setup steps. It aims to cover the common production essentials (auth, payments, analytics/error wiring points) without turning into an over-opinionated framework.

I’d love feedback on:

What you expect a real-world RN starter to include (or avoid)

Where most boilerplates feel bloated or fragile

Whether the docs are clear enough for a first-time setup

Happy to answer technical questions and explain trade-offs.