Open Reports
Design reports in your browser. Render them anywhere.
Start new thread

How should an embedded report designer fit into an existing app?

by•

I’m building Open Reports around one integration boundary: the host application owns report JSON, authentication, business data, and when users can print; Open Reports edits the definition and renders the output. The host can send a definition and JSON data to the render API, or embed the designer and save edits back to its own store.

I’ve tested the embedded workflow in a second-origin Chromium host. Other browsers and restrictive production CSP setups still need validation. This is early v0.x, not a drop-in JasperReports or Crystal Reports replacement; JRXML import is partial and compiled .jasper files are not supported.

If you build software that embeds reports, where would this model break for you? What would you need to see before trying it with one synthetic invoice or statement?

Demo:
Code and integration guides:
10-minute workflow:

3 views

Add a comment

Replies

Best

Update: the 12-minute flagship walkthrough is now playable on the demo site, with English captions, a transcript, and chapter links: . It shows creating an invoice report and integrating it into a host application through the render API and embedded designer, using fictional sample data. If you try it, I’d especially value feedback on any integration step that feels unclear.