This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
XCON Viewer
Render UI code blocks in Markdown as real interface previews
Write UI inside Markdown. XCON Viewer helps you add cards, charts, grids, dashboards, reports, and screen concepts to Markdown documents and preview them as real interfaces. It is useful for product specs, technical docs, data reports, lightweight prototypes, and AI-generated UI review.
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.
About XCON Viewer on Product Hunt
“Render UI code blocks in Markdown as real interface previews”
XCON Viewer was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #136 on the daily leaderboard. Write UI inside Markdown. XCON Viewer helps you add cards, charts, grids, dashboards, reports, and screen concepts to Markdown documents and preview them as real interfaces. It is useful for product specs, technical docs, data reports, lightweight prototypes, and AI-generated UI review.
On the analytics side, XCON Viewer competes within Design Tools, Productivity, Writing and GitHub — topics that collectively have 1M followers on Product Hunt. The dashboard above tracks how XCON Viewer performed against the three products that launched closest to it on the same day.
Who hunted XCON Viewer?
XCON Viewer was hunted by xcon. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of XCON Viewer including community comment highlights and product details, visit the product overview.
xcon
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.