HN Explorer

5 comments

[ 4.2 ms ] story [ 74.0 ms ] thread
somery
Hi, it's Alex from DocuSeal.

Recently we released a new embedded JS api for document signing at DocuSeal. Instead of doing it via iframe we decided to provide a JS-based solution.

Here are some benefits over iframe:

- faster load speed

- easy to customize

- optimized on different screen sizes

Also there is a React components library which also works with SSR Next.js https://github.com/docusealco/docuseal-react

Looking for some feedback and would be happy to answer any questions.

babanooey21
What do you mean by native Web components?
somery
The solution utilizes a native web elements (aka web components) browser API for easier embedding into websites: https://developer.mozilla.org/en-US/docs/Web/API/Web_compone...

Basically instead of using JS snippet for mounting the UI - we're using a custom web element so it can be embedded just with HTML tag without JS.

quickthrower2
What is the main advantage of that for a user? Compared to say a css class or node id?

You still need a script tag either way it seems.

somery
When comparing to Iframe our JS-based solution better adopts to the existing page layout due to the fact that it embeds into the existing page DOM (when iframe lives in it's own DOM which brings many limitations). Also it loads much faster than any equivalent iframe solution