Skip to main content

Products as a concept

In WPP Open, the term "product" means applications that you can develop for Open OS. This guide walks you through different applications that you can build within Open OS.

Native apps​

For those interested in full-fledged development, we offer the ability to build native apps. They are loaded into iframes as a micro-app and can utilise specific APIs provided by Open and Open's Authorisation framework for seamless interactions.

The following are the key features of native applications:

  • Launched within an iframe: Open OS introduced Content Security Policy (CSP) standards with minimal permissive CSP headers across Open. To support the implementation of CSP headers, native applications are launched with an iframe environment.

  • Supports single-spa: Open OS runs native products as micro-frontends with single-spa. This includes handling product registration, managing base routing, and overseeing the mounting and unmounting of micro-apps. We support products written with React, Angular, and Vue.

  • Supports os-context: Native applications support the use of OS Context that helps developers to extract needed information on the project, application instance, custom configuration and permissions.

  • Supports versioning: Product versions enable you to maintain isolated product configurations for the development and production environments in Open OS. You can support multiple different versions—each with its route, roles, permissions, and so on—as you continue to develop and test your product.

  • Supports adding roles and permissions: Open OS features a built-in authorization and permissions management module, Open Authorization, which allows you to control user access to different functions and data in your product. To onboard a product, you need to integrate with Open Authorization.

tip

We recommend that each team develop their products as native to Open OS. This way, your product can benefit from the full potential of Open OS, and we can ensure its seamless integration with all platform components.

See Build native products to start developing your first native product.

Embedded link applications are loaded into an iframe as well, but not as a micro-app. Key features of embedded links are as follows:

  • Launched within an iframe

  • Supports os-context

  • Supports adding roles and permissions

Choose a native application when your app is a single-SPA and demands versioning.

Opt for an embedded link if your app isn't a single-SPA and doesn't need versions.

ProductNativeEmbedded Link
iframe (embedded on page)YesYes
Single SPA (loaded as a micro app)YesNo
OS Context (context data passed to the app)YesYes
Versions (multiple product instances)YesNo
Profiles (share roles & permissions between versions)YesNo
Role and permissionsYesYes

No-code apps​

Open OS enables you to create functional no-code products without the traditional development processes.

In most cases, adding no-code products comes down to choosing the appropriate template and filling out its configuration details in DevHub, and does not require any software development skills.

The following are the types of no-code applications supported by Open OS:

  • Embedded link: Easily embed webpages into an iframe. Follow embedded link configuration guide to learn more.

  • Embedded code: Display products that do not support iframe natively. Follow embedded code configuration guide to learn more.

  • External link: Provide a way to navigate to a product outside of Open OS. Follow external link configuration guide to learn more.

  • Custom page: Create static pages through the Open OS WYSIWYG page builder. Follow custom page configuration guide to learn more.

  • Miro board: Embed boards from Miro. Follow miro app configuration guide to learn more.