While working on the UX/UI design for the charity section, my key challenge was to integrate a donation system into the bank’s ecosystem in a way that felt natural within the existing user experience. My goal was to embed donation opportunities into familiar banking scenarios — such as setting up recurring donations or allocating a portion of cashback — without disrupting the overall user flow. The first version of the feature was designed in less than two months.
I joined the bank when the product was far from what it is today: it was radically different and had limited capabilities. Back then, it was a fintech company with only basic app features allowing users to invest and save money.

User Journey
Tested various donation flow options:

• instant fixed-amount donations vs. setting up recurring contributions.
• Introduced a gamified system of achievements and rewards to encourage continued participation.
• Experimented with feedback formats — thank-you screens and messages highlighting the social impact of each donation.
• Onboarding experiments: A/B-tested a guided step-by-step tutorial with hints vs. a minimalist onboarding flow.

Main Navigation

• Explored different layouts for the main screen: a card-based interface focusing on visual charity stories vs. a list view of available initiatives.
• Tested alternative ways to present donation history: a visual analytics dashboard with graphs and category breakdowns vs. a traditional transaction list with short descriptions.

Charity as a Unique Feature

• Explored different donation mechanisms: rounding up payments, automatically donating a percentage of cashback, and setting up recurring subscriptions.
• Compared progress display formats: a collective counter showing all users’ donations vs. personal contribution statistics.
• Tested notification styles: immediate “Thank you for supporting this cause” messages vs. weekly summaries of total contributions.

Notifications & Feedback

• Timing of push notifications: instant (after each operation) vs. batched (daily or weekly).
• Tone of messages: neutral vs. emotionally driven (“You helped children get new books”).

• Loyalty and Retention:

Hypothesis: If users can see transparent reports showing how their donations directly support specific projects, they will return to the app more often and continue using it as their primary bank. Business goal: Increase user retention and extend customer lifetime value (LTV).

• Brand Perception and Advocacy

Hypothesis: If marketing communications highlight the bank’s social mission, customers will be more likely to recommend the product to friends and colleagues. Business goal: Drive organic app installs through referrals.

• Partnerships with Charities and Businesses

Hypothesis: By integrating a catalog of charities and donation projects into the app, the bank can attract partners willing to pay for promoting their initiatives within the banking ecosystem. Business goal: Create a new revenue stream through B2B partnerships.

The initial testing focused on integrating all key parts of the system to verify end-to-end functionality and identify “bottlenecks” — areas where the user flow was interrupted or included unnecessary steps: registration, identity verification, transfers, and payments.
Special attention was given to the charity system: users tested rounding up payments in favor of funds, setting up recurring donations, and viewing reports in their transaction history.

• Payment for a service with the option to round up the amount for a charity fund;
• Setting up a recurring donation (e.g., 1% of all card expenditures);
• Viewing a report of donations made in the transaction history;
• Receiving a “Thank you for your contribution” notification after a transaction.

Developed a design system from scratch for a mobile application, establishing a unified visual style and interface logic.
The system was built on the principles of the Human Interface Guidelines and included UI components, design tokens, typography, color palette, and rules for adaptability and interactions.
Created a well-structured component library in Figma using Auto Layout, which simplified interface maintenance and scaling.
The implementation of the design system standardized the product’s visual language, improved UX consistency, and enhanced overall team efficiency.

After analyzing the test results, the following user interaction scenarios were revised:
Refinement and improvement of notifications: 1.Configuring push notifications for transactions, account status, and new offers. 2.Determining the appropriate number of notifications to avoid overwhelming the user.

More flexible data entry: 1.Allowing users to easily edit contact information, addresses, and account details. 2.Enabling the addition of supplementary materials (e.g., uploading documents or photos for identification or transaction verification).

Optimization of operation parameters: Auto-filling frequently used details to speed up transactions.
After implementing these improvements, the next step could involve testing more complex scenarios: stress testing and personalization testing.