--- cuppy_hub: salesforce cuppy_path: reference/official/data360/data-cloud-dev/guide/dc-app-lifecycle.md cuppy_section: docs cuppy_doc: 0GAN-F7AT cuppy_doc_uuid: 55ce0623-9e13-4b9e-bf6c-7991806a72a3 cuppy_permalink: https://cuppy.io/salesforce/d/0GAN-F7AT cuppy_version: 1 cuppy_updated: 2026-10-23T16:16:52.575Z cuppy_canonical: https://cuppy.io/salesforce/docs/reference/official/data360/data-cloud-dev/guide/dc-app-lifecycle cuppy_mcp: https://cuppy.io/mcp cuppy_body_sha256: 75e4867298d0fc992460fab163df33da68e2160772dae2809941ae38664840e9 # cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks. --- > Mirror of (Salesforce, Data 360 Developer Guide), read 2026-10-23. Salesforce's own page is the authority; this copy exists because that site refuses non-browser readers. ## App Development Lifecycle The app development lifecycle includes planning and gathering requirements, creating the app, testing the app, making iterative changes to fix issues, and performing user-acceptance testing as a final test. The final step for an app developed in-house is the app’s release to production. The final step for an app developed by a Salesforce partner is app distribution to other Data 360 customers who purchase the app. ![Image 1: App development lifecycle](https://a.sfdcstatic.com/developer-website/sfdocs/data-cloud/media/data-cloud-dev/AppDevLifecycle.png) If you’re a Salesforce partner, the development lifecycle also includes distributing, marketing, selling, and supporting your app. ![Image 2: App development lifecycle for Salesforce partners](https://a.sfdcstatic.com/developer-website/sfdocs/data-cloud/media/data-cloud-dev/AppDevLifecycle-Partner.png) For more information about the Salesforce partner program, check out the [Build Apps as an AppExchange Partner](https://trailhead.salesforce.com/content/learn/trails/isv_developer_beginner) trail. This trail is intended for development on the Salesforce platform and isn’t customized for Data 360, but it contains some useful information about the program. We encourage customers to purchase apps from Salesforce partners rather than building them themselves. Installing and using apps from AppExchange ensures that the app is maintained regularly and meets quality and security standards. In addition, AppExchange apps save customers time and resources. Third-party apps that are available on AppExchange are for data activation and data enrichment. To find AppExchange apps AppExchange for Data 360, see [Data 360 product collection](https://appexchange.salesforce.com/mktcollections/cloud-collections/customerdataplatform) on AppExchange. If you’re a Salesforce partner, you’re familiar with the package development workflow, and you know that the workflows and tools for developing a first-generation managed package and second-generation managed package are distinct. To learn about building apps on AppExchange, check out these resources. * _[First-Generation Managed Packaging Developer Guide](https://developer.salesforce.com/docs/atlas.en-us.pkg1\_dev.meta/pkg1\_dev/sharing\_apps.htm)_ * _[Second-Generation Managed Packaging Developer Guide](https://developer.salesforce.com/docs/atlas.en-us.pkg2\_dev.meta/pkg2\_dev/sfdx\_dev\_dev2gp.htm)_ * _[ISVforce Guide](https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/packaging\_intro.htm)_ * _Salesforce Help:_[_Build and Share Data 360 Functionality_](https://help.salesforce.com/s/articleView?id=data.c360_a_build_and_share_functionality.htm&type=5) * _Trailmix_: [Building Data Cloud Activation Platform Apps for ISVs](https://trailhead.salesforce.com/users/isv-platform-experts/trailmixes/building-activation-platform-apps-for-isvs) Customer developers who develop an app in-house for their own org can use a separate test org for creating and testing their apps. You can use a sandbox org with Data 360 (beta) for testing, or you can use a test org. The Data 360 test org is also a production org, and service usage results in billing charges the same way as on the production org. See [Cost and Usage](https://developer.salesforce.com/docs/data/data-cloud-dev/guide/dc-cost-usage.html). To request a Data 360 test org, contact your Account team. The app development lifecycle model described in this section uses an org dedicated for development and testing and the Data 360 production org. In this model, you develop and test the app on one Data 360 org and release it to production. You migrate the app and configuration settings to the production org using unmanaged packaged, data kits, or Metadata API. ![Image 3: App development lifecycle for customer developers](https://a.sfdcstatic.com/developer-website/sfdocs/data-cloud/media/data-cloud-dev/DataCloud_AppDevelopmentFlowChart.png) **See Also** * [Packages and Data Kits](https://developer.salesforce.com/docs/data/data-cloud-dev/guide/packages-data-kits.html) * [Metadata API](https://developer.salesforce.com/docs/data/data-cloud-dev/guide/custom-app-dev.html#metadata-api) * [_Salesforce Help_: Data Cloud in a Sandbox (Beta)](https://help.salesforce.com/s/articleView?id=data.c360_a_data_cloud_sandbox.htm&type=5) --- You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 376 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/salesforce/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.