Solution Development Guidelines

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 list of apps 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 solution design 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 rights of usage to avoid rejection of your solution, ensure that you have the necessary rights to use the apps included multi tenancy your solution and the apps within it should be multi tenant we’ll only require review for apps currently in development core apps 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 default apps 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 add on apps 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 functionality and performance 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 copyrights and ip infringement 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 customer data and user privacy 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 user guides and support 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