Create plugin architecture

[kylecorry31]

Research how a plugin can be added.

• Create an example plugin that has a UI and provides some data to Trail Sense (two way)
• Create a way to show the UI of a plugin (might just mean that Trail Sense can enable or disable a built in tool if the plugin is installed)
• Create a way to communicate with a plugin (if services/broadcast receivers are used, create a implementation)

Questions

• How can Trail Sense communicate with the plugin?
• Can the plugin add UI to Trail Sense or does the UI need to be implemented in Trail Sense and call out to the plugin's service?
• How can Trail Sense detect if the plugin is installed? (I previously experimented with app queries for this, back when offline maps was a "plugin" - though that acted as a launcher for a standalone app)
• How do permissions work for plugins?

[kylecorry31]

https://developer.android.com/guide/components/aidl

[kylecorry31]

https://stackoverflow.com/questions/70674239/android-12-breaks-aidl-ipc-with-runtime-permissions-on-ipc-apk

[kylecorry31]

[kylecorry31]