Show HN: Datapuddle, a native macOS DuckDB client that doesn't page results
datapuddle.app
I have a soft spot for pretty/polished macOS apps. It bugged me there wasn't one for DuckDB. TablePlus is my favorite multi-db client, I'm in it daily, but the DuckDB support is thin.
The other thing was paging. Every client gives you the first N rows and a "load more" button. I didn't want that. DuckDB is the only place on my local machine where I actually am dealing, slicing/dicing, and perusing large datasets.
So I built Datapuddle to fully embrace DuckDB for in a macOS friendly way :)
The grid:
- Whole result is in it. Not the first page. Rows never become objects, cells get read out of DuckDB's columnar chunks at draw time and drawn with Core Text. Memory is flat at 40 rows or 41 million. Row 41,000,000 costs what row 40 costs.
- Numbers, on 20M rows x 30 cols out of an 11GB file: 119 fps average on a sustained fling, min-instantaneous 52-60, 2.8GB resident, jump to last row under a third of a millisecond.
- I tested this thoroughly on my M1 Max MacBook Pro with 64 GB RAM
Everything else:
- Column headers draw their own distribution, null share, distinct count.
- Query plans as a waterfall, or a tree, or raw JSON.
- History is local SQLite with FTS, so you can dig up last week's query from a fragment.
- Completion knows your schema. Connections saved, secrets in the Keychain.
- Extensions are statically linked, so DuckDB's reach is the app's: Parquet, CSV, JSON, .duckdb, local or on S3. Postgres tables attach alongside, so you can join across them. Nothing downloads at runtime.
- Speaks Quack, so you can point it at your own DuckDB server. Want an extension I didn't bundle? spatial, say. Load it there, query through it. Costs about 2x to pull the result across, then it's identical.
- No Electron. No webviews. No bundled Chromium to draw a table.
- Sends nothing anywhere. There's a build check that fails if anything linked in can open a socket.
$39.99 once, not a subscription, 7 day trial first. Apple Silicon, macOS 14+. Swift 6, AppKit. Around 3-4 months of work.
On AI, because someone always asks: couple of decades as an engineer, shipped native apps long before any of this existed. I used Claude throughout. Two places it really earned its keep: getting DuckDB and the extension set statically bundled and actually behaving, and the buffered Core Text grid. The rules were mine and enforcing them was most of the work. No DuckDB call on the main thread. Result rows never become objects. AppKit for anything that renders your data.
App Store: https://apps.apple.com/app/id6811235967
Happy to go into any of it.