SDK Integration - Standard Mode

Overview

Standard Mode is the default way to protect a mobile app with AppTego. Upload a compiled APK, AAB, or IPA and AppTego applies MobileDefender protection according to the selected security configuration. No source code changes are required.

Use Standard Mode when you are evaluating AppTego, protecting an existing release candidate, or moving protection into CI/CD. The protected app should behave like the original app with the selected security controls active, but every protected artifact should be validated before release.

How It Works

1. Configure controls and response actions in the AppTego Portal.
2. Upload the compiled app through the portal, a CI/CD integration, or the Automation API.
3. AppTego protects, packages, and signs the app according to the selected configuration and signing option.
4. Download the protected output when the build completes.
5. Validate the protected app on representative devices.
6. Distribute through your normal release channel after QA approval.

Supported Formats

Upload Via The Portal

1. Open Application Builds in the sidebar.
2. Click Upload.
3. Select Android or iOS.
4. Choose the configuration version: Development, Staging, or Production.
5. Select the APK, AAB, or IPA file.
6. Select a signing key when the build should use customer signing material.
7. Click Upload.

The build appears in the Application Builds list with a live status indicator. When complete, download the protected artifact from the build record.

Upload Via CI/CD

For repeatable CI/CD integration, use one of these paths:

Build Limits

Default build and application limits depend on your subscription plan. Contract-specific or support-configured limits can override these defaults.

Build history, retention, signing, and detailed build behavior are covered in Uploading and Building Apps. Plan details are covered in Subscription Plans and Billing.

What Standard Mode Applies

During protected build creation, AppTego can apply the selected configuration, including:

1. MobileDefender runtime protection.
2. Detection controls and configured response actions.
3. Prevention controls and platform hardening.
4. AppTego obfuscation and build-time hardening supported by the tenant plan and platform.
5. Protected configuration packaging for the selected environment.
6. Signing using the selected signing key or temporary test signing.

Controls are plan-gated at configuration and build time. Many controls are build-time protections, so changing a configuration usually requires a new protected build before the app contains that change.

Signing

If no custom signing key is selected, AppTego can produce an installable test build using temporary signing. Temporary test signing is useful for QA and smoke testing, but it is not intended for app store distribution.

For production workflows, upload and select your own signing identity:

1. Open Application Builds.
2. Add the Android or iOS signing material in the Signing Keys panel.
3. Select the signing key during upload, or set it as the default for future builds.

Custom signing keys are available on paid plans. Always validate that the protected artifact uses the expected signing identity for its distribution path.

Architecture Settings

Standard Mode protected outputs are device-focused by default. Enterprise tenants can enable optional build settings for Android x86/x86_64 support or iOS simulator support when QA or CI needs emulator/simulator installation. See Uploading and Building Apps for the current portal settings and tradeoffs.

Validation Checklist

Comparison with Library Mode

For source-level setup, see Library Mode.