Mobile UI DESIGN / DESIGN SYSTEM
Designing Mobile App & Design System For PeakXV’s Investment Tracking Platform
My Role
Product Designer
Duration
5 Months
DOmain
Enterprise Mobile
Background
Peak XV's internal investment tracking platform, initially a web-only application, presented usability challenges for mobile users, limiting accessibility and on-the-go functionality. To address this, I was tasked with creating the user experience for mobile devices.
The goal was to provide a seamless, responsive experience that maintained feature parity with the web version while optimizing for mobile contexts.
Business Goals
Help Analysts to Scan Data Quickly
Increase Engagement
Enhance Overall Efficiency
Reduce Web App Dependency
Features Overview
News Feed
The Newsfeed feature in Peak XV's platform functions as an internal, professional microblogging system tailored for the venture capital ecosystem.
Users, including investors, partners, and analysts, can share various types of content such as private and public notes, meeting summaries, and financial reports. This supports features, allowing users to participate in threaded discussions, set reminders, provide company or founder ratings, and attach relevant documents.
It keeps Peak XV team informed about key ecosystem events, from investor meetings and quarterly financial updates to external funding rounds.
Company 360
Company 360 allows investing partners and analysts at Peak XV to study upcoming startups & existing portfolio companies, facilitating better fund allocation and decisions .
Why Mobile Version Was Important?
Upon discussing the issues with some of our users, here’s what I discovered
3/5 🫤
Users hardly used their laptops as most of their work except assessments gets done using mobile phones alone.
4/5 🥱
Users found the web portal inconvenient for updating their meeting summaries on company introductions and urged to have a mobile experience
4/5 👹
Users missed voting before a Investment Committee Meeting as they missed the email notifications and voting on laptops was cumbersome
5/5 👾
The users reported that the mobile-responsive version of the web application often experienced performance issues, resulting in a less than optimal user experience
How we prioritized
The web platform had around 15 unique features which had detailed experiences, layered features and complex designs.
In order to streamline the design & development activity, we decided to prioritize the top 5 features that users access on a daily Basis. For this, we analysed data charts from Amplitude and Validated the same with Users
Newsfeed
To update meeting summary, add notes and provide company performace summary with the PeakXV ecosystem
IC Meeting
In order to vote and add personal inputs about a company that get’s selected for fund allocation
Company 360
To analyse and assess company stats & metrics for optimized fund allocation
Get Real
Quarterly update of portfolio companies where our users can add updates about how our portfolio companies are doing
Content Optimization on Mobile
I used a responsive web design approach that automatically adjusts the layout and content to fit different screen sizes prioritizing single-column layouts for mobile
1
2
3
1
Responsive Newsfeed
2
Add Notes/Updates
3
Filter
Some Explorations
and Why It Didn’t Make it
Building Design System
Motivation
We were team of two - a Senior Product Designer and a Junior Designer. But our engineering team was fairly large. When we handed over the designs in our first two sprints, during QA I realised the developed version looked quite different from the designs and we had to pinpoint the discrepancies by creating additional documentation and Asana Tickets.
To solve this problem, I took the initiative to document the designs by creating a system of deliverables and breaking the design down by using atomic design principle. This also helped the devlopers to maintain similar components in the local repositories to minimise redundancy
I designed the system even before tokens were introduced in Figma Hence I had to do a lot of manual work from ground up. I took a systematic approach by brainstorming a component list and then breaking them down into Atomic design principle of component organosation
