Developing Apps
SitePack Partners can build and distribute applications that extend the platform's core functionality: anything from a social media integration to an advanced e-commerce tool. Apps let you create reusable functionality once and offer it to any SitePack website, either privately for your own clients or publicly through the App Marketplace.
Application management
The Apps section of your Partner Dashboard lists every application created by your organisation. From here, you can:
- Create a New App: Start the registration process for a new application.
- View App Details: Review each app's description, icon, and current status.
- Access Documentation: Jump straight to the technical developer documentation whenever you need it.
The Apps overview also shows, per app, its status and its key figures at a glance: total installs, monthly recurring revenue (MRR) and annual recurring revenue (ARR).
Publishing and review
Every app starts out Private to your own organisation. To offer it publicly through the App Marketplace, it goes through a short review, and SitePack approves it before it goes live.
The app details page shows a Review checklist: the exact checks our reviewers run, such as a valid icon, a complete English marketplace listing, a valid app.json, and the files your manifest references. Each check shows green when it passes and explains what is still missing when it does not.
You can only Submit for review once every check passes. Keeping the checklist green up front means our review can focus on your app's content and quality rather than technical gaps. After you submit, you can follow the app's status on its page: Submitted, Under review, and finally Live once it is approved.
Listing images
On the app details page you upload the images shown on your marketplace listing: the app icon and up to four screenshots per language. You can use PNG, JPG, GIF, WebP or SVG files, each up to 5 MB. If you upload an SVG, SitePack automatically cleans it before saving, so use plain vector artwork without any interactive or scripted elements.
OAuth and install
Not every app needs OAuth. Enable OAuth on the app page only when merchants install your app through the SitePack consent screen and your app receives an authorization code on a callback URL. When you enable it, set your redirect URI and SitePack provides the client credentials and a ready-to-share install link. Apps that do not use a callback (for example a background integration) can simply leave OAuth off.
Performance
Once your app has at least one install, the app page and the Apps overview show how it is doing: total installs, how many of those are paying customers, and the recurring revenue it generates as MRR (per month) and ARR (per year).
Developer quickstart
To jumpstart development, we recommend using the SitePack CLI (Command Line Interface), a developer tool that helps you scaffold and manage app projects. You can initialize a new application project with a single command:
sitepack app:init
Resources
For detailed technical guidance on building, testing, and deploying apps. Visit our dedicated developer portal:
Frequently asked questions
What can a SitePack app actually do?
Apps extend the core functionality of a SitePack website. Examples include social media integrations, advanced e-commerce tools, or other custom features not built into the platform by default.
Do I need to know how to code to build an app?
Yes. App development is a technical process that uses the SitePack SDK and CLI, intended for developers. If you're looking for no-code customization instead. See Theme & Design for what regular site owners can adjust without coding.
What is the SitePack CLI used for?
The CLI (Command Line Interface) is a developer tool for creating and managing app projects from your terminal. Running sitepack app:init scaffolds a new application project to get you started quickly.
Can I sell the apps I build?
Yes. Apps can be distributed through the App Marketplace, where SitePack users can discover and install them, and you can earn commissions on sales. See Commission Platform.
Where do I find full technical documentation for building an app?
Visit the SitePack App Documentation on our developer portal for complete, in-depth guidance.
Can I keep an app private to my own clients instead of publishing it publicly?
The Apps section lets you manage your organisation's applications and their status; check the app's details and documentation for the specific visibility options available when registering a new app.
How do I get my app listed on the marketplace?
Set the app to Public, complete the marketplace listing, and get every point on the Review checklist to pass. Then use Submit for review on the app page. SitePack reviews and approves the app before it appears publicly.
Why can't I submit my app for review yet?
The Submit for review button stays disabled until every check on the Review checklist passes. Open the checklist on the app page: each failing check explains exactly what is still missing (for example an icon, a complete English listing, or a file your app.json references).
Does my app need OAuth?
Only if merchants install it through the SitePack consent screen and it receives an authorization code on a callback URL. Enable OAuth on the app page in that case and set your redirect URI; otherwise leave it off.
What image formats can I use for my app icon and screenshots?
You can upload PNG, JPG, GIF, WebP or SVG files, up to 5 MB each. SVG files are cleaned automatically when you upload them, so stick to plain vector artwork without scripts or interactive elements.