For MVP:
• Focus just on external tools
• Specifically remote external tools
• This encompasses the vast majority of external tools currently in production
• Simpler, as no need to install any apps, just register the manifest file
• Would not be tied to a specific version of the app (though we could ask apps, for example, to provide an API which we could query to know existing versions?
•Simple db would contain all the tool info to “advertise” and register (e.g. the manifest file)
• Simple UI to add tools to that DB
• Locally run apps are more complicated, so not for MVP
• Marketplace itself would be an external tool, that eventually could be embedded into Dataverse SPA UI (under some admin tool type section, maybe?)
• Requires modification of external tools API to be runnable outside of Admin (can be created as an issue already)
• Need to think about auth / security - one time URL for this?
• Provide extra auth specifically at manifest registration time
• API for listing public info of tools
• Define tool compatibility with which version of Dataverse
• Check if tool is still working / status check
• Start as a shiny app