The current extension system in Modly is incredibly powerful, but discovering and installing new extensions can be a bit fragmented. Users currently need to manually hunt down GitHub repositories and paste URLs to install new AI models. A centralized way to browse and install community-created extensions would massively improve the user experience and encourage more developers to build for the platform.
I propose building a "Serverless Marketplace" directly integrated into the Modly UI, powered entirely by a public JSON registry hosted on GitHub. This avoids the need for a dedicated backend database or server infrastructure.
Here is how the architecture could work:
- The Registry: We create a registry.json file (either in the main repo or a dedicated modly-extensions repo). This file contains an array of metadata for all approved extensions (e.g., id, name, author, description, github_url, tags).
- The Creator Workflow: When a community developer creates a new extension, they don't upload the code here. They simply fork the registry repository, append their extension's JSON object to the list, and open a Pull Request.
- App Integration: The Modly React/TypeScript frontend makes a GET request to fetch the raw registry.json (potentially via a free CDN like jsDelivr to avoid GitHub rate limits). The UI parses this file and renders a clean "Marketplace" grid.
- One-Click Install: When a user clicks "Install" on an item, Modly triggers the existing installation logic using the github_url provided in the JSON.
The current extension system in Modly is incredibly powerful, but discovering and installing new extensions can be a bit fragmented. Users currently need to manually hunt down GitHub repositories and paste URLs to install new AI models. A centralized way to browse and install community-created extensions would massively improve the user experience and encourage more developers to build for the platform.
I propose building a "Serverless Marketplace" directly integrated into the Modly UI, powered entirely by a public JSON registry hosted on GitHub. This avoids the need for a dedicated backend database or server infrastructure.
Here is how the architecture could work: