
Rauva WebApp
Designing Rauva’s cross-platform responsive Web App
Device
Desktop, Tablet, Mobile
Role
Product Design Lead
Special Note
Thanks Radek for your support as a PM.
Users began to voice frustrations about performing complex tasks like bookkeeping, accounting, and banking operations on mobile:
Limited visibility: Small screens made it hard to view detailed financial information and reports.
Lack of flexibility: Managing multiple tasks at once, as comparing transactions, reconciling accounts, doing bookkeeping felt cumbersome.
Inefficiency: Features optimized for mobile convenience weren’t scaling well for heavier operational needs.
B2B users often rely on desktops for critical workflows, as larger screens and multitasking capabilities directly impact productivity. Neglecting this context created a gap in their overall experience. It became clear that a responsive web app with optimized desktop and tablet experiences was essential to meet user needs and resolve these pain points.
As the main business priority for the quarter, the focus was on the Supercharged Users Plan (the most premium plan). The goal was to map a realistic redesign without compromising the user experience, recognizing that the approach for Desktop differs significantly from Mobile.
While mobile interfaces often reduce interactions to prioritize simplicity, my challenge was to take the opposite approach: scaling a mobile-first product to meet the heavier, more complex needs of desktop users. To tackle this, I conducted competitor analysis to understand key interfaces and user journeys.
Competitor Insights
The main inspirations (Revolut Business, Finom, Wise, Tiime, and QuickBooks) offered valuable lessons:
Data Visibility: Prioritized clear presentation of data, making it easy to access detailed reports and manage multiple workflows at once.
Simplified Operations: Streamlined tasks like invoicing and account reconciliation with clear, step-by-step flows.
User-Centric Features: Included customizable dashboards and integrated financial tools to address specific user needs and improve efficiency.
Tools like Mobbin allowed us to navigate quickly through competitors flows to understand the journeys.
UX Patterns and User Journey Prioritization
Once the main UX patterns and journeys were identified, I refined the navigation, focusing on the most critical user tasks. Working in bi-weekly sprints, the key sections of the redesign were:
Dashboard: A hub for main actions and an essential overview of the account and key tasks.
Banking Sections: Features for local and international transfers, bank card management, top-ups, and transaction history.
Business Toolkit: Tools for invoicing and bookkeeping reconciliation.
Accounting: Direct access to accountants, with document storage and sharing through the internal cloud.
Secondary Features: Support for Open Banking, multi-user access, customer support, and more.
Localizations: Full journey translation into Portuguese using Lokalise, ensuring accessibility for all target users.
This prioritization would evolve through the quarter, but it was my north star to be able to deliver in time.
Design critiques played a key role in ensuring we moved quickly while maintaining alignment across teams and stakeholders:
Involved engineers and product managers early to gather instant feedback and adapt the UX/UI on the fly
Fostered transparency and collaboration, with team members feeling actively involved in shaping the process
Held bi-weekly demos with the CEO and CTO to stay aligned with business objectives and validate our progress.
Maintained an open communication line to tackle the product’s core challenges and set the stage for user testing.
This process allowed us to move fast and stay focused while ensuring every decision was grounded in business and user needs.
During the design process, it became clear how essential it was to unify the component library. The WebApp redesign, with its refreshed interface, required a significant number of new components.
To streamline delivery and enable rapid iterations:
Components were first created locally and then imported into a unified component library.
We consolidated five separate component libraries into one, simplifying development and maintenance.
Over 50 new components were built, following an atomic design system to ensure consistency and scalability.