Hey Product Hunt — maker of XCON Viewer here.

I built XCON Viewer because Markdown is great for writing specs, docs, and product notes, but it is still limited when you want to describe an actual interface.

With XCON Viewer, you can write structured UI blocks inside Markdown and preview them as interface-like screens. Cards, charts, grids, dashboards, reports, and product screen ideas can live directly next to the text that explains them.

The goal is not to replace frontend development. It is to make early UI ideas easier to write, review, share, and version before they become full apps.

I think this can be useful for makers, technical writers, product teams, AI workflows, and anyone who uses Markdown to explain product ideas.

I’d love feedback on three things:

• Would you use Markdown to describe UI ideas?

• What UI blocks would be most useful: cards, charts, grids, forms, dashboards, or mobile screens?

• Should this lean more toward documentation, prototyping, or reviewing AI-generated UI?

Thanks for checking it out.

Forum Threads

p/xcon-viewer

•

3mo ago

What should Markdown-native UI be useful for first?

We re launching XCON Viewer to explore a simple idea:

Markdown is great for writing specs, docs, product notes, and technical explanations but it is still limited when you want to describe an actual interface.

With XCON Viewer, we re trying to make it possible to write structured UI blocks inside Markdown and preview them visually. Things like cards, charts, grids, dashboards, reports, and screen concepts can live directly next to the text that explains them.

The part we re thinking about most is where this should be useful first.

View all

Hey Product Hunt — maker of XCON Viewer here.

I built XCON Viewer because Markdown is great for writing specs, docs, and product notes, but it is still limited when you want to describe an actual interface.

The goal is not to replace frontend development. It is to make early UI ideas easier to write, review, share, and version before they become full apps.

I think this can be useful for makers, technical writers, product teams, AI workflows, and anyone who uses Markdown to explain product ideas.

I’d love feedback on three things:

• Would you use Markdown to describe UI ideas?

• What UI blocks would be most useful: cards, charts, grids, forms, dashboards, or mobile screens?

• Should this lean more toward documentation, prototyping, or reviewing AI-generated UI?

Thanks for checking it out.

XCON Viewer

AI-Generated UI Inside Markdown

AI-Generated UI Inside Markdown

Forum Threads

What should Markdown-native UI be useful for first?

Forum Threads

What should Markdown-native UI be useful for first?