Back to Projects
Remittance SDK – Alfardan Exchange icon

Remittance SDK – Alfardan Exchange

Technical Lead : Built the SDK using Flutter Plugin and Flutter Module architecture, entirely with Claude Code despite having no prior Flutter experience

FlutterFintechSDKClaude Code

Overview

A cross-platform remittance SDK built for Alfardan Exchange (UAE), letting partner apps embed beneficiary management, transfer flows, and transaction tracking without building remittance infrastructure themselves.

My Role

Technical Lead — sole engineer responsible for architecture, implementation, and delivery.

Problem

Alfardan Exchange needed to offer remittance services inside partner apps without every partner rebuilding compliance-heavy transfer flows from scratch, and it had to work regardless of each partner's own native stack.

Solution

A Flutter-based SDK using Flutter Plugin and Flutter Module architecture, so partner apps can embed the module as a drop-in unit — beneficiary management, transfer initiation, transaction tracking — instead of a rebuild.

Tech Stack

FlutterDartFlutter Plugin/Module architectureNative iOS/Android platform-channel bridgingClaude Code

Business Impact

Gives Alfardan Exchange a distributable remittance capability partner apps can integrate instead of building in-house.

Engineering Challenges

Two compounding constraints: zero production Flutter experience going in (core stack is React Native), and Flutter Module/Plugin embedding into third-party host apps is a materially different integration model than a standalone app. Used Claude Code to ramp on Flutter idioms and platform-channel bridging fast, while applying architecture judgment already built from React Native native-module work — the cross-platform mental model transferred even though the syntax didn't.

My Contributions

  • Sole technical lead: architecture, Flutter Plugin/Module setup
  • Beneficiary management, transfer, and tracking flows
  • Native iOS/Android bridging
  • End-to-end delivery

Why This Is Technically Impressive

Shipping a production SDK — a less forgiving integration surface than an app — in an unfamiliar framework, alone, is a strong proxy for how you perform on unfamiliar parts of any stack. It's a data point most React Native-only candidates can't offer: being the integration point other teams build on top of, not just a consumer of someone else's SDK.