Day 25 of building Flow — my UI/UX design project šŸš€ Yesterday, I shared three different options ...Day 25 of building Flow — my UI/UX design project šŸš€ Yesterday, I shared three different options ...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Day 25 of building Flow — my UI/UX design project šŸš€ Yesterday, I shared three different options (A, B, and C) for the milestone payment flow. Today, I came up with a completely different approach — Option D. What do you think about this version? I’d love to hear your thoughts and which version you would choose. šŸ‘‡ Now, I’m working on the hourly payment flow. Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Rohan's avatar
pro
• 5h
Option D is a smart iteration because it simplifies the payment decision without losing the surrounding context. The stronger contrast on the primary action should help users scan the next step faster; I’d keep validating the copy length at mobile widths.
Sayan's avatar
Thank you! I’ll keep checking the copy length at mobile widthsšŸ™Œ
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started