Application Builds
Application Builds is the operational workspace for protecting compiled Android and iOS apps. Use it to upload a release candidate, apply a selected AppTego configuration, review build progress, download the protected output, and hand the artifact to QA or release automation.
Guides
| Guide | Use it to... |
|---|---|
| Uploading and Building Apps | Upload APK, AAB, or IPA files; understand build status; choose signing; download protected artifacts; and troubleshoot failures. |
| Custom Messages | Design the end-user messages shown when selected detection responses need to explain what happened and what the user should do next. |
Build Lifecycle
| Stage | Owner | Outcome |
|---|---|---|
| Configure | Security or app owner | A Development, Staging, or Production configuration is ready to apply. |
| Upload | Release engineer or CI job | AppTego receives an APK, AAB, or IPA and creates a build record. |
| Protect | AppTego | The selected configuration is applied and a protected artifact is produced. |
| Validate | QA or mobile team | The protected app is installed and tested on representative devices. |
| Release | Release owner | The protected artifact moves to app store, MDM, internal distribution, or downstream signing. |
Production Guidance
Temporary test signing is convenient for smoke tests and internal QA, but production releases should use your own signing identity. Treat every protected artifact like a release candidate: install it on real devices, exercise critical workflows, verify expected controls, and keep the original build job ID with your release notes.