Custom Library (BYOA)

The Custom Library card in Application Builds lets Enterprise tenants generate MobileDefender library artifacts configured for application identifiers. Use it for Library Mode integrations where your team embeds MobileDefender directly in source code instead of uploading a compiled app for Standard Mode protection.

Custom library generation is Enterprise-only. Team and Free tenants do not see the Custom Library card.

When To Use A Custom Library

Use a custom library when you need any of the following:

• Source-code integration: you want to call MobileDefender APIs directly from your app.
• Granular runtime control: your app needs custom callbacks, screen-specific behavior, or product-specific detection handling.
• Strict supply-chain requirements: your build pipeline must produce the final signed binary without post-build AppTego processing.

For most apps, Standard Mode is faster and easier. See Standard Mode before choosing Library Mode.

Setting an Application Identifier

Custom libraries are bound to application identifiers: Android package names or iOS bundle IDs. Choose identifiers carefully because generated artifacts are intended for those apps.

1. Open Application Builds.
2. Open the Custom Library card.
3. Select Add Identifier.
4. Enter the application identifier, such as com.company.myapp.
5. Save the identifier.
6. The portal queues library generation for Android and iOS variants.

Setting or changing an identifier requires the Modify Tenant Settings permission.

Identifier rules:

Enterprise tenants can configure multiple identifiers up to the tenant's custom-library identifier limit.

Build Status

The Custom Library page shows build status for each platform:

The portal displays friendly labels such as Generating, Download, and Failed. Builds are produced separately for each platform; one platform may complete before the other. Builds that remain stuck for more than about three hours time out.

Downloading the Library

When status is success, download buttons appear:

• Android produces a mobiledefender.aar file.
• iOS produces a MobileDefender.xcframework.zip archive.

Downloads use short-lived URLs. Click Download again if a previous URL expires.

Deleting a Custom Library

To stop making a generated library available in the portal, use Delete from the Custom Library card. Existing downloads already in your possession are not removed from your local systems; deletion affects future availability in the portal.

Successful builds have a 30-day per-platform cooldown before deletion is allowed.

Deleting requires the Build Applications permission.

Integrating the Downloaded Library

After downloading, follow Library Mode. That guide covers:

• Gradle and Xcode setup.
• Initialization.
• Detection, prevention, and integrity APIs.
• Platform requirements.

Release Guidance

1. Keep the downloaded library in your controlled dependency or artifact system.
2. Record which application identifier and AppTego tenant produced it.
3. Validate the integrated app in Development or Staging before production release.
4. Rebuild and retest your app after replacing the library.
5. Use Support and Help if a custom library build fails or the integrated app behaves unexpectedly.

Permissions Summary