API: Option to create custom components/extensions/addons #2435

New issue

Open

opened 2026-02-20 01:11:29 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-20 01:11:29 -05:00

Owner

Originally created by @Blendan1 on GitHub (Nov 11, 2025).

Confirmation

I checked this request against the roadmap and existing issues

What Problem Does This Solve and Why Is It Valuable?

An option to create your own extensions/addons for the Frontend (maybe even with backend options like custom apis) would be great, as it would allow external developers to work on photoprism and create custom features without impacting the main project.
Other users can then import the addons from others and use them.

What Solution Would You Like?

It would be great to have an addon manager in the settings, something where you can add addons from a link (github) and it can search for updates automatically, the addons are then loaded into the page/api.
The addons are stored in a folder where you can also add addons manually (for development) without a github.

The addons itself are vue components that get a Standard api and a placer file where the component should appear (is it a new tab in photo details, in the side menu, in the search or so on) and the api the component gets is determend by where its placed (so the current scope).

as for the backend im unsure of how to do that maybe someone else has an idea there.

What Alternatives Have You Considered?

Currently i wrote some addons by directly manipulating the page via js and getting the apis by looking into the dom of the page, but this is very buggy and not reliable.

Additional Context

No response

Originally created by @Blendan1 on GitHub (Nov 11, 2025). ### Confirmation - [x] I checked this request against the roadmap and existing issues ### What Problem Does This Solve and Why Is It Valuable? An option to create your own extensions/addons for the Frontend (maybe even with backend options like custom apis) would be great, as it would allow external developers to work on photoprism and create custom features without impacting the main project. Other users can then import the addons from others and use them. ### What Solution Would You Like? It would be great to have an addon manager in the settings, something where you can add addons from a link (github) and it can search for updates automatically, the addons are then loaded into the page/api. The addons are stored in a folder where you can also add addons manually (for development) without a github. The addons itself are vue components that get a Standard api and a placer file where the component should appear (is it a new tab in photo details, in the side menu, in the search or so on) and the api the component gets is determend by where its placed (so the current scope). as for the backend im unsure of how to do that maybe someone else has an idea there. ### What Alternatives Have You Considered? Currently i wrote some addons by directly manipulating the page via js and getting the apis by looking into the dom of the page, but this is very buggy and not reliable. ### Additional Context _No response_