Skip to main content

Android - Publishing

Development and Release Process

This section explains the steps for developing and releasing mobile modules for Android. It walks through everything from setting up a sandbox to deploying the final product.

Request a Sandbox​

If your project repository in GitLab does not include the /android child repositories, these are essential for developing your Q2 Mobile SDK modules.

To gain access, submit a Mobile SDK case through q2developer.com requesting that the repositories be added to your project. These repositories contain the necessary tools and resources for building and testing your mobile extensions.

Development​

Once your sandbox is created and you have access to the Mobile SDK:

  1. Verify the presence of the Android repositories in your project.
  2. Use the provided Q2DevApp in these repositories to test your mobile extension during development.
  3. Develop your extension until it is complete and passes all development testing.
important
Branching Structure

You are free to use any branching structure during development.

  • master branch is protected and used for certification builds.
  • production branch is protected and used for production builds.

Certification​

Once development is complete and your extension is ready for testing within a Q2MobileApp:

  1. Submit a GitLab Merge Request from your branch to the master branch of the repository.

For Financial Institutions​

  • Q2 will review your code. Upon approval:

    • The Android app will be delivered to the /artifacts folder in the master branch.
    • The test app will point to the FI’s PTE environment (notify us if you need a different one).

  • If issues are identified:

    • Resolve them in your branch using the DevApp.
    • Submit a new Merge Request once resolved.

  • After verification:

For Partners​

  • Q2 will review your code. Upon approval:

    • The Android app will be delivered to the /artifacts folder in the master branch.
    • The test app will point to the Sales Demo Experimental (SDX) environment.

    If SDX credentials are required, request them through q2developer.com.

  • If issues are identified:

    • Resolve them using the DevApp.
    • Submit a new Merge Request after resolution.

  • After verification:

Production​

For Financial Institutions​

  • After receiving the SDK Deployment Request:
    • Q2 will merge the master branch into production. No need to create a Merge Request.
    • The module will be released with the specified version.
    • Q2 will build and submit the updated Q2 Mobile Applications to Apple and Google for review.

For Partners​

  • Submit a Merge Request from master to production.
  • Q2 will:
    • Approve the Merge Request.
    • Release your module with the specified version.
    • Prepare build systems for integration in requested FI builds.

If this is your first partner release:

  • Your onboarding process concludes here.
  • Your app will be listed in the Q2developer Application Catalog.

For updates to existing catalog apps:

  • No additional steps required.
  • FIs can request your module via the Marketplace Catalog.