Domphy
plain-object UI for tool apps, AI-correctable output
Details
- External ID
- 48593346
- Source
- HN
- Company
- —
- Product
- —
- Website domain
- —
- Launched
- June 19, 2026
- Cohort
- —
- Upvotes
- 11
- Upvotes percentile
- 0.6284153005464481
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:26 p.m.
- Updated at
- Sept. 7, 2026, 9:26 p.m.
Description
I built a UI framework named Domphy because I could not learn React although I tried many times. I mean I could not understand React code which is hidden behind multiple layers, especially when some of them use React ecosystem libs. Maybe I am an architect turned developer, so I had no foundation of programming, or I expected something clear and clean.I just think that UI should be simple — HTML and JS are enough and just need some way to make it stateful instead of making it more complicated. My idea: just using JS objects to reflect HTML, and using functions for state. When I need to reuse a component I had one more concept — just make a partial (I call it a Patch) to add props to the main object (but native props still win). With a component-based approach you get deep nesting and exploding props, but with patches you don't. The example below: import { ElementNode, toState } from "@domphy/core"; import { tooltip } from "@domphy/ui"; const count = toState(0); const App = { div: [ { h3: (listener) => `Count: ${count.get(listener)}` }, { button: "Increment", onClick: () => count.set(count.get() + 1), $: [tooltip({ content: "Add one to the count" })], }, ], style: { display: "flex", gap: "8px", alignItems: "center" }, }; const root = new ElementNode(App); root.render(document.getElementById("app")!); Right now I am the only one using Domphy, for around a year, for creating SketchUp and Revit plugins in the AEC (Architecture, Engineering, Construction) industry. I created Domphy before AI code generation took off, to make code humans can read and understand clearly, but now AI can build UIs with React well, so sometimes I feel my work is meaningless. But I still use Domphy for my apps, because I feel more confident when I need to read and edit UI code when the AI gets stuck.
Enrichment
- Theme
- browser automation and scraping for AI
- Vertical
- Horizontal
- Function
- Dev tools
- Audience
- Developer
- AI stance
- AI feature
- Project type
- Commercial product
- Normalized one-liner
- ui framework for tool apps with ai output correction
- Manually corrected
- False
Could you build this?
Yes A lightweight, plain-JavaScript/DOM manipulation UI library designed for simple tool apps can be built and iterated with an AI assistant in a couple of weeks.
Discussion
3 comments analyzed.
Competitors mentioned: Preact
Competitors
Other products that read as similar to this one — 202 launches clear the similarity bar, closest 8 shown.
Attention rank: #97 of 203 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 227 days after the earliest competitor.
- Elements by Unlayer - Open-source React components for emails, pages, and PDFs · yc · 2026-07-08 · 5 upvotes · similarity 0.50
- Coi · hn · 2026-01-20 · 225 upvotes · similarity 0.50
- Viora UI · ph · 2026-09-14 · 1 upvotes · similarity 0.50
- Once UI 2.0 · ph · 2026-09-25 · 75 upvotes · similarity 0.49
- A portfolio that re-architects its React DOM based on LLM intent · hn · 2026-02-22 · 6 upvotes · similarity 0.49
- Nectar, a Rust-like React that compiles to WebAssembly · hn · 2026-07-06 · 29 upvotes · similarity 0.48
- morph-ui · github · 2026-09-24 · 35 upvotes · similarity 0.48
- GrainJS · hn · 2025-12-26 · 5 upvotes · similarity 0.47
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a dev tools tool for Sales yet.