SDK Integration
AppTego supports two mobile integration models: Standard Mode and Library Mode. Standard Mode protects a compiled app after your team builds it. Library Mode, also called Custom Library or BYOA integration, gives Enterprise teams a MobileDefender library to embed directly in source code.
Most teams should start with Standard Mode. Choose Library Mode only when your product or release process needs source-level control.
| Guide | Use it when |
|---|---|
| Standard Mode | You want AppTego to protect an uploaded APK, AAB, or IPA without source code changes. |
| Library Mode | You need an Enterprise custom library, detection callbacks, runtime control toggles, or final signing entirely inside your own pipeline. |
Choosing a Mode
| Requirement | Recommended mode |
|---|---|
| Protect an existing release binary without source changes. | Standard Mode |
| Add mobile protection to CI/CD quickly. | Standard Mode with the Automation API, GitHub Action, or CircleCI orb |
| Use AppTego post-build obfuscation and hardening. | Standard Mode |
| Keep final app compilation, signing, QA, and distribution in your own pipeline. | Library Mode |
| Route detection events into your own logging, messaging, or product logic. | Library Mode |
| Enable or disable controls from application code at runtime. | Library Mode |
Adoption Path
- Protect a QA build with Standard Mode.
- Validate installation, login, critical workflows, networking, and selected controls on representative physical devices.
- Move repeatable protection into CI/CD when the QA build is stable.
- Move to Library Mode only if your app needs source-level callbacks, custom runtime decisions, or final signing inside your own build pipeline.