SDK Integration

at purple, we are happy to integrate sdks and 3rd party systems that we do not currently support we believe that this helps to provide variability and opportunity for our customers not every 3rd party system is ready to integrate with the purple platform following our product approach, we need to be able to automate the build process of our purple apps we provide a white label app framework (native android and ios, respectively) to which we pass a specific configuration and get an app as output for third party integrations, we have certain abstraction layers for instance, analytics frameworks and consent management platforms requirements in result, we require any sdk integration to meet the following specifications we expect published artefacts in common package managers, without the need to manually include any library code for android, a published aar artefact in a maven repository, so that we can include it like this (using sourcepoint as an example) implementation 'com sourcepoint cmplibrary\ cmplibrary 7 1 0' this maven repository can be password protected if needed for ios, we use cocoapods, so we expect something like this to include the library pod 'consentviewcontroller', '7 1 0' actually, in our case it's included in a podspec instead of a pod file, since our app framework is a library, too sub dependency 'consentviewcontroller', '7 1 0' if you don't want to publish your source code publicly, it's also possible to publish a precompiled xcframework in a cocoapod, like consentmanager does for example (see https //github com/iubenda/cm sdk xcframework) since our app builds are running on various developer machines and in ci/cd runners, we cannot provide ssh keys here, especially since they can change over time (e g adding a new machine) to ensure smooth development, we also require a development environment it should be configured the same way as a generic production environment and enable us to verify proper functioning of our code and configuration