TreeInAPool
Case study · Fintech · 2024

Bill payments, from web app to both stores

Vuvu.ng, a bill payment product built for Baniri Technologies. A web app, wrapped and shipped for Android and iOS so it lives where people actually pay bills: on the phone, beside everything else they pay with.

Bill payments, from web app to both stores, screenshot of the live product
Client & context
Client

Baniri Technologies

Sector

Payments

Engagement

Client engagement

Duration

Sep 2024 to Sep 2025

Problem

Paying a bill is a phone task. It happens in a hurry, often on a poor connection, and usually from whatever is already installed. A web app alone asks someone to remember a URL and open a browser at exactly the moment they are least patient, which is a real amount of friction to put in front of a transaction that should take thirty seconds.

Phone-first usersNeeds a store presencePayments are unforgiving

Approach

01

One codebase, built for the web

A single web build to maintain and fix, rather than two native codebases drifting apart and needing every change made twice. For a product this size that is the difference between shipping and maintaining.

02

Wrapped for Android and iOS

The same product shipped into both app stores without a separate native rewrite for each platform. That is what put it on the home screen rather than in a bookmark nobody returns to. Version 1.0 was listed by Baniri Technologies Ltd on the App Store on 19 November 2024, with the Google Play listing alongside it.

Stack

Web applicationAndroidiOS

Working with us


You do. Repositories and accounts are transferred to you at launch, not licensed back to you.

A weekly demo on a live URL, plus an async channel for day-to-day questions. No status-report theatre. You see the actual product every sprint.

30 days of support are included with every full build. After that, a maintenance retainer is optional. Nothing is forced.

About two hours a week: one demo, plus decisions when a question is genuinely yours to answer. Everything else is our job.

Often, yes. It starts with an audit of what exists so nobody promises a timeline before reading the code.

Have a process that looks like this?

Bring the messy version. Thirty minutes on a call and you will have a scope, a price, and a date.