<?xml version="1.0" encoding="utf-8"?>

FlowPay - Mobile Onboarding Flow 1

FlowPay - Mobile Onboarding Flow 2

FlowPay - Mobile Onboarding Flow 3

FlowPay - Mobile Onboarding Flow 4

FlowPay - Mobile Onboarding Flow 5

-------------------------------------------------------------------------

Thank You

Tools used

Figma

From brief

Topics

Share

Share your insights — leave a project review and help others grow their skills

Reviews

4 reviews


Good job


Hi Sandeep!

From a product perspective, this onboarding flow feels streamlined and intentional. In fintech especially, first impressions matter users need to feel clarity and control from the start. The structure appears to guide them progressively rather than overwhelming them with too much information upfront.

I appreciate the apparent balance between explanation and action. Strong onboarding in financial apps isn’t about decoration it’s about reducing uncertainty. If the flow communicates value clearly while keeping steps manageable, that’s a solid strategic choice.

If I were refining it further, I’d examine moments of reassurance: data privacy cues, transparent step indicators, and clear expectations about what happens next. In payment-related products, trust is built in small details. Overall, this feels grounded and conversion-aware, with a good understanding of fintech onboarding principles.


I really like the idea of keeping FlowPay onboarding lightweight; the 3D icons work well, and the app value is clearly communicated.

That said, I’m wondering if there’s a tension between the goal of “minimal onboarding” and having three separate screens explaining key features. Even with a skip option, this might still feel like a lot of upfront information, especially for users who just want to start tracking quickly.

I also think the permission context is a strong and important moment, especially for a finance app. But if we offer a “Not now” option there, I’m curious about the intended next step. Can users still meaningfully use the app without connecting expenses? If yes, what does that experience look like? If not, what’s the risk of deferring that permission?

It would be great to see how onboarding connects to the next steps: permissions, sign-up, and the technical constraints behind them, to better understand the full user journey after onboarding ends.

Thank you Anastasiia, for your thoughtful feedback. To clarify one point: the three key features aren't separate screens, but rather swipeable cards within a single screen. That said, your point about the balance between "lightweight" and "value-led" onboarding still really resonates, and I'm rethinking how much education should happen upfront versus later in the product. On the permission side, your question helped me realize I needed to be clearer about the system behind the UI. If a user selects "Not now," they enter a manual mode, where they can still use the app by adding expenses themselves, which keeps the experience meaningful while gradually showing the value of connecting accounts later.
That makes a lot of sense, thanks for explaining the system behind it.

Congratulations, Sandeep Murmu — excellent work!


19 Claps
Average 3.8 by 5 people
5 claps
4 claps
3 claps
2 claps
1 claps
<?xml version="1.0" encoding="utf-8"?>