On Modern Widget Architectures
(2) Pixlee publishes through encapsulated code via iFrames.
iFrame versus Native JS is an ongoing debate played out by software vendors that live on client websites. While there are pros and cons for both, we are firmly in the iFrame with a thin native-js control layer camp. We’ve followed this approach for years now and have been able to produce an incredibly compelling set of products that minimize up-front integration resources, ongoing integration maintenance, and ensure maximum stability. We pride ourselves on being pioneers in the space.
All Pixlee code is protected & maintained by our team and operates within our sandboxed iFrame environment. This ensures that our integrations cannot interfere with any other site functionality or design and vice-versa.
(1) Design control over style and functionality
(2) Speed and performance.
In practice however, we have been able to create a system that addresses both of these issues.
We provide marketers full control over gallery design without the need for development resources through a WSIWYG design editor, as well as a sandboxed environment for designers to customize our widgets to their hearts content without worrying about CSS resets, already-set styles, or any myriad of issues that may come up. There is no risk of conflict between Pixlee and other aspects of the host site. And because many of the most cutting edge companies have invested in iFrame and Cross-Domain techniques over the last few years, we’ve been able to stay ahead of the curve in speed and performance.
Our architecture allows brands to make improvements and optimizations on their Pixlee initiatives without disrupting or requiring involvement from engineering resources.