Designing Digital Confidence

e-Ledger: A Banking App for India’s Senior Citizens

An app with 3M+ downloads, 4.7 stars, aimed at Senior Citizens, for bridging old patterns into digital touch-points for a top government bank.

“If it’s too complex, I’m out of here.” — Lata, 58

The Brief

"Could you check my balance for me, please? I’ve rung twice and still haven’t got through."

That was something we heard more than once while doing early research in a local branch. And while the bank already had a feature-rich mobile app, it was clear that it wasn’t reaching everyone.

The request came from within the bank’s own IT team, where I was working at the time. The goal wasn’t to overhaul the bank’s main app. Instead, we were tasked with creating a simpler companion app for senior customers—those who often preferred in-person banking but were willing to try digital, as long as it didn’t feel intimidating.

Why it Mattered

Despite increasing smartphone usage in India (particularly among older users), many long-time customers still preferred visiting branches or phoning in for basic services—like checking a balance.

This created two issues:

  • Long wait times and overburdened staff at local branches.
  • A large segment of customers left out of digital transformation efforts.

We saw this not as a technology gap, but as a trust gap.

My Role

As a Product Designer in the IT team, I:

  • Synthesized insights from research, support logs, and branch interviews
  • Shaped user journeys and personas with our customer care team
  • Designed senior-friendly interfaces, accessibility features, and information architecture
  • Worked closely with internal dev teams to ship a functional MVP in just 8 weeks
  • Focused heavily on accessibility, localization, and family-use scenarios

Tools Used

Figma, Illustrator, Photoshop

The Approach

We used the GLE model to define our product vision:

  • Goal: Empower users to understand and manage their finances simply and confidently.
  • Leverage: Familiar banking concepts, minimalist UI, human-friendly language, habit-forming UX.
  • Evidence: Interviews with walk-in customers, support call logs, staff surveys, and usage data.

Research : Listening at branch level

Instead of making assumptions about "older users," we went straight to the source:

  • We visited local bank branches and spoke directly to walk-in customers.
  • We surveyed branch staff and call centre agents.
  • We analysed common customer service queries and frustrations.

What We Found

Working closely with frontline staff and customer support, we started by looking at logs, complaints, and stories from real users. We also visited a few branches and sat in on calls to observe common pain points.

What We Heard:

“I can’t remember the password rules, it’s all too much.”
"Why can’t my partner check the balance too?”

“I only want to see what’s gone in or out, nothing else.”
“I try to save, but I don’t know where the money goes each month.”

Some patterns stood out:

  • Login flows were too complicated—especially the need to remember passwords
  • The app was cluttered and slow, with features seniors didn’t want or understand
  • Seniors often used shared family phones, so secure multi-user access was important
  • Many didn’t want to “budget”—but were curious where their money was going
  • Visual clarity and plain language made a huge difference

Real Stories, Real People

We built around three core user types:

  • Lata (58): Tech-wary, prefers to do things herself, but gives up easily if stuck
  • Maya (62): Uses SMS banking, finds visuals easier than words
  • Neha (28): Daughter who helps her mother navigate apps

This helped us design with multi-generational use in mind, while staying senior-first.

Market Research

We looked at what other major Indian banks were doing:

  • Some had built similar “passbook” apps.
  • Others bundled everything into one large app.

We decided simpler was better. Our app focused only on day-to-day banking and financial awareness, not every possible feature.

Key Problems Identified

  • Login friction – Passwords were complicated, recovery even worse.
  • Single-device login – Prevented partners or family from sharing access.
  • Missing basic features – No easy way to track expenses or set budgets.
  • Long app loading times – Existing apps loaded slowly due to banners and offers.
  • Overwhelmed branches – Many in-person visits were avoidable with the right tool.

Our Goals

Our goals were both practical and emotional:

  • Enable customers to check balances and transactions without logging into the full app.
  • Reduce non-critical calls and footfall at branches.
  • Help seniors form a healthy digital relationship with their money.
  • Allow shared device access—like between spouses or family members.
  • Maintain security, while simplifying login (MPIN/fingerprint, not passwords).
  • Extend usability beyond seniors to include young adults or first-time digital users.

Designing for Familiarity, Not novelty

The app had one job: help users feel in control of their money.

Home Screen: Simple by Design, Built for Confidence

We kept the home screen calm and clutter-free — no flashy carousels, no pushy offers. Just simple, easy-to-read buttons stacked vertically for key actions:

  • Check Balance
  • View Transactions
  • Track my Spending
  • Budget Insights
  • Branch Calender

We also avoided financial jargon, using plain everyday language so users always know what each section does.

Sign-In Options

Through A/B testing, we tried:

  • Short alphanumeric password
  • MPIN (4-digit code)
  • Fingerprint login

MPIN and fingerprint were the clear winners—fast, secure, and easy to remember.

Designing the Budget Screens: Turning Confusion Into Clarity

One of the most frequently voiced concerns in our early research was around money “just disappearing.” Several users admitted they had little understanding of where their money was going each month. While they weren’t necessarily seeking complex financial tools, they craved visibility and control. We saw an opportunity here — not to overwhelm, but to gently introduce budgeting in a familiar, helpful way.

But designing a budgeting feature for a senior-first audience came with its own challenges. Traditional budgeting apps often rely on charts, categorization systems, and financial jargon. For many of our users, this language created a barrier rather than a bridge. So, we started with a simple question: What would budgeting look like if it felt like pen and paper — but better?

Our Goals Were Clear:

One of the most frequently voiced concerns in our early research was around money “just disappearing.” Several users admitted they had little understanding of where their money was going each month. While they weren’t necessarily seeking complex financial tools, they craved visibility and control. We saw an opportunity here — not to overwhelm, but to gently introduce budgeting in a familiar, helpful way.

But designing a budgeting feature for a senior-first audience came with its own challenges. Traditional budgeting apps often rely on charts, categorization systems, and financial jargon. For many of our users, this language created a barrier rather than a bridge.

So, we started with a simple question:

What would budgeting look like if it felt like pen and paper — but better?

  • Create an interface that visualizes spending, not just lists it.
  • Use plain language (“Food”, “Utilities”) rather than financial terms.
  • Keep actions intuitive — adding a budget, tracking spending — with as few steps as possible.
  • Offer gentle prompts to nudge healthy habits without being pushy.

Designed for Shared Trust

“Why can’t my partner check the balance too?”This was one of the most frequently asked questions during interviews with senior users. Many of them shared their phones with a spouse, adult child, or caregiver. Others had limited digital fluency and preferred that someone they trusted help with managing their finances.

To address this, we introduced a Shared Trust Access feature. Users could optionally add a secondary phone number—belonging to a family member or trusted person—who could then access the app in a read-only mode. This allowed both peace of mind and accountability, without compromising on security or autonomy.

We ensured that users were always in control of the feature:

  • The primary account holder receives a notification each time the secondary user accesses the app.
  • Secondary users cannot make changes, only view balance and transactions.
  • Access can be revoked at any time.

Settings were made accessible via a clear profile icon. Tap it, and you’d get a simple drawer with:

Settings Menu: Designed With Care

Settings were made accessible via a clear profile icon. Tap it, and you’d get a simple drawer with:

  • General Settings
  • Accessibility Settings
  • Call Support

Logically organized. Progressive Disclosure. Easy to understand at a glance.

Accessibility

Designing for seniors meant accessibility wasn’t a feature — it was a foundation. From the earliest wireframes, we made sure every interaction was comfortable and confidence-boosting.

We Included:

  • High-contrast themes for better readability in all lighting conditions
  • Adjustable text sizes, so users could enlarge content based on their comfort
  • Text-to-voice support for key screens, offering audible guidance
  • Simple sliders to change settings like brightness or text size without confusion
  • A clearly visible “Call Support” button on the home screen and settings menu — letting users quickly reach their local branch or call centre with one tap

Many of our users told us that even with all the technology, sometimes they just wanted to speak to someone. That insight shaped our decision to keep calling a human not only possible, but prominent.By listening to our users and building for their comfort, we weren’t just ticking boxes — we were earning trust.

Usability Testing

Designing for older adults means assuming less — and testing more. Once the early prototypes were in place, we moved into an intensive usability testing phase to identify not just technical issues, but cognitive and emotional blockers as well.

We ran a combination of:

  • Multivariate Testing – to compare different login flows (e.g., 4-digit MPIN vs. fingerprint vs. short alphanumeric passwords)
  • SUS (System Usability Scale) – to quantitatively gauge overall ease of use and confidence in using the app
  • Think-Aloud Protocols – participants were encouraged to verbalise their thought process as they navigated the app
  • Scenario-Based Testing – real-world tasks such as “Check your last 3 transactions” or “Set your monthly grocery budget”

Common Usability Issues Encountered

  • Unclear MPIN Requirements: Several users got stuck at the MPIN setup screen. The placeholder text did not specify the required number of digits, leading to confusion.Fix: We added helper text that clearly stated “Enter a 4-digit MPIN”.
  • Unfriendly Error Feedback: Error messages like “Invalid credentials” were not helpful.
    Fix: Reworded errors to be more human: “That didn’t work. Please check your MPIN and try again.”
  • Overlooked Support Option: While support was available, it wasn’t obvious on first glance.Fix: We added a persistent “Call Support” button at the top-right of the home and settings screens.
  • Financial Jargon Confusion: Terms like “Statement”,  or “Ledger” felt cold or unfamiliar.Fix: We used more intuitive phrasing like “Track My Spending” and, “View Transactions"
  • Small Tap Targets & Inconsistent Icons: Some icons (like settings or calendar) were too small or non-obvious.
    Fix: We increased the minimum tap target to 48x48 px and added labels to all icons.

Outcomes

  • The SUS scores improved from 58 to 84 over three iterations.
  • MPIN login and fingerprint scan emerged as the most preferred options from A/B testing.
  • Support call satisfaction (measured via feedback prompts) improved by 26% post-redesign.
  • 90% of users were able to complete common banking tasks without needing external help.
  • Small Tap Targets & Inconsistent Icons: Some icons (like settings or calendar) were too small or non-obvious.
    Fix: We increased the minimum tap target to 48x48 px and added labels to all icons.

The Impact

The app now has:

  • 3M+ downloads
  • 4.7-star rating on Play Store
  • 25% drop in balance-related branch calls
  • 20% fewer in-person walk-ins

More importantly, it helped real people feel comfortable managing their money.

Reflections

Designing for senior citizens isn’t about “dumbing things down.” It’s about understanding the rhythms of their lives, their unspoken hesitations, and designing with empathy and respect. Many of our users didn’t want full digital banking — just a simple way to feel in control.

This wasn’t a flashy app. It was a kind one.

“If it’s too complex, I’m out of here.”
— Lata, 58

We kept her in mind every step of the way.