Marketplace
What Are the Platform Capabilities of the Mendix Marketplace?
What Types of Reusable Components Are Available in the Mendix Marketplace?
For developers, the Mendix Marketplace offers a rich repository of reusable components that can significantly accelerate development productivity. These components are shared in the Mendix community as open-source components or commercial products.
The Mendix Marketplace is directly accessible from Mendix Studio Pro, where Marketplace components can be loaded into the project model with a single click. The components are presented in the categories described below.
-
Connectors
A connector is a Mendix Marketplace component that contains microflow activities that can directly be used in your app logic to connect to external systems. For example,the AWS DynamoDB connector provides a way for you to increase the security, scalability, and performance of your Mendix app by implementing AWS DynamoDB, and the OData Connector for SAP solutions to can be used to connect to any SAP system.
-
Widgets
A Mendix widget is a part of your Mendix app’s UI that enables functionality and interaction with users of the app. The widget is a page element used to display (visual) information on the page and to provide additional page interactions, like swipe controls or form-based fields.
The Mendix Platform provides several dozen widgets out of the box, and additional widgets are available from the Mendix Marketplace. A full overview of Mendix-supported widgets is shown on the Mendix Atlas UI site.
In addition to the widgets provided by Mendix, any developer can build additional custom widgets and upload these to the Mendix Marketplace. A custom widget can alter the interface, data, and images of the app as well as the way the app works. For details on creating a custom widget, see the Make Custom Widgets how-to’s in the Mendix Studio Pro How-to’s.
-
Modules
A module is a self-contained application component that can be reused in multiple applications. Modules can be downloaded from the Mendix Marketplace/Marketplace into a project as a local copy. By doing this, the module becomes part of the project scope and is maintained through its lifecycle as part of the app project.
A module typically consists of a domain model, user interfaces, and microflows. Although technically identical, the following types of modules can be distinguished:
- Functional business modules (for example, PostalCodeHousenumber for discovering street addresses)
- Integration connectors (for example, the Excel Importer)
- Technical module (for example, Audittrail for audit logging)