Working with plug-ins


An plug-in is an out-of-the-box example app that can be easily added to your project. It can be as simple as a single page or service but provide more complete functionality; it usually contains a page, service, and mapping. Such plug-ins are called public and are available to all users by default.

Working with Plug-ins

A public plug-in is usually created by the team and then made available.
Our team regularly releases new plug-ins. To review the available plug-ins from , in the Project view, click CREATE NEW > From Plugin:


In the new window, the Catalog of plug-ins opens where you can apply filtering or grouping by Category or API Provider:


Catalog of plugins


Most sample apps can be imported as a plug-in.


Private Plug-ins

You can also create your own plug-ins called private. These plug-ins will be private by default, and available only to you.
With this option, you can create your own services and save them as plug-ins to use later. In fact, this is a custom implementation of generic services. These plug-ins will be private by default but can also be made public.
To learn how to create a private plug-in, update it, or publish it as a project template, go to this page.
Both plug-ins types (public and private) work exactly the same way and are listed in the Catalog of plug-ins (in the app editor, click CREATE NEW > From Plugin).

To quickly find the needed plug-in, you can start typing its name or group all plug-ins by the vendor. By default, they are grouped by Category:


👍 YouTube Channel

You can also check our YouTube Channel where the newest and/or most requested plug-ins are presented.


Resolving Name Conflicts

If an app resource name conflicts with a plug-in resource name, it will be automatically renamed. You might need to rename screens, services, directives, etc.