Skip to main content

Is the Mobile SDK right for you?

Q2 offers several tools for extending its platform. The Mobile SDK is the right one when your feature needs to run natively on the phone. Use this page to check your idea before you start building.

Quick check​

The Mobile SDK is a good fit if…

  • Your feature needs a native phone feature that Tecton doesn’t already offer, like rich notifications, device security checks, or a vendor’s native SDK.
  • You want a fully native screen or flow inside the Q2 Mobile App.
  • You need to react to app events, such as launch, login, or a notification arriving.

Look elsewhere if…

  • Your feature is a screen or widget inside online banking that should also work on desktop.
  • You need server-side logic, data storage, or an integration with a core or third-party system.
  • An outside system needs to read or write Q2 data.
  • Your online banking page only needs a basic phone feature Tecton already offers, like taking a photo or picking a contact.
  • You want to change Q2’s own built-in screens, or build a separate standalone app.

Do you need a module for that?​

Online banking pages can already use several phone features through Tecton, and the Q2 SDK can send standard push notifications. You only need a module when you go beyond them.

Push notificationsNo module neededStandard notifications. The device signs up through Tecton, and the Q2 SDK or Caliper API sends the message.Push notifications in the Q2 SDK Needs a moduleRich notifications with images or custom sounds, or opening a specific screen when tapped.
CameraNo module neededTake a photo or scan a QR code from an online banking page with Tecton.Tecton camera features Needs a moduleUsing the camera inside your own native screens.
ContactsNo module neededLet a customer pick a contact from their phone with Tecton.Tecton contact picker Needs a moduleUsually not needed.
Links and other appsNo module neededOpen a website, another app, or a universal link from online banking with Tecton.Tecton link and app features Needs a moduleBringing customers into the app from a link and straight to your feature (deep links).

What the Mobile SDK is not for​

If your need is one of these, the Mobile SDK is the wrong tool. Head to the right docs instead. If you're unsure, open a support ticket in the Q2 Developer Portal, not through standard Q2 technical support.

UI changes inside online bankingTecton Build screens, forms, and widgets that run inside online banking, on desktop and in the mobile app.Web or backend extensionsQ2 SDK Build extensions that run on the Q2 platform, connect to cores and third parties, and work with account data.An outside system that talks to Q2Caliper API Read and write Q2 data from your own systems through Q2’s API.
Many features combine tools

A fraud alert feature might use the Q2 SDK to spot unusual activity and send the alert, the Mobile SDK to add an image to the notification and open the right screen when it is tapped, and Tecton for the online banking page where the customer reviews it. Each tool handles the part it is built for.

Next steps​

From idea to production See each step from getting set up to going live in an FI’s app, on Android and iOS.