Soln Development Guidlines

A Solution is a collection of compatible apps that solve an end-to-end business workflow. For example, a delivery management solution can include multiple apps such as dispatch, order management, routing, facility management, user management, etc., required to manage last-mile deliveries. Below are some important elements to consider when defining your solutions.

If you’ve included your app in a solution, ensure that your app content clearly describes its features and addresses potential questions. Additionally, if your app isn’t published yet and is in the development stage, ensure it follows the App Review guidelines before publishing.

Ensure your solution doesn’t include any app that has more than one backend with one front-end. For example, an Order web app in a solution should not have many independently registered backend apps. Instead, it should have only one backend and one front-end app.

To avoid rejection of your solution, ensure that you have the necessary rights to use the apps included.

Your solution and the apps within it should be multi-tenant. We’ll only require review for apps currently in development.

Core Apps are mandatory for a particular use case across all solutions. Therefore, you must keep the Core Apps within your solution to ensure it's accepted.

There are some apps that are included in the solution by default.If your solution has replaced any default app, ensure the app you replaced works as expected with a compatible app.

If you include add-on apps in the solution, ensure they are approved and published before submitting the soln with the add-on app for publishing.

Your solution must be fully functional and bug-free. Perform end-to-end testing on commonly used features and multiple scenarios. Furthermore, do not attempt to publish an app with known bugs or performance issues.

Only use components and other assets you’ve created to avoid infringement on the copyrights or IP of others. This includes ensuring that your solution has the necessary licenses to use paid or open-sourced external software.

When you submit your solution for review, clearly state your user data collection and retention policy. Additionally, communicate to users how you intend to use their data. Lastly, include required terms and conditions that inform users about your privacy policy.

Provide complete and easily accessible documentation for your solution. For example, your user guides should be easy to follow and help users understand how to use your solution. Additionally, you must provide support channels that are readily accessible and contact information for support inquiries.