Displays a list of applications can be downloaded and used by user.

Page Summary

Specifications references


The Recirculation module exposes a feature allowing the final users to get the available apps they can use. This feature is based today only on the Orange proprietary Apps Plus backend which provides a JSON file with list of apps and sections of apps. This service today is based on a simple URL containing both a lang parameter and an API key.

This API key will define the type of data returned by the backend ; maybe you should have your own API key which matches the suitable filters to get only a subgroup of apps.


To be able to call this service and display the list of available apps, you have to use the ODSRecirculation. This View has a dataSource parameter of type ODSRecirculationDataSource which must contain the type of source of data to display the apps:

    // Get data from the Apps Plus backend
    ODSRecirculationView(dataSource: .remote(url: "https://url-to-appsplus-backend/get?apikey=SomeKey&lang=fr"))
    // Get data for some local files
        ODSRecirculationView(dataSource: .local(path: somePathToJSONFileInResources))

Note also that the data picked from the Apps Plus service is saved in cache directory so as to be used if the device is offline or if an error occured.

If you want to flatten the list of apps without displaying categories, set the flattenApps flag in the configuration:

    ODSRecirculationView(dataSource: ..., flattenApps: true)

The apps icons displayed in the list of apps can also be cached. If you do not want to see these values put in cache, meaning e.g. displaying instead a placeholder if no network, use:

    ODSRecirculationView(dataSource: ..., cacheAppsIcons: false)

The list of apps can trigger also haptic notifications, e.g. vibrations when the data have been lodaded or if an error occured. By default this feature is enabled, but it can be disabled:

    ODSRecirculationView(dataSource: ..., enableHaptics: false)

Example about definiton of Apps Plus credentials

You can for example for your app use a .xcconfig configuration settings file to store such credentials. A key named APPS_PLUS_URL can be defined with the URL (containing the API key) to call. Then the Info.plist file of your app must have an entry with the same name. Of course the .xcconfig file should not be versionned in Git, ensure this with Gitleaks for example.

See the example for the .xcconfig:

// Configuration settings file format documentation can be found at:
// See also

APPS_PLUS_URL = https:/$()/url-to-api?apikey=$(APPS_PLUS_API_KEY)

// Here $() prevents the // to be interpreted as comment, we suppose the URL has an apikey parameter and is GET only

And the entry for the Info.plist:

    <key>APPS_PLUS_URL</key> <!-- Key used in the demo app code -->
    <string>${APPS_PLUS_URL}</string> <!-- Key in the xcconfig side, or write here the full URL with API key but without lang -->

Then in your code you can read the URL, get the locale, and forge the final URL to give to ODSMoreAppsItemConfig. We could have choosen this implemention deeper in the repository but wanted to let ODS lib users choose their own way to deal with the URL.

    private func buildAppsPlusURL() -> URL {
        guard let appsPlusURL = Bundle.main.infoDictionary?["APPS_PLUS_URL"] else {
            fatalError("No Apps Plus URL found in app settings")
        let currentLocale = Bundle.main.preferredLocalizations[0]
        let requestURL = "\(appsPlusURL)&lang=\(currentLocale)"
        guard let feedURL = URL(string: requestURL) else {
            fatalError("Failed to forge the service URL to get more apps")
        return feedURL
    // And then ODSRecirculationView(dataSource: .remote(url: buildAppsPlusURL()))

In some CI/CD chain like our GitLab CI runner, we can use a Fastlane lane to read some previously environment variable and fill the Info.Plist file in the suitable row.