Zapp Mobile
Keeping a payment moving across devices.
Explain a new payment method and the handoff it requires.
I led UX and UI for Zapp’s mobile payment products, including a purchase that needed to continue in a banking app on another device.
The purchase can begin on a device without the required bank app.
The original R1 overlay addresses that specific state. A separate introduction explains paying from the phone through the bank account underneath it.
Changing devices can break the person’s understanding of the next step.
The handoff needs to explain why the journey moves, where to continue and which code to carry. The source designs establish this situation; they do not include measured abandonment or completion rates.
Explain the reason, then give the steps and the code together.
The original work uses one proposition and a Next action for the introduction, followed by numbered instructions for the cross-device handoff. Earlier alternatives are not included in the surviving archive.
Connect the introduction to a clearly explained handoff.
This reconstruction follows the original mobile introduction and R1 instructions. It does not invent payment completion, validation or transaction-history screens.
- A new payment concept
- No banking app on this device
- 01Explain the payment method
- 02Open the banking app elsewhere
- 03Select Zapp and enter the code
- A clear next step
- A cross-device handoff
The instructions and code remain together while the person continues on another device.
Keep the instruction available while the device changes.
The two reconstructed frames cover introduction and handoff. The displayed code is illustrative.
Make the product proposition readable
Keep the next device within the same journey
Reconstructed from the original Zapp introduction and LinkedIn R1 handoff presentation; the example code is illustrative.
Give the next device a clear role in the same journey.
The R1 instructions explain how to open the banking app, select Zapp and enter the displayed code. The original images below retain the source context; the utility-app image is a separate proof of concept.
The handoff design is documented; its success rate is not.
No participant study accompanies these recovered mockups. A useful evaluation would test whether people understand the device change and can carry the instruction and code across it.
A visible design response to a cross-device payment problem.
The original artifacts establish the introduction and handoff work. They do not establish a completed-payment outcome or a measured change in conversion.
Want to talk through the design decisions?