Skip to main content

Why the Mobile SDK

The Mobile SDK gives FIs and partners a supported way to put native features inside Q2's mobile banking apps. This page covers what you get by building on it, and the kinds of features teams build most often.

Why use it?​

Reach customers where they already bank

Your feature lives inside the FI’s own app, the one customers already have on their phone.

  • No separate app to download
  • No extra login; modules work with the signed-in user
  • Build for iOS, Android, or both

Do what a web page can’t

Modules run natively on the phone, so they can go beyond what online banking pages can do.

  • Rich push notifications and deep links
  • Native vendor SDKs
  • Device security checks

Feels like part of the FI’s app

Modules pick up the FI’s look and language, so your feature feels built in rather than bolted on.

  • The FI’s theme colors and fonts
  • Access to the app’s translated text
  • Can be launched from online banking pages

Build once, offer to many FIs

Partners can make a released module available to any FI on Q2, not just one.

  • Listed in the Q2 developer Application Catalog
  • FIs request your module through the Marketplace Catalog
  • One module, many FI apps

Who does what​

Building on the Mobile SDK means you only own your feature. Q2 owns most of what's around it.

Q2 takes care of

  • Building and branding each FI’s app
  • Submitting the app to the App Store and Google Play, unless the FI handles this itself
  • Keeping the app current with new iOS and Android versions
  • Login, sessions, and the app’s built-in banking features
  • Reviewing your module, producing a test build, and releasing it

You focus on

  • The experience your feature delivers
  • Your business logic and any vendor integrations
  • Testing your module in the DevApp and the test build
  • Recording a walkthrough video for production sign-off
  • Keeping your module up to date with new Mobile SDK releases

Common use cases​

These are the kinds of features teams most often build with the Mobile SDK. Each card links to the developer guides for that feature.

Full native screens

Present your own native screens or multi-step flows inside the app, with full control over the experience. Usually opened from an online banking page built with Tecton.

OnboardingCard controlsRewards and loyaltyFinancial tools
Developer guides:AndroidiOS

Rich push notifications

Go beyond standard notifications: add images or custom sounds, and decide what happens when a customer taps one. Standard notifications don’t need a module.

Images in notificationsCustom soundsOpen a screen on tap
Developer guides:AndroidiOS

Deep links

Send customers straight to the right place in the app from an email, text message, website, or another app.

Email and SMS campaignsLinks from a websiteReturn from a partner app
Developer guides:AndroidiOS

React to app events

Run your logic at key moments, like when the app launches, comes back to the foreground, or a customer logs in or out.

Refresh data at loginClean up at logoutStart a vendor SDK at launch
Developer guides:AndroidiOS

Security and fraud checks

Run your own checks at sensitive moments, such as before login. If a check fails, the app blocks the action.

Device integrityTamper detectionCustom security rules
Developer guides:AndroidiOS

Native power for online banking

Let an online banking page ask the native app to do work, like calling a vendor’s native SDK, and get the result back.

Background API callsNative SDK calls from a web page
Developer guides:AndroidiOS

Vendor mobile SDKs

Bring a vendor’s native mobile SDK into the FI’s app, so customers get the vendor’s capabilities without leaving it.

Identity verificationAnalyticsChat and support
Developer guides:AndroidiOS

Next steps​

Is it right for you? Check whether your idea needs the Mobile SDK, or another Q2 tool.From idea to production Already know it fits? See each step from setup to going live.