What 'expert' has to mean before you pay for it
In a city full of people who can make an app icon appear, the expert is the one who can explain what happens when the payment gateway times out
Here is a test you can run on anyone in Rajshahi who calls themselves a mobile app development expert, before you transfer a taka. Ask them three things: what happens in your app if a user taps 'pay' on bKash and the network drops before the callback returns; how the app behaves when it is opened on a phone with no internet at all; and who holds the signing key for the Play Store release. A genuine expert answers all three in plain language in under a minute.
The wrapper-builder — the one who turned your website into an APK in an afternoon — goes quiet, because none of those questions have an answer in a WebView. That silence is the entire difference between expertise and an app icon, and it is exactly the difference Rajshahi buyers cannot see until it is too late.
Most of what is sold as 'app development' in this city is not app development. It is a website squeezed inside a thin native shell so it can be uploaded to the Play Store. It looks like an app on the home screen and falls apart the moment a user does anything real — no offline state, no push notifications, payment flows that lose orders when the gateway hiccups, and crashing on the low-RAM Symphony and Walton phones most of your customers actually carry.
Real mobile app development is architecture: deciding how data is stored on the device and synced back, how the app survives a dead connection, how a payment is confirmed even if the user closes the app mid-transaction. That is the work the word 'expert' is supposed to point at, and it is the work I do.
I am one senior operator, around five years building for the Bangladeshi market, and I do the whole thing myself — discovery, the screens in Figma, the actual code, the data model, the bKash and Nagad integration, the signed release, and the WhatsApp line you message when something misbehaves after launch. No agency layer, no project manager translating your problem to a junior and the junior's mistakes back to you.
Rajshahi's app briefs are shaped by what the city is — a serious education hub and silk-and-agriculture country — so I have built for the buyers it actually produces: coaching and admission-prep centres around RUET, Rajshahi University and the medical college that want student apps for routines, fees, attendance and results; mango and agro traders who want repeat buyers reordering before the season; clinics and diagnostic chambers wanting appointment and serial apps. One person accountable from scope to ship to the fix in month eight.
And the most expert thing I do is sometimes tell you not to build the app at all. If your real goal is people finding you, browsing and ordering from a phone, a fast installable web app will usually launch quicker, cost a fraction of a native build, and spare you maintaining two things — and in a city where people install almost nothing for local businesses, it often gets used more.
A native app earns its cost when there is a real repeated daily habit: a student opening the app every morning, a wholesale buyer reordering every week, a patient booking a serial. I will tell you which one you actually need on the first call, even when the website is the smaller invoice for me.
The pricing is published either way: from 50,000 BDT, tiers at 50,000 / 90,000 / 1,50,000 BDT, fully custom builds from 3,00,000 BDT, always 50% advance and 50% on launch via bKash, Nagad or bank transfer.
See pricing in BDT