Manage wealth on hand and collaborate with your advisors
Access the tools you need to manage your wealth and collaborate with your advisor.
.png)
The client portal app is designed to provide clients with easy access to manage their wealth and collaborate with their advisors. This app offers a suite of tools necessary for wealth management, allowing for a seamless mobile experience for all financial and investment needs
After Orion's acquisition of the Advizr (now Orion Planning) platform, the primary focus was to bring Orion investment data into the desktop experience of our white-labeled client portal, which our clients (the investment advisors) brand and distribute to their clients. Therefore, there was a new acquisition called for a new mobile app in this project.
I played a key role throughout the project, from defining the problem and conducting user provocations to designing, collaborating with engineers, and testing builds for quality assurance.
The primary focus was to bring Orion investment data into the desktop experience of our white-labeled client portal, which our clients (the investment advisors) brand
The challenge of ensuring consistency in the desktop and mobile experience with a newly formed design system can be effectively managed, leading to a more cohesive and user-friendly product.
Build a MVP experience and give clients a fully branded, one-stop-shop for all of their financial needs.
After I conducted some initial discovery research around the legacy mobile app, I was able to gather some valuable insights into its current functionality, user engagement, and areas requiring improvement.
Before I started, there were two key challenges: the missing mobile design system and the 3-month time constraints. We had to innovate without a pre-existing mobile design system, working towards a solution that would make complex financial data comprehensible and manageable on smaller screens.
To accelerate development and maintain visual consistency, I adapted the existing web design system for mobile. This allowed us to reuse core components while customizing interactions and layouts for smaller screens and touch gestures. Working closely with engineering, we prioritized mobile-first usability without duplicating effort.
I create information hierarchy based on high adoption involves organizing content or data in a way that prioritizes the most widely adopted or important aspects at the top, ensuring that users or readers encounter the most relevant information first.
Highest Adoption Rate
Low Priority
I ideated on possible product features and prioritized them based on what are must-haves in Phase1 , further enhancement in Phase 2, and future for future product updates.
I first created user flow helping users navigate them to find and process the information. The goal is to bring Orion investment data into the desktop experience of our a white-labeled client portal.
After mapping out the task flows to guide users through key actions, I moved into low-fidelity wireframes to visualize and validate the layout and interaction patterns.
After mapping out the task flows to guide users through key actions, I moved into low-fidelity wireframes to visualize and validate the layout and interaction patterns.
Given the tight timeline, I prioritized early feedback from the design team. Internal critiques were instrumental in identifying areas where the user flow could be simplified and made more intuitive. These collaborative sessions also helped align our design with user expectations and highlighted diverse perspectives that ultimately improved the overall experience.
After reviewing the Hi-Fi wireframe with the team, I ensure the mobile components are updated before handoff to the engineers for production. Create a list row component for a mobile fintech application that can handle multiple combinations of data, including but not limited to account balances, transaction details, notifications, and financial insights.
As the mobile app grew, this component ended up supporting 99% of the interface. Over time, I found the original structure too complex for ongoing scaling. This list component was later refactored to simplify the structure and improve performance as our feature set expanded. I worked closely with engineers to ensure the new version was more scalable and easier to maintain.
Through this case study, I learned users behave very differently on their phone compared to the desktop and it can be action focused or less action oriented dependent on the industry you are designing it for. Touch screens let users have a lot more interaction compared to the web.