Mobile Banking Apps with AR Navigation to Branches and ATMs

Summary

We build full-cycle mobile banking applications for iOS and Android, together with the mobile-shaped back end they depend on, and extend them with augmented-reality navigation to branches, ATMs and self-service terminals. This kind of engagement covers account information, transfers and payments, card and deposit management, exchange rates, two-step identification, an SMS fallback channel, and a camera-based wayfinding mode layered over a geocoded service point directory.

The Challenge

A banking application is judged on how much an account holder can finish without visiting a branch, but every one of those actions is a transaction against a core banking system with its own limits, cut-off times and error semantics. The application is a front end onto banking services rather than a self-contained product, and the hard problems live at the seams: a retried payment must never become two payments, and a balance shown in the interface must be one the core would agree with.

Security constraints pull in a second direction. Knowledge of a PIN on another handset must be useless, and notification content must never leak balances onto a lock screen. Hardening applied bluntly, such as per-operation session codes, costs more in daily friction than it adds in protection. Connectivity is a third constraint, because markets with unreliable mobile data still expect basic operations to work, and a fallback channel easily becomes the weakest link. Augmented reality adds sensor problems on top: magnetometer readings drift indoors and near vehicles, and satellite positioning accuracy varies block to block, so an overlay presented as certain will confidently point the wrong way.

The Solution

Architecture and the back end

Native iOS and Android applications paired with a purpose-built back end remain the standard shape. That back end is not a passthrough proxy: it aggregates core banking, card processing and payment gateways behind one mobile-shaped API, enforces its own limits and idempotency, holds device and session state, and shields the application from core outages.

• Device and session registry - activation binds an installation to an account holder, and revocation is immediate and central.
• Transaction service - idempotency keys, signed request payloads and a durable log, so a retry cannot duplicate a payment.
• Service point directory - geocoded ATMs, self-service terminals and banking centres with status, services offered and opening hours.

Security and offline fallback

Two-step identification is the baseline: a PIN bound to the application at activation combined with a device-held secret. Hardening extends to key material in the Secure Enclave or Android Keystore, certificate pinning, jailbreak and root detection, screenshot suppression on sensitive views, and no plaintext persistence of account data. SMS banking provides an offline path for basic operations, with a strict command grammar and its own authentication so the fallback is not the softest target.

Augmented-reality navigation

The AR view overlays the camera feed with a radar, a compass accuracy indicator and a directional arrow to the nearest chosen service point, updating distance as the person walks. Heading is fused from gyroscope and accelerometer rather than the magnetometer alone with confidence surfaced instead of implied, and points are filtered by radius and type so the overlay does not become a wall of markers. Because camera and location use drains battery, AR is entered deliberately, with a conventional map as the default.

How the work runs

We run the full cycle: requirements analysis, prototyping, design, implementation, testing, store release and ongoing support. Design favours a minimal interface, crisp contrast, configurable dashboards and short paths to frequent operations. Store review is unforgiving about permissions justification and authentication flows, so those are designed early, accessibility is treated as legal exposure, and releases include a forced-upgrade path so a security fix reaches installations.

What This Delivers

Account holders complete everyday banking without a branch visit, on a screen that stays legible and quick to navigate. The bank gains a channel it can extend without renegotiating core system access, alerts that inform without disclosing, and in-application feedback paths such as call-back requests and service point ratings. Finding a nearby branch or terminal becomes something done while walking rather than read from a list.

Technologies and Tools

Native iOS and Android development, a Java-based channel back end, augmented reality built on device camera, gyroscope, accelerometer, magnetometer and satellite positioning, Secure Enclave and Android Keystore for key storage, push notification and SMS gateways, and integrations with core banking, card processing and payment gateways.