100 days of learning English on Duolingo! 🦉💚
What started as a personal challenge became something even more special. From Day 50, my 6-year-old sister joined me on this journey, and since then, we’ve been learning and growing together. ❤️
100 days, countless lessons, and a lot of fun along the way 🚀📚
Day 32 of building Flow — my UI/UX design project 🚀
After a long break because I was sick, I’m finally restarting the Flow project from Day 32.
Today I worked on the review page and explored two different designs. The first version was shared previously, so I wanted to iterate on it and improve the overall hierarchy.
In the second version, I separated the message section because I felt that in the first version, too many elements were competing for attention. I also added a “Due now” badge to make it clearer what the first deposit refers to and what the client needs to pay at this stage.
I increased the spacing in the payment section as well. Since the information uses relatively small text, tighter spacing can make it harder to read and scan.
I also decided to keep the CTA at the bottom. The client needs to go through the important agreement, payment, and contract details before taking action. This encourages them to review the necessary information first instead of jumping straight to the CTA.
Which version do you think works better — Version 1 or Version 2? Or would you approach the page differently? Feel free to share your own Option C in the comments. 👇
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
I just watched “AI vs Manual Designing” by Saptarshi Prakash, and honestly, this is one of the most practical videos I’ve come across on AI and UX.
There’s a lot of AI hype right now. Some people are using AI for almost everything and thinking designers will be replaced, while others are still hesitant to adopt it.
I think the real answer is combining both.
One point from the video really stayed with me: AI can get you through the first 80% very quickly, but that final 20% can take much longer. And that 20% is where the details matter — those small UX decisions, edge cases, interactions, and refinements that make a product truly user-friendly.
That’s where I believe designers still play a huge role.
My ideal workflow would be something like:
User research → AI for exploration & first drafts → Refinement and manual design work → AI for further ideation → Manual evaluation & refinement
But throughout the entire process, the user should remain the priority.
We should start with user research, understand their problems and goals, and only then move toward solutions. AI should help us design faster, not think less.
Thank you, Saptarshi Prakash, for such an eye-opening video. As a UI/UX design student, it gave me a lot of clarity on how I should approach AI in my design process. 🙌
🎥 Watch the video:
I’ve made some major changes to my LinkedIn profile, and I’d love your honest feedback. 👀
I’m currently looking for UI/UX design internships and entry-level opportunities, so I’ve updated my profile to better reflect my skills, projects, and experience.
I’d really appreciate feedback from designers, recruiters, hiring managers, and fellow designers.
What should I improve, remove, or change?
Please be critical — I’m here to learn and improve. 🙌
🔗 My LinkedIn: https://www.linkedin.com/in/sayan-mondal-work/
I’m sharing my resume — and I’d genuinely love your criticism. 👀
I’m still learning and improving as a UI/UX designer, so there’s a good chance I’ve made mistakes in my resume that I’m not noticing myself.
I’m currently looking for UI/UX design internships and entry-level opportunities, and I want to make sure my resume communicates my skills and experience clearly.
So, if you’re a designer, recruiter, hiring manager, or someone experienced with resumes, I’d really appreciate your honest feedback.
What should I improve?
What feels unnecessary or unclear?
What would make you more likely to shortlist me?
Please don’t hesitate to criticise it — I’m here to learn. 🙌
Day 31 of building Flow — my UI/UX design project 🚀
Today, I worked on the agreement review page, and I’m still refining it.
I started with a personalized message, followed by the first deposit, project details, payment sequence, taxes, and contract.
For the payment section, I used a clear milestone-based layout to show the order of payments and make it easy to understand what comes next.
I also added “What your client will see” at the top so the sender can preview exactly what the client will receive. The goal is to keep both parties on the same page before signing.
Still working on it, so I’d love to hear your thoughts. 👇
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 30 of building Flow — my UI/UX design project 🚀
Today was mostly about iterations. I revisited several previous decisions, but one of the bigger changes was in the payment flow.
I changed the CTA placement to match the button placement across the other screens. It’s a small change, but it makes the overall design feel more consistent.
I’d love to know your thoughts — A or B? 👇
Apart from that, I created the signing screen and started working on the review page. I’m also revisiting some of my earlier UX decisions and making changes where needed.
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 29 of building Flow — my UI/UX design project 🚀
Today I created the screen that comes after all the agreement details are completed. It gives users a quick overview of everything they’ve added before reviewing the agreement.
I’ve created a few more screens as well — I’ll share those soon. 👀
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 28 of building Flow — sharing the design thinking behind the payment flows 🚀
Today, I created the taxation screen and made another round of iterations across both payment flows. After getting feedback from others, I wanted to share the reasoning behind some of the decisions I made.
For milestone payments, I connected each milestone with a vertical line and used an active state for the first milestone. This helps communicate the order of the milestones and which one needs to be paid first. I also placed the due date and amount at the top because they are the most important details when creating a milestone.
For hourly payments, I kept the structure simpler — hourly rate, maximum hours, start date, and end date. I aligned related fields together to make the information easier to scan. Below that, I kept the deliverables simple since they mainly communicate what will be delivered as part of the hourly work.
For taxation, I went with a country-based approach. The user can select their country and tax type, with the country flag helping make the selection easier to recognize. Since the user has already provided India as their nationality during account creation, I assumed India as the default tax country. Once tax details are added, I use a simple card to show the saved information with edit and delete actions.
Still refining, but the payment experience is starting to feel much more complete. 🚀
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 27 of building Flow — my UI/UX design project 🚀
Today, I finalized the hourly payment flow after a few rounds of exploration and iterations.
Another important part of the payment experience checked off. ✅
Follow the project:
Day 26 of building Flow — my UI/UX design project 🚀
It’s Sunday, so I spent most of the day relaxing. 😌 Still, I explored a few ideas for the hourly payment flow and made some progress.
Not every day has to be super productive — consistency matters too. 😅
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
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
Day 24 of building Flow — my UI/UX design project 🚀
Today I worked on the milestone payment flow and explored different ways to structure the milestone form. I created 3 different versions (A, B, and C) and I’d love your opinion:
Which one would you choose for Flow — A, B, or C? And why? 👇
The flow is still being iterated, so your feedback could help me decide the direction.
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 23 of building Flow — my UI/UX design project 🚀
I planned to finish the payment flow today, but due to some other work, I couldn’t get it done.
I did explore a few payment method ideas and created the first draft. The goal is to finish it tomorrow—no excuses. 😅
Follow the project:
Day 22 of building Flow — my UI/UX design project 🚀
Today, I iterated on the agreement creation flow, created new flows, and designed new screens.
Most of the flow is now complete. The payment flow is the only major part left, and I’ll work on it separately tomorrow because it needs more attention.
Once the payment flow is done, I’ll share the final screens and ask for your opinions and feedback.
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 21 of building Flow — my UI/UX design project 🚀
Today, I revisited the account creation experience and made a significant change.
Flow has 3 major steps: Personal information, Business information, and Identity verification, each with multiple sub-steps. I added a step indicator at the top of the screen, next to the progress bar, to show users exactly which major step they’re currently on. The previous version didn’t make this clear.
I also created the agreement creation overview, where payment is optional. In Flow, users can send an agreement with or without payment, and I’m still exploring the best way to communicate this.
I’d love to hear your thoughts: Does the new step indicator make the flow clearer? And how would you communicate optional payment? 👇
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 20 of building Flow — my UI/UX design project 🚀
Today, I continued working on the agreement creation flow and focused on iterations to make the experience clearer.
Nothing is completely finished yet, so just sharing a quick progress update. 😅
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 19 of building Flow — my UI/UX design project 🚀
Today, I continued working on the agreement creation flow and created more screens using my existing components.
The more I design, the more I realize how important iterations are. Things rarely feel right in the first attempt, and refining them is part of the process. 😅
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 18 of building Flow — my UI/UX design project 🚀
Not every day is super productive, and today was one of those days 😅
I spent most of my time wireframing the agreement creation flow, exploring different ideas, and working on a few screens.Slow progress is still progress.
Back at it tomorrow.
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 17 of building Flow — my UI/UX design project 🚀
Today, I started working on the agreement creation flow and got stuck on one small but important part: how should users add a client they’ve already worked with?
Instead of making them create the same client again, I wanted them to quickly find and select previous clients.
I created my first version based on my understanding, then asked ChatGPT, Claude, and Gemini to explore different approaches. I picked the direction that worked best for me and iterated on top of it.
This is how I like to use AI in my design process:
AI for iteration, not for the baseline or final decision.
I still want my own thinking to drive the design. If we simply accept whatever AI gives us, we stop questioning and thinking for ourselves.
Alongside this, I conducted 2 more user interviews with freelancers, which gave me more insights to consider as I move forward with Flow.
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Framer expert building high-converting, pixel-perfect websites.
100 days of learning English on Duolingo! 🦉💚
What started as a personal challenge became something even more special. From Day 50, my 6-year-old sister joined me on this journey, and since then, we’ve been learning and growing together. ❤️
100 days, countless lessons, and a lot of fun along the way 🚀📚
Day 32 of building Flow — my UI/UX design project 🚀
After a long break because I was sick, I’m finally restarting the Flow project from Day 32.
Today I worked on the review page and explored two different designs. The first version was shared previously, so I wanted to iterate on it and improve the overall hierarchy.
In the second version, I separated the message section because I felt that in the first version, too many elements were competing for attention. I also added a “Due now” badge to make it clearer what the first deposit refers to and what the client needs to pay at this stage.
I increased the spacing in the payment section as well. Since the information uses relatively small text, tighter spacing can make it harder to read and scan.
I also decided to keep the CTA at the bottom. The client needs to go through the important agreement, payment, and contract details before taking action. This encourages them to review the necessary information first instead of jumping straight to the CTA.
Which version do you think works better — Version 1 or Version 2? Or would you approach the page differently? Feel free to share your own Option C in the comments. 👇
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
I just watched “AI vs Manual Designing” by Saptarshi Prakash, and honestly, this is one of the most practical videos I’ve come across on AI and UX.
There’s a lot of AI hype right now. Some people are using AI for almost everything and thinking designers will be replaced, while others are still hesitant to adopt it.
I think the real answer is combining both.
One point from the video really stayed with me: AI can get you through the first 80% very quickly, but that final 20% can take much longer. And that 20% is where the details matter — those small UX decisions, edge cases, interactions, and refinements that make a product truly user-friendly.
That’s where I believe designers still play a huge role.
My ideal workflow would be something like:
User research → AI for exploration & first drafts → Refinement and manual design work → AI for further ideation → Manual evaluation & refinement
But throughout the entire process, the user should remain the priority.
We should start with user research, understand their problems and goals, and only then move toward solutions. AI should help us design faster, not think less.
Thank you, Saptarshi Prakash, for such an eye-opening video. As a UI/UX design student, it gave me a lot of clarity on how I should approach AI in my design process. 🙌
🎥 Watch the video:
I’ve made some major changes to my LinkedIn profile, and I’d love your honest feedback. 👀
I’m currently looking for UI/UX design internships and entry-level opportunities, so I’ve updated my profile to better reflect my skills, projects, and experience.
I’d really appreciate feedback from designers, recruiters, hiring managers, and fellow designers.
What should I improve, remove, or change?
Please be critical — I’m here to learn and improve. 🙌
🔗 My LinkedIn: https://www.linkedin.com/in/sayan-mondal-work/
I’m sharing my resume — and I’d genuinely love your criticism. 👀
I’m still learning and improving as a UI/UX designer, so there’s a good chance I’ve made mistakes in my resume that I’m not noticing myself.
I’m currently looking for UI/UX design internships and entry-level opportunities, and I want to make sure my resume communicates my skills and experience clearly.
So, if you’re a designer, recruiter, hiring manager, or someone experienced with resumes, I’d really appreciate your honest feedback.
What should I improve?
What feels unnecessary or unclear?
What would make you more likely to shortlist me?
Please don’t hesitate to criticise it — I’m here to learn. 🙌
Day 31 of building Flow — my UI/UX design project 🚀
Today, I worked on the agreement review page, and I’m still refining it.
I started with a personalized message, followed by the first deposit, project details, payment sequence, taxes, and contract.
For the payment section, I used a clear milestone-based layout to show the order of payments and make it easy to understand what comes next.
I also added “What your client will see” at the top so the sender can preview exactly what the client will receive. The goal is to keep both parties on the same page before signing.
Still working on it, so I’d love to hear your thoughts. 👇
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 30 of building Flow — my UI/UX design project 🚀
Today was mostly about iterations. I revisited several previous decisions, but one of the bigger changes was in the payment flow.
I changed the CTA placement to match the button placement across the other screens. It’s a small change, but it makes the overall design feel more consistent.
I’d love to know your thoughts — A or B? 👇
Apart from that, I created the signing screen and started working on the review page. I’m also revisiting some of my earlier UX decisions and making changes where needed.
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 29 of building Flow — my UI/UX design project 🚀
Today I created the screen that comes after all the agreement details are completed. It gives users a quick overview of everything they’ve added before reviewing the agreement.
I’ve created a few more screens as well — I’ll share those soon. 👀
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 28 of building Flow — sharing the design thinking behind the payment flows 🚀
Today, I created the taxation screen and made another round of iterations across both payment flows. After getting feedback from others, I wanted to share the reasoning behind some of the decisions I made.
For milestone payments, I connected each milestone with a vertical line and used an active state for the first milestone. This helps communicate the order of the milestones and which one needs to be paid first. I also placed the due date and amount at the top because they are the most important details when creating a milestone.
For hourly payments, I kept the structure simpler — hourly rate, maximum hours, start date, and end date. I aligned related fields together to make the information easier to scan. Below that, I kept the deliverables simple since they mainly communicate what will be delivered as part of the hourly work.
For taxation, I went with a country-based approach. The user can select their country and tax type, with the country flag helping make the selection easier to recognize. Since the user has already provided India as their nationality during account creation, I assumed India as the default tax country. Once tax details are added, I use a simple card to show the saved information with edit and delete actions.
Still refining, but the payment experience is starting to feel much more complete. 🚀
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 27 of building Flow — my UI/UX design project 🚀
Today, I finalized the hourly payment flow after a few rounds of exploration and iterations.
Another important part of the payment experience checked off. ✅
Follow the project:
Day 26 of building Flow — my UI/UX design project 🚀
It’s Sunday, so I spent most of the day relaxing. 😌 Still, I explored a few ideas for the hourly payment flow and made some progress.
Not every day has to be super productive — consistency matters too. 😅
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
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
Day 24 of building Flow — my UI/UX design project 🚀
Today I worked on the milestone payment flow and explored different ways to structure the milestone form. I created 3 different versions (A, B, and C) and I’d love your opinion:
Which one would you choose for Flow — A, B, or C? And why? 👇
The flow is still being iterated, so your feedback could help me decide the direction.
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 23 of building Flow — my UI/UX design project 🚀
I planned to finish the payment flow today, but due to some other work, I couldn’t get it done.
I did explore a few payment method ideas and created the first draft. The goal is to finish it tomorrow—no excuses. 😅
Follow the project:
Day 22 of building Flow — my UI/UX design project 🚀
Today, I iterated on the agreement creation flow, created new flows, and designed new screens.
Most of the flow is now complete. The payment flow is the only major part left, and I’ll work on it separately tomorrow because it needs more attention.
Once the payment flow is done, I’ll share the final screens and ask for your opinions and feedback.
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 21 of building Flow — my UI/UX design project 🚀
Today, I revisited the account creation experience and made a significant change.
Flow has 3 major steps: Personal information, Business information, and Identity verification, each with multiple sub-steps. I added a step indicator at the top of the screen, next to the progress bar, to show users exactly which major step they’re currently on. The previous version didn’t make this clear.
I also created the agreement creation overview, where payment is optional. In Flow, users can send an agreement with or without payment, and I’m still exploring the best way to communicate this.
I’d love to hear your thoughts: Does the new step indicator make the flow clearer? And how would you communicate optional payment? 👇
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 20 of building Flow — my UI/UX design project 🚀
Today, I continued working on the agreement creation flow and focused on iterations to make the experience clearer.
Nothing is completely finished yet, so just sharing a quick progress update. 😅
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 19 of building Flow — my UI/UX design project 🚀
Today, I continued working on the agreement creation flow and created more screens using my existing components.
The more I design, the more I realize how important iterations are. Things rarely feel right in the first attempt, and refining them is part of the process. 😅
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 18 of building Flow — my UI/UX design project 🚀
Not every day is super productive, and today was one of those days 😅
I spent most of my time wireframing the agreement creation flow, exploring different ideas, and working on a few screens.Slow progress is still progress.
Back at it tomorrow.
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 17 of building Flow — my UI/UX design project 🚀
Today, I started working on the agreement creation flow and got stuck on one small but important part: how should users add a client they’ve already worked with?
Instead of making them create the same client again, I wanted them to quickly find and select previous clients.
I created my first version based on my understanding, then asked ChatGPT, Claude, and Gemini to explore different approaches. I picked the direction that worked best for me and iterated on top of it.
This is how I like to use AI in my design process:
AI for iteration, not for the baseline or final decision.
I still want my own thinking to drive the design. If we simply accept whatever AI gives us, we stop questioning and thinking for ourselves.
Alongside this, I conducted 2 more user interviews with freelancers, which gave me more insights to consider as I move forward with Flow.
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
100 days of learning English on Duolingo! 🦉💚
What started as a personal challenge became something even more special. From Day 50, my 6-year-old sister joined me on this journey, and since then, we’ve been learning and growing together. ❤️
100 days, countless lessons, and a lot of fun along the way 🚀📚
Day 32 of building Flow — my UI/UX design project 🚀
After a long break because I was sick, I’m finally restarting the Flow project from Day 32.
Today I worked on the review page and explored two different designs. The first version was shared previously, so I wanted to iterate on it and improve the overall hierarchy.
In the second version, I separated the message section because I felt that in the first version, too many elements were competing for attention. I also added a “Due now” badge to make it clearer what the first deposit refers to and what the client needs to pay at this stage.
I increased the spacing in the payment section as well. Since the information uses relatively small text, tighter spacing can make it harder to read and scan.
I also decided to keep the CTA at the bottom. The client needs to go through the important agreement, payment, and contract details before taking action. This encourages them to review the necessary information first instead of jumping straight to the CTA.
Which version do you think works better — Version 1 or Version 2? Or would you approach the page differently? Feel free to share your own Option C in the comments. 👇
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
I just watched “AI vs Manual Designing” by Saptarshi Prakash, and honestly, this is one of the most practical videos I’ve come across on AI and UX.
There’s a lot of AI hype right now. Some people are using AI for almost everything and thinking designers will be replaced, while others are still hesitant to adopt it.
I think the real answer is combining both.
One point from the video really stayed with me: AI can get you through the first 80% very quickly, but that final 20% can take much longer. And that 20% is where the details matter — those small UX decisions, edge cases, interactions, and refinements that make a product truly user-friendly.
That’s where I believe designers still play a huge role.
My ideal workflow would be something like:
User research → AI for exploration & first drafts → Refinement and manual design work → AI for further ideation → Manual evaluation & refinement
But throughout the entire process, the user should remain the priority.
We should start with user research, understand their problems and goals, and only then move toward solutions. AI should help us design faster, not think less.
Thank you, Saptarshi Prakash, for such an eye-opening video. As a UI/UX design student, it gave me a lot of clarity on how I should approach AI in my design process. 🙌
🎥 Watch the video:
I’ve made some major changes to my LinkedIn profile, and I’d love your honest feedback. 👀
I’m currently looking for UI/UX design internships and entry-level opportunities, so I’ve updated my profile to better reflect my skills, projects, and experience.
I’d really appreciate feedback from designers, recruiters, hiring managers, and fellow designers.
What should I improve, remove, or change?
Please be critical — I’m here to learn and improve. 🙌
🔗 My LinkedIn: https://www.linkedin.com/in/sayan-mondal-work/
I’m sharing my resume — and I’d genuinely love your criticism. 👀
I’m still learning and improving as a UI/UX designer, so there’s a good chance I’ve made mistakes in my resume that I’m not noticing myself.
I’m currently looking for UI/UX design internships and entry-level opportunities, and I want to make sure my resume communicates my skills and experience clearly.
So, if you’re a designer, recruiter, hiring manager, or someone experienced with resumes, I’d really appreciate your honest feedback.
What should I improve?
What feels unnecessary or unclear?
What would make you more likely to shortlist me?
Please don’t hesitate to criticise it — I’m here to learn. 🙌
Day 31 of building Flow — my UI/UX design project 🚀
Today, I worked on the agreement review page, and I’m still refining it.
I started with a personalized message, followed by the first deposit, project details, payment sequence, taxes, and contract.
For the payment section, I used a clear milestone-based layout to show the order of payments and make it easy to understand what comes next.
I also added “What your client will see” at the top so the sender can preview exactly what the client will receive. The goal is to keep both parties on the same page before signing.
Still working on it, so I’d love to hear your thoughts. 👇
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 30 of building Flow — my UI/UX design project 🚀
Today was mostly about iterations. I revisited several previous decisions, but one of the bigger changes was in the payment flow.
I changed the CTA placement to match the button placement across the other screens. It’s a small change, but it makes the overall design feel more consistent.
I’d love to know your thoughts — A or B? 👇
Apart from that, I created the signing screen and started working on the review page. I’m also revisiting some of my earlier UX decisions and making changes where needed.
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 29 of building Flow — my UI/UX design project 🚀
Today I created the screen that comes after all the agreement details are completed. It gives users a quick overview of everything they’ve added before reviewing the agreement.
I’ve created a few more screens as well — I’ll share those soon. 👀
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 28 of building Flow — sharing the design thinking behind the payment flows 🚀
Today, I created the taxation screen and made another round of iterations across both payment flows. After getting feedback from others, I wanted to share the reasoning behind some of the decisions I made.
For milestone payments, I connected each milestone with a vertical line and used an active state for the first milestone. This helps communicate the order of the milestones and which one needs to be paid first. I also placed the due date and amount at the top because they are the most important details when creating a milestone.
For hourly payments, I kept the structure simpler — hourly rate, maximum hours, start date, and end date. I aligned related fields together to make the information easier to scan. Below that, I kept the deliverables simple since they mainly communicate what will be delivered as part of the hourly work.
For taxation, I went with a country-based approach. The user can select their country and tax type, with the country flag helping make the selection easier to recognize. Since the user has already provided India as their nationality during account creation, I assumed India as the default tax country. Once tax details are added, I use a simple card to show the saved information with edit and delete actions.
Still refining, but the payment experience is starting to feel much more complete. 🚀
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 27 of building Flow — my UI/UX design project 🚀
Today, I finalized the hourly payment flow after a few rounds of exploration and iterations.
Another important part of the payment experience checked off. ✅
Follow the project:
Day 26 of building Flow — my UI/UX design project 🚀
It’s Sunday, so I spent most of the day relaxing. 😌 Still, I explored a few ideas for the hourly payment flow and made some progress.
Not every day has to be super productive — consistency matters too. 😅
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
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
Day 24 of building Flow — my UI/UX design project 🚀
Today I worked on the milestone payment flow and explored different ways to structure the milestone form. I created 3 different versions (A, B, and C) and I’d love your opinion:
Which one would you choose for Flow — A, B, or C? And why? 👇
The flow is still being iterated, so your feedback could help me decide the direction.
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 23 of building Flow — my UI/UX design project 🚀
I planned to finish the payment flow today, but due to some other work, I couldn’t get it done.
I did explore a few payment method ideas and created the first draft. The goal is to finish it tomorrow—no excuses. 😅
Follow the project:
Day 22 of building Flow — my UI/UX design project 🚀
Today, I iterated on the agreement creation flow, created new flows, and designed new screens.
Most of the flow is now complete. The payment flow is the only major part left, and I’ll work on it separately tomorrow because it needs more attention.
Once the payment flow is done, I’ll share the final screens and ask for your opinions and feedback.
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 21 of building Flow — my UI/UX design project 🚀
Today, I revisited the account creation experience and made a significant change.
Flow has 3 major steps: Personal information, Business information, and Identity verification, each with multiple sub-steps. I added a step indicator at the top of the screen, next to the progress bar, to show users exactly which major step they’re currently on. The previous version didn’t make this clear.
I also created the agreement creation overview, where payment is optional. In Flow, users can send an agreement with or without payment, and I’m still exploring the best way to communicate this.
I’d love to hear your thoughts: Does the new step indicator make the flow clearer? And how would you communicate optional payment? 👇
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 20 of building Flow — my UI/UX design project 🚀
Today, I continued working on the agreement creation flow and focused on iterations to make the experience clearer.
Nothing is completely finished yet, so just sharing a quick progress update. 😅
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 19 of building Flow — my UI/UX design project 🚀
Today, I continued working on the agreement creation flow and created more screens using my existing components.
The more I design, the more I realize how important iterations are. Things rarely feel right in the first attempt, and refining them is part of the process. 😅
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 18 of building Flow — my UI/UX design project 🚀
Not every day is super productive, and today was one of those days 😅
I spent most of my time wireframing the agreement creation flow, exploring different ideas, and working on a few screens.Slow progress is still progress.
Back at it tomorrow.
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
Day 17 of building Flow — my UI/UX design project 🚀
Today, I started working on the agreement creation flow and got stuck on one small but important part: how should users add a client they’ve already worked with?
Instead of making them create the same client again, I wanted them to quickly find and select previous clients.
I created my first version based on my understanding, then asked ChatGPT, Claude, and Gemini to explore different approaches. I picked the direction that worked best for me and iterated on top of it.
This is how I like to use AI in my design process:
AI for iteration, not for the baseline or final decision.
I still want my own thinking to drive the design. If we simply accept whatever AI gives us, we stop questioning and thinking for ourselves.
Alongside this, I conducted 2 more user interviews with freelancers, which gave me more insights to consider as I move forward with Flow.
Follow the project: https://www.figma.com/design/a9BOd8eltqp038l6LkToHb/Flow---Fintech-App?node-id=394-2459&t=8VLXpCbYSlSdCzDF-1
