Organizations use Appdome to automate the integration of 3rd-party services to mobile apps. Mobile DevOps teams use Appdome-DEV™ to better integrate Appdome in their Continuous Integration (CI) and Continuous Delivery (CD) processes and achieve an accelerated mobile app lifecycle.
This Knowledge Base article explains Appdome-DEV, the role it plays in CI/CD processes and how it offers DevOps an accelerated mobile app lifecycle workflow.
Appdome-DEV empowers mobile developers to customize, enhance and deploy their apps to public and private app stores and offers:
- All Appdome-GO Features PLUS
- CI/CD integration + Automated Integration Life Cycle
- Advanced Team Controls and App Approvals
- Flex-Release™ – shared templates and Fused-Apps
- Advanced Security Controls + DEV-Events
- Mobile Threat Control with a Mobile Threat subscription
- Encryption Control with a TOTALData Encryption subscription
- Session Control with a Secure Communication subscription
- Custom MFA Control with an MFA subscription
- Auto-Dev Private Signing
- Auto Deploy to public and private App-stores
We hope you find this knowledge base useful and enjoy using Appdome!
Prerequisites for using Appdome-DEV™
- Appdome account – IDEAL or Higher.
- Mobile App (.ipa for iOS, or .apk for Android) Have the app file available for Fusion on your computer.
- Appdome-DEV access
- Note – If you’d like to set up the build-to-publish API you will have to request API access
- Signing Credentials (e.g., signing certificates and provisioning profile)
- A CI/CD System for integration.
The Challenge of CI/CD in Mobile Apps
Mobile development and DevOps teams know that Continuous Integration (CI) and Continuous Delivery (CD) accelerate release cycles and improve mobile app delivery. Unfortunately, most CI/CD processes don’t account for the work needed to implement third-party SDKs, APIs, and services such as mobile security, enterprise authentication, mobility management and more. These services are typically outside the control of mobile developers and DevOps teams. If external services cause breaks as new versions of a mobile app are released, CI/CD stops. Even more likely, a new release of an API/SDK, or mobile operating system requires the integration to start from scratch, causing delays and disruption to CI/CD workflows.
Remove Mobile Integration From the Build
Appdome provides mobile developers and DevOps a no-code, mobile integration platform as a service (IPASS) to quickly add mobile services, SDKs and APIs into any Android and iOS mobile app in seconds – post build. There is no code or coding required. This enables anyone, including DevOps to integrate third-party services into mobile apps and complete projects themselves – with no dependencies on what’s coded inside the app.
Typically, mobile developers must work hard to add and maintain mobile SDK/API and third-party service in apps. Creating continuous integration and continuous delivery is the way to improve mobile app delivery speed and quality. With Appdome, the line-by-line, manual development work required to add SDK/APIs and other services to apps is gone. This also includes any required mobile standard, framework, method and workflow needed inside the mobile app. Bottom line, developers can simply build great apps, focusing their attention on the use case and user experience needed in the app. After building the app, anyone can use Appdome to automatically add third-party services as a final step in CI/CD processes.
Align Appdome With Existing Mobile Development Workflows
Development organizations invest heavily in CI/CD tools and creating unique CI/CD development cycles that meet their mobile app development needs. Appdome integrates with CI/CD tools including Jenkins, GitLab CI, TeamCity, Travis CI, Bamboo, CircleCI, Codeship, Codefresh, Azure DevOps and others. Organizationally, project managers and DevOps teams assign specific steps and responsibilities in the CI/CD workflow to specific experts. Ensuring that the right people are doing the right job accelerates the development cycle. Appdome is designed to integrate directly into existing CI/CD workflows at a platform and organizational level. Organizations can connect Appdome directly to build systems and assign integration responsibilities to different team-mates as needed.
Appdome-DEV Offers an Accelerated Mobile App Lifecycle Workflow
Appdome offers a CI/CD integration called Appdome-DEVTM. Appdome-DEV expands on Appdome’s no-code mobile integration capabilities to provide mobile development teams with all the tools needed to accelerate mobile integration lifecycles. Inside Appdome-DEV, developers will find mobile integration templates, teams, integration with build systems, automatic publishing and more. Appdome-DEV allows organizations to complete hundreds of simultaneous integrations, making Appdome the perfect complement to other CI/CD processes, systems and tools which enterprises already have deployed.
Key Benefits of Appdome-DEV
Below is a list of specific Appdome-DEV features which enable mobile development and DevOps teams to fully automate mobile integration and delivery projects and workflows:
Appdome-DEV provides RESTful APIs that connect with CI/CD automation software (such as Jenkins and other CI/CD tools). This enables organizations to remove SDK/API mobile integration from the build process and complete integrations post build automatically. Using Appdome’s Build-to-Publish API, developers automatically to push Android and iOS apps to Appdome directly from build systems and complete automatic jobs for any Fusion-Set created on Appdome. Appdome-DEV also offers the ability to automatically deploy Fused (integrated) apps to any public app store (like Apple’s AppStore or Google Play) or private app store (like Microsoft Intune, IBM MaaS360 or MobileIron).
Refer to this knowledge base article to learn how to use Build-to-Publish APIs.
End-to-End Integration Templates
Mobile developers and DevOps teams can create re-usable mobile integration templates, called Fusion Sets™ on Appdome. Fusion Sets allow organizations to add pre-defined information needed in each step in Appdome’s mobile integration workflow, including Fusion (integration) choices, mobile app Context™ (configuration and branding), app signing, and deployment. Fusion Sets can include any combination of third-party services, SDKs or APIs. Using Integration-Freeze™, a Team member can lock a Fusion Set for production use, guaranteeing that the approved Fusion Set will always be used by others. Organizations can subscribe one or more Android or iOS app to each Fusion Set, to complete end-to-end mobile integration lifecycles fast.
Refer to this knowledge base article to learn more about Mobile Integration Templates.
Mobile Integration Teams
Appdome Teams are collaborative workspaces allowing owners of specific organizational responsibilities to come together to complete mobile integration projects. For example, team members can include experts on development, security, IAM, delivery and other areas related to the mobile app lifecycle. Appdome supports two models of Teams: Organization (internal users only) and Open (internal and external users). For example, using the Open Team Model, an organization that builds mobile apps for customers, can invite the customer to become a member of the team so that they can add the right network configurations to the Fused app and sign it with their enterprise developer certificates. Appdome Teams are unique separate entities that exist in a secure, private, multi-tenant environment. Appdome-DEV teams offer structured collaboration with a designated team leader who can assign team member entitlements, and approve app integration workflows
Refer to this knowledge base article to learn how you can collaborate using Appdome Teams.
CI/CD entitlements ensure that each user sees and does what they are supposed to do. Appdome supports two entitlement models for teams: Collaborate or Manage. Collaborate allows team members to claim and assign responsibilities in an open flexible system of entitlements. This collaborative workflow empowers diverse functional areas to perform the work needed to release an app as needed per app. Manage allows a team leader to assign entitlements to different team members, according to their expertise for the different steps in the mobile integration workflow. For example, app-signing entitlements can be given to team members who are not part of the development organization. Manage also allows approvals of mobile integration and publication. Organizations can use different models for testing and production as needed to improve mobile app delivery.
Refer to this knowledge base article to learn how you can use Entitlements to collaborate on mobile integration projects.
Flex-Release™ – Copy Fusion Sets and Fused Apps
With Flex-Release, team leaders can copy Fusion Sets and Fused Apps into another team. This gives development teams the notion of an Appdome “Fusion-Sandbox”, a Team used as a mobile integration test environment. It also simplifies sharing of approved Fusion Sets and Fused Apps across the entire mobile development organization and therefore accelerates and automates the mobile integration process even more. With Flex-Release key members of the DevOps team can test and determine the correct integrations and share the approved Fusion Sets with other teams in production. Once in production, that Fusion Set is fully integrated into the automatic build system, without impacting the workload for the production DevOps team. Build-by-build, the organization can guarantee that the required third-party services are integrated into the app.
By creating different Teams for Testing and Production, the organization can achieve a true System Development Life Cycle (SDLC) integration process, where test and productions teams can only share data in a one-way approach.
Refer to this knowledge base article to learn more about Appdome Teams.
Advanced Security Controls and Appdome DEV-Events
Appdome DEV-Events can trigger developer lifecycle systems by integration-oriented activities such as fusion complete, ready to be published and more. As a result, Appdome delivers notifications for key integration workflow events so that other systems can be linked to the process. Examples of these triggers are: send emails, start automated processes, etc.
Refer to this knowledge base article to learn more about Appdome DEV-Events.
Mobile Threat Control with a Mobile Threat subscription
If you have a license for Mobile Threat Services, you will get access to Mobile Threat Control with Appdome-DEV.
Encryption Control with a TOTALData Encryption subscription
If you have a license for TOTALData Encryption, you will get access to Encryption Contro with Appdome-DEV.
Session Control with a Secure Communication subscription
If you have a license for Secure Communication, you will get access to Session Control with Appdome-DEV.
Custom MFA Control with MFA subscription
If you have a license for Appdome for MFA, you will get access to Custom MFA with Appdome-DEV.
Auto-DEV Private Signing
Signing iOS applications are required in order to install the applications on mobile devices. Many individuals sign within their development and integration platform, but some are required to sign the applications on designated computers in order to preserve the signing credentials within a trusted environment.
Appdome’s Auto-DEV private signing script allows users to sign fused apps locally without uploading the signing certificate to Appdome’s cloud service. The unsigned app is embedded in the script generated by Appdome. Running the script on your trusted environment will extract and sign the app using a certificate in your key chain.
Refer to this knowledge base article to learn more about Auto-Dev Private Signing.
Auto Deploy to Public and Private App Stores
With Appdome-DEV, mobile developers can auto deploy their Appdome-Fused apps to both public and private app stores.
Refer to these knowledge base articles to learn more about Auto Deploying to Public Appstores; Apple Appstore and Google Play Store and Auto Deploying to Private/Enterprise Appstores: Microsoft Intune, IBM MaaS360 and MobileIron.
Fusion History is very powerful for troubleshooting and auditing purposes. Throughout the integration workflow, it provides a complete history of all integration and deployment activities, available on a per app and per Fusion Set basis. This enables Appdome admins to view and audit the complete log history, seeing who did what during each step of the Fusion process. Fusion History also offers built-in versioning and indexing for everything users do on Appdome, such as uploaded apps, fused builds, fusion sets, signing activity and more. In addition, Integration Binding ensures that all activities related to published builds are fully trackable, using mechanisms like timestamps, fusions stamps, and audit stamps. Lastly, users can also access and re-integrate original app binaries to suit any mobile integration use case.
Refer to this knowledge base article to learn more about using Fusion History.
How Do I Learn More?
If you have any questions, please send them our way at email@example.com or via the chat window on the Appdome platform.
To zoom out on this topic, visit the Appdome Platform section on our website.
Thank You and Try Appdome!
Thanks for visiting Appdome! Our mission is to make mobile integration easy and offer mobile DevOps an accelerated mobile app lifecycle workflow. We hope we’re living up to the mission with your project. If you don’t already have an account, you can sign up for free.