Zaid Mubbasher
Senior iOS & Full-Stack Engineer - live App Store apps
New to Contra
Zaid is ready for their next project!
Three years on a live mobile-banking app taught me this: fintech iOS is less about fancy UI and more about trust under bad networks.
What actually matters in production😍
1. Offline-first for money f CoreData (or equivalent) so amount entry, beneficiaries and recent transfers still work when the radio drops mid-session. Users do not forgive a spinner over their salary.
2. Biometrics without trapping the session. Face ID / Touch ID should gate sensitive actions, not brick the app when the token refresh fails. Always keep a clean password fallback and clear session recovery.
3. Live rates and idempotent transfers. Exchange-rate widgets feel simple until a double-submit or a stale quote hits the ledger. Treat every payment tap as a once-only command with server-side idempotency keys.
I spent those years on UBL Tezraftaar — amount entry with live FX, payee management, quick transfers, KYC and biometric login — Swift, UIKit, MVVM, REST, in a regulated environment used by millions.
If you are scoping a fintech or payments mobile build, start with the failure modes, not the happy path. Happy to compare notes.
0
67
UBL Tezraftaar - mobile banking for a major Pakistani bank. Three years as iOS engineer on the customer-facing money-transfer journeys: amount entry with live exchange rate, beneficiary/payee management, quick transfers, KYC onboarding and biometric login, with CoreData offline caching so account and transaction data stays usable on poor connections. Swift, programmatic UIKit, MVVM and REST APIs, in a regulated, security-sensitive environment.
1
55
Spent this week wiring AI features into production iOS apps - chat assistants, document understanding, and voice-to-summary flows.
Three things make or break these integrations.
1. Never ship the API key in the binary. Extracting a hardcoded key from an IPA takes minutes - use a proxy or secure storage.
2. Stream the response. The same feature feels 10x faster when tokens render as they arrive instead of after a long spinner.
3. Cap the spend. Per-user token budgets keep the API bill predictable before the invoice surprises anyone.
I have been building fintech-grade iOS apps in Swift and SwiftUI for 5+ years. If you are weighing an AI feature for your app, happy to share what is realistic before you commit a budget.
1
73
UBL Tezraftaar - mobile banking for a major Pakistani bank. Three years as iOS engineer on the customer-facing money-transfer journeys: amount entry with live exchange rate, beneficiary/payee management, quick transfers, KYC onboarding and biometric login, with CoreData offline caching so account and transaction data stays usable on poor connections. Swift, programmatic UIKit, MVVM and REST APIs, in a regulated, security-sensitive environment.
1
76