iOS Engineer / Dhaka, Bangladesh
Ashiqur Rahman
I build iOS apps for about a hundred million people.
Seven years of it. Most recently Muslim Pro, where I moved the Quran from UIKit to SwiftUI. I tend to end up with the parts other people would rather not touch — migrations, monetization plumbing, the screen everybody is afraid to break.
Open to remote work (UTC+6)
Selected work
-
01
Lazy Staggered Grid
Muslim Pro's Inspiration feed wanted a Pinterest-style masonry layout. SwiftUI doesn't ship one, and the iOS versions we still supported didn't even have
LazyVGrid. So I wrote the layout myself, with pluggable chunking strategies so the balancing rule could change without touching a single call site — then lifted it out of the app and open-sourced it. It runs in production. -
02
The Quran, rebuilt in SwiftUI
I was first on the team to ship production SwiftUI, bridging new screens into a large existing UIKit navigation stack through
UIHostingController. Then I took on the Quran itself. The reader page is the most-used surface in the whole app, so I deliberately left it for last and migrated everything around it first — the unglamorous sequencing call that kept the risky part from becoming everybody's problem. -
03
Tripling ad revenue in three months
Our mediation wasn't filling well, so I wrote our own waterfall layer. Shipping it straight to the flagship would have been reckless, so it went out in phases — smallest titles first, then mid-tier, then the games that actually paid the bills. Three months later the ad revenue had tripled.
-
04
One framework, twenty-plus titles
Every new game re-integrated the same handful of SDKs by hand, badly and slightly differently each time. I built one integration layer for all of it and moved the studio's titles onto it. A new game went from days of plumbing to roughly two hours. Where an engine had no support, I wrote the bridge — Objective-C wrappers with C# interop, Android plugins in Java, and post-build Xcode and
Info.plistconfiguration that ran itself. -
05
Ummah Pro
A community layer inside a prayer app — posts, comments, reactions, sharing, profiles, enrollment. Mostly UIKit, with SwiftUI where it earned its place. I also built the Quran reading history and duration tracking, the Qalbox Courses rails, and the whole search experience for the Dua feature.
-
06
Picasso Pro
A text-to-image app built twice — once in SwiftUI, once in UIKit — so I could feel the difference between them rather than argue about it.
-
07
Games, on both stores
Police vs. Thief 3D, Sea Monster City, Shark Attack, Jurassic Sniper. I built the monetization, the analytics and the native iOS side of these — widgets, push and local notifications, in-app search, review prompts, haptics, StoreKit and Play Billing.
-
08
Privy
Opens a link — or whatever text you've selected — straight into a private tab. Tiny, and I use it constantly.
About
I like software that feels like someone was paying attention.
Most of what I do lives in the seams — bridging a legacy
completion-handler API to async/await, getting a SwiftUI
view to sit convincingly inside a UIKit stack, working out which half
of a migration to ship first. It's rarely the part anyone demos, and
it's usually the part that decides whether the demo works.
I've spent most of my career on apps with a lot of people on the other end of them, which has made me conservative about risk and stubborn about the small stuff. I use Claude Code and Gemini CLI daily, mostly to get to the interesting decisions faster.
Before iOS I shipped games, which is where I learned to care about frame budgets and about how quickly a bad integration compounds.
Contact
Say hello.
If you're building something for iOS and want another pair of hands on it — or you just want to argue about SwiftUI — I'd like to hear about it.