​
IFrame

The IFrame is a sandboxed web page, it can be thought of as an entire isolated standalone website that is loading inside the surrounding application.

​
Benefits of the IFrame

  • The IFrame is an isolated environment. There will be no unexpected interactions or clashing between the application and the embedded dashboard because they are completely separate.
  • Potential performance benefits - the loading of the IFrame and the surrounding application happen separately and one after the other. This means the IFrame should not impact the load time of the surrounding application.

​
Limitations of the IFrame:

  • URL parameters in the browser can not be read directly from the IFrame and must be pushed into the IFrame url.
  • URL relative paths are not accessable by the IFrame to be used for link formatting in the dashboard.

​
Additional Notes on IFrame Security:

  • The IFrame is authenticated with an expiring JWT, so the IFrame itself will expire after an amount of time they provide.
  • The IFrame optionally can take in an iss claim that requires that the IFrame can only be loaded from that parent domain.
  • The IFrame also follows our normal allowlisting rules, so even without the iss claim, the IFrame can only be viewed on domains that they’ve allowlisted.

​
Web Component

The web component is essentially a piece of code that will render inside the context of the surrounding application.

​
Benefits of the web component option:

  • The web component lives in the same JS environment as the surrounding application. This means Explo supports event listeners via the web component. It also reads in URL params from the browser, and can pull in the URL relatives into the dashboard.

​
Limitations of the web component:

  • There can be unexpected style clashing or loading issues as a result of one entire application’s code being loaded inside another application’s code.
  • Many of Explo’s drag-and-drop functionality is not compatible with CSS transforms. Please disable CSS transforms.