Where can I read about the main difference between an App and a Plugin in the App Platform

I have been looking for the documentation for the major difference between an App and a Plugin in the App Platform but have not seen one.

Can someone point me to this?

Anyone with this info?

Monthly Dev Meetup : https://www.youtube.com/watch?v=gqGoRF3ktw4

For Apps : https://www.youtube.com/watch?v=WP6ZWbsTz-Q&list=PLCijFqDkh2y28i-2DpwcY8-21Wk5Rtzjw&index=5

For the Plugin : https://www.youtube.com/watch?v=RVkOAPcHWVg

Documentation :

I believe this will help you

2 Likes

The documentation is not opening but the videos didn’t really address my question as it focus more on the introduction of extensions and not the difference between the App and Plugin

Thanks for the question @jetisco4u . For the moment, we are focusing on encouraging the use of capture plugins. Our webinars (thank you @hio.amakomaya ) and our documentation (Getting started | DHIS2 Developer Portal) reflect this prioritization.

We next plan to enable use of plugins in the dashboard, and when we do so, we will provide some additional documentation.

While it is possible to build your own plugins that can be consumed within your own apps (e.g. for code reuse purposes), this is not a use case which we have prioritized documenting. You can find references to how to configure and use plugins in our documentation for our d2.config.js file (Configuration File Reference | DHIS2 Developer Portal) and in our documentation of our component (Plugin Component | DHIS2 Developer Portal)

If you have a specific reason why you are interested in using the plugin architecture, please let us know.

(cc @kpvandivier , @Rene )

1 Like

Links to the developer site is not opening from my end

I have looked at the plugin architecture but can’t really figure out the main difference between it and an app given that both of them import the AppAdapter in the header and have a root define in the index.html file.

I am building a custom architecture using my proprietary DOMS architecture with a custom Routing solution and a custom framework that support plugin injection at build time. But the idea of my plugin is one that will use React Portal without the AppAdapter. I want to fully remove the plugin and use app in d2.config file while I use Plugin for my own architecture.

If you share the error you are getting when trying to access the docs site, maybe @rene can help troubleshoot.

The page is opening again