Live data from Hacker News

Ask HN: What Are You Working On? (Nov 2025)

news.ycombinator.com

641–650 of 1001 posts

Re: Ask HN: What Are You Working On? (Nov 2025)

#642
Dog enrichment calendar - I have a lot of different types of treats, toys and activities that I'd like to do with my dog but I fell into routines and just gave him two or three toys and treats on repeat. So I'm building an app where I'd be able to configure an inventory of all the treats and toys I own and the app would remind me to use a new toy or treat every day, to minimize repetition. You'll also be reminded ahead of time for toys and treats that require preparation

Re: Ask HN: What Are You Working On? (Nov 2025)

#643
I’m building RootCX (https://rootcx.com). A customer "operating system" replacing dozens of SaaS tools.

As a second-time founder, I've watched the SaaS boom create an ocean of best-of-breed tools. Each solving one slice of the problem. One solving it end-to-end.

Now every company runs on a patchwork of apps, APIs, and workflow hacks just to keep customer context alive. It's insane how normalized that's become.

RootCX starts from the opposite premise: the customer is the core, not the app. Everything: CRM, support, billing, workflows, AI, ... plugs into one shared customer base. Less juggling tools, more actually running the business.

Re: Ask HN: What Are You Working On? (Nov 2025)

#644
Building an MCP Gateway: https://www.gatana.ai/

Idea came from one of my clients, where they wanted to use AI agents throughout the organization but at that moment there was no centralized governance or security concepts. This pulls everything at one place and tries to solve the security concept with per-user credentials, which can be provided out-of-band through the MCP protocol (generated a one-time link end-user can use to sign in to the underlying MCP server with OAuth or provide API key)

Re: Ask HN: What Are You Working On? (Nov 2025)

#645
I built a wireless highlights & annotations export service for Kobo e-readers earlier this year [1]. Had a free tier limited to 20 exports but wasn't sure how to price it beyond that, so I just left it. Recently a user reached out asking if I'd settled on pricing and how they could pay for unlimited exports! That jolted me into coming up with a price, and now I'm finally getting Stripe integrated :)

[1] - https://highlights.email

Re: Ask HN: What Are You Working On? (Nov 2025)

#646
https://unheard.fm

I was tired of repeat, sponsored, and "safe" music suggestions from Spotify, so I built a discovery engine that puts the control back in the user's hands.

The core idea is simple: You define a "Discovery Model" with explicit constraints (specific genres, release years, track popularity, etc.). The app then uses this blueprint to source tracks.

The results are fresh for two reasons:

- "Known" Track filtering: Excludes all songs saved in your library and recent listening history.

- Active Curation: Uses your custom model, not a vague, opaque algorithm.

It’s built with a local-first mentality and a focus on privacy. No black-box AI "vibe" mixes, just pure, objective discovery based on your criteria.

Hope ya'll find some new gems!

Re: Ask HN: What Are You Working On? (Nov 2025)

#647
I am building Mizu, a lightweight web framework for Go that aims to keep things simple and Go-first. Everything is written in plain Go with no hidden abstractions, and you can start with a single file then grow into a full project without changing your coding style. The name means "water" in Japanese; the framework tries to flow with your code rather than force its own patterns.

Docs: https://docs.go-mizu.dev/overview/intro

Re: Ask HN: What Are You Working On? (Nov 2025)

#649
As a means to learn about both WebAssembly and Rust, I started writing a WebAssembly binary decoder (i.e. a parser for `.wasm` files) from scratch.

Recently it hit v2.0 spec conformance. 3.0 is next on the roadmap. (I'm executing it against the upstream spec test suite.)

My aim is probably not for it to become a highly-performant decoder for use in production environments, but rather one that can be used for educational purposes and/or debugging issues with existing modules. That's why I decided not to offer a streaming API, and why I'll be focusing on things like good errors, good code docs etc.

https://github.com/agis/wadec

P.S. I'm new to the language so any feedback is more than welcome.

Post reply on HN