This topic explains what applications and application versions are and how to use them.
An application is a LaunchDarkly resource that describes what you are delivering to a customer. LaunchDarkly automatically creates applications when it establishes a connection with a LaunchDarkly SDK that contains application information. After LaunchDarkly creates an application, you can build flag targeting rules based on the application name, version, or other properties, such as whether or not a particular application version is supported.
For a list of SDKs that support applications and application versions, read the SDK configuration topic.
Applications are unique per account. This means that the same application can exist in multiple environments, across different projects.
If you use engineering insights, you can also automatically create applications when you send deployment events. To learn how, read Applications in Engineering insights.
The most common use case for working with applications is when you are developing a mobile app. You can use applications to track which versions are associated with which flags, and to evaluate flags differently for supported or unsupported app versions.
Here’s how:
From the Applications list, you can find applications by name or key. You can also narrow the list by kind, or sort the list by application name or creation date. By default, the most recently created applications appear first.
When you click the name of an application in the Applications list, the application’s Versions page appears. From the Versions page, you can do the following:

To access the change history for an application, click the clock icon. The “Change history” dialog appears, filtered to show the changes made in LaunchDarkly to the application or its versions. To learn more, read Change history.
The application’s Versions page shows the adoption of your application by application version.
The adoption percentage for each application version is calculated as the ratio of:
that LaunchDarkly has seen over the last 30 days.
For example, suppose there are five devices running your application. If two of those devices are using v3.0, then the adoption percentage for v3.0 is 40%.
Because the adoption percentage only looks at the last 30 days, your adoption percentages could change over time. For example, it may look like 100% of your customers have adopted v3.0 of your app if a customer with an older version does not use the app very often.