Asset Port

A mobile app that lets people pledge a vehicle they already own as collateral for Shariah-compliant financing, replacing an entirely paper-based process.

RoleProduct Designer
Year2025
Timeline1–3 months

Overview

I designed a mobile app that lets people pledge a vehicle they already own as collateral for Shariah-compliant financing, replacing an entirely paper-based process.

Problem

Islamic vehicle financing traditionally ran through a manual, paper-based process: in-person document collection, manual verification, and no visibility once a request was submitted. Asset Port set out to digitize this, with a twist — instead of financing a new vehicle purchase, users could pledge a vehicle they already owned as collateral.

  • No self-service way to register a vehicle. Every asset had to be logged manually at a branch before any financing conversation could start.
  • Zero visibility once submitted. Applicants had no way to see where their request stood or what was still needed, so status checks meant calling in.
  • Balances and limits lived off-app. Outstanding balance, available credit, and repayment dates weren’t visible anywhere a user could check on their own.

Standing balance at a glance, applications underneath

Surfaces outstanding balance, available limit, and next repayment date as soon as the user opens the app, with a running list of their applications and current status underneath. Returning users get their standing without digging through menus.

Balance, limit, and next repayment sit above the applications list, not behind a tab.

A vehicle registered once, reused across applications

Users register a vehicle by entering its registration, engine and chassis numbers, mileage, market value, and condition. Each asset gets its own detail view with verified fields, kept separate from any specific financing request so one vehicle can back more than one application.

Every field on a registered asset shows as independently verified before an application can start.

Named stages instead of a percentage bar

Each request moves through named stages — In Progress, Credit Offered, Final Review — shown as a step tracker rather than a generic progress bar. Every step lists the specific action needed at that stage, such as verifying identity or scheduling an assessment, alongside the estimated financing amount.

Each stage names its own next action instead of leaving the user to guess what happens next.

Credit limit as a gauge, not a table of numbers

Shows total credit limit as a radial gauge alongside outstanding balance, disbursement date, and next repayment due. Users withdraw approved funds straight to a linked bank account and scroll through recent transactions without leaving the screen.

The gauge answers "how much do I still have" before the user reads a single number.

Account upkeep kept apart from financing flows

Personal details, CNIC documentation, bank details, and notification preferences all live in one place, kept apart from the financing flows so account upkeep never gets tangled with an active application.

Notifications, documents, and bank details are grouped together, away from anything tied to an active loan.

Key Decisions

  • Separated asset registration from application submission. A vehicle is added to the user’s account independently of any financing request, so it can be reused across multiple applications instead of re-entered each time.
  • Used a named step tracker instead of a percentage bar. Financing approval involves distinct stages with different required actions, so showing the stages by name tells the user exactly what’s next rather than an abstract percentage.
  • Built the design system alongside the product, not ahead of it. With no existing UI foundation and a 1–3 month timeline, components were defined as each screen was built rather than as a separate upfront exercise.