Mrunali Yadav's Portfolio

Work

Contact

About me

Resume

Zyllyon - Professional Networking Reimagined

Designed a 0-to-1 mobile networking app that reduces contact exchange time from 30–60 seconds to under 5 seconds, built for spontaneous in-person connections at events, conferences, and meetups. Co-founder and lead designer, driving product from concept to prototype — currently in development, launching soon.

Role

Product Designer, UIUX Designer

Team

2 Product Designers

Sector

B2C Networking

Duration

July 2025 - January 2026

Zyllyon - Professional Networking Reimagined

Role

Product Designer, UIUX Designer

Team

2 Product Designers

Sector

B2C Networking

Duration

July 2025 - January 2026

Zyllyon - Professional Networking Reimagined

Role

Product Designer, UIUX Designer

Team

2 Product Designers

Sector

B2C Networking

Duration

July 2025 - January 2026

Zyllyon - Professional Networking Reimagined

Role

Co-Founder, Lead Product Designer

Team

2 Product Designers

Sector

B2C Networking

Duration

July 2025 - January 2026

Challenge

LinkedIn has a trust problem. In a survey of 50 young professionals, 53% rated it closer to a job board than a genuine networking tool. 66% said networking today feels transactional or performative. And when we asked people about the best professional connection they ever made 46% said it happened in person, at an event. Not online.

The tools haven't caught up. Business cards get lost. LinkedIn requires WiFi, app switching, and an awkward "what's your last name?" moment that kills conversation flow. The window for a genuine connection at an event is 2–3 minutes. The friction of exchanging information eats into that window every time.

LinkedIn has a trust problem. In a survey of 15 young professionals, 53% rated it closer to a job board than a genuine networking tool. 66% said networking today feels transactional or performative. And when we asked people about the best professional connection they ever made 46% said it happened in person, at an event. Not online.

What I set out to prove

Before designing anything, I needed to know if this was a real problem or just my assumption. I ran two rounds of research, structured interviews and on-the-ground observation.

I interviewed 50 young professionals aged 22–35 who regularly attended networking events. The questions focused on how they currently exchange information, what frustrates them, and what would make networking feel effortless.

I also attended 5+ networking events and watched what actually happened when people tried to connect:

60% weren't carrying business cards
LinkedIn exchanges took 30–60 seconds and visibly broke conversation flow
People misspelled names, leading to failed connection requests
Groups of 3+ people had no graceful way to exchange info simultaneously
Nobody followed up because they had no memory of the context

The survey data confirmed the emotional layer: 40% said they were uncomfortable reaching out to someone they didn't know professionally unless they had something in common. The problem wasn't just friction — it was trust.

Design Process

As a two-person team building this app from scratch, I wore multiple hats, leading user research, defining the product vision, designing the entire user experience, and collaborating closely with our developer to ship a functional MVP. I used a lean design thinking approach: conducting user interviews to validate the problem, rapidly prototyping solutions, testing with real users at networking events, and iterating based on feedback to create an intuitive, visually distinctive networking experience.

As co-founder and lead designer on a two-person team, I led end-to-end — user research, product vision, UX, visual design, and development collaboration. I used a lean approach: validate the problem first, design second, test with real people at real events, iterate fast

How your best connections happen

15 survey respondents

In-person event — 47%Online community — 27%Mutual introduction — 20%LinkedIn — 7%

Would you use a networking app for early-career professionals?

15 survey respondents

Definitely yes — 33%Probably yes — 47%Not sure — 20%

Biggest frustration with professional networking today

15 survey respondents

Understanding The Problem

Research helps you empathize with users and experience the product as they do. To validate whether this was a real problem worth solving, I conducted user interviews and observational research at networking events.

Before designing anything, I needed to know if this was a real problem or my assumption. I ran two rounds of research, a structured survey and on-the-ground observation at networking events

Early quotes from users

Conducting User Interviews

I interviewed 40+ young professionals (ages 22-35) who regularly attended networking events, conferences, and meetups. My goal was to understand:

- How do people currently exchange professional information?

- What frustrates them about existing tools (business cards, LinkedIn)?

- When do they feel most awkward or inefficient during networking?

- What would make in-person networking feel effortless?

I interviewed 15+ young professionals (ages 22-35) who regularly attended networking events, conferences, and meetups. My goal was to understand:

- How do people currently exchange professional information?

- What frustrates them about existing tools (business cards, LinkedIn)?

- When do they feel most awkward or inefficient during networking?

- What would make in-person networking feel effortless?

swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.

View the User Interview Questions

Observational Research

Attending networking events

I attended 5+ networking events and observed how people exchanged contact information. I noticed: - 60% of people didn't carry business cards - LinkedIn exchanges took 30-60 seconds and broke conversation flow - People often misspelled names, leading to failed connection requests - Groups of 3+ people found it awkward to exchange info simultaneously - No one followed up because they couldn't remember context of the conversation

Creating Empathy Maps

While conducting interviews, I started to understand what are the users’ painpoints, I created empathy maps to synthesize what users say, think, feel, and do during networking moments. Common themes emerged: Says: "I'll connect with you on LinkedIn" (but often forgets) Thinks: "I hope I don't lose this business card" Feels: Anxious about awkward LinkedIn search, frustrated by broken flow Does: Pulls out phone, searches name, sends request, returns to conversation

Empathy Maps

swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.
swipe >>>
Designing a physical debit card taught me that digital design principles don't translate directly colors, typography, and materials behave differently, and constraints often lead to better solutions.

User Personas

Alex and Marcus shared similar networking challenges, so I merged their empathy maps to create "Frequent Networker Alex" someone who attends multiple events monthly and needs instant contact exchange with automatic context-saving for follow-up. Sarah and Jessica both valued quality over quantity in networking, so I created "Selective Connector Sarah" someone who wants meaningful connections and needs tools that preserve conversation context for authentic follow-up.

User Persona 1

User Persona 2

Defining the Solution

In the define phase, I synthesized research insights to frame the problem clearly and outline what success would look like.

Three design questions shaped every decision that followed:

Problem Statement

Alex is a young professional who attends frequent networking events and needs a frictionless way to exchange professional information in person because he wants to build meaningful connections without awkward LinkedIn searches or lost business cards interrupting the flow of conversation.

Hypothesis Statement

If we create a mobile app that allows instant profile sharing via QR code or NFC tap, then users can exchange professional information in under 5 seconds without breaking conversation flow, and they'll actually follow up because context is saved automatically.

Value Proposition - What Makes Zyllyon Different?

I mapped out core features and categorized them by value: Speed: Exchange info in under

5 seconds (vs. 30-60 sec for LinkedIn) Context: Attach notes about where you met and what you discussed Frictionless: No WiFi required, no name spelling, no app switching Visual: Beautiful digital profiles that stand out (unlike boring business cards) Smart Follow-up: Reminders to reconnect based on when/where you met

product’s features and benefits

product’s features and benefits 2

IDEATION

Exploring Solutions

With a clear problem defined, I started ideating on interaction patterns, visual design, and core user flows.

I evaluated 6 networking apps. They fell into two categories, digital business card replacements (static, felt like PDFs) and LinkedIn clones (too heavy for a quick exchange). Neither was designed for spontaneous, in-person moments with context-saving built in.

Competitor Analysis

I evaluated 6 networking apps and digital business card tools. Most fell into two categories: 1. Digital business card replacements (static, boring, felt like PDFs) 2. LinkedIn clones (heavy social features, overwhelming for quick exchanges) Gap identified: No app optimized for spontaneous, in-person exchanges with context-saving and visual appeal.

Competitor Analysis

How Might We Exercise

- HMW make exchanging info faster than pulling out a business card?

- HMW help users remember who they met and why it mattered?

- HMW make networking feel less transactional and more human?

- HMW eliminate the awkwardness of LinkedIn searches?

- HMW make digital profiles feel as personal as a handshake?

Core Functionalities

Based on research and ideation, I defined must-have features:

Instant Profile Sharing: QR code or NFC tap to exchange info in <5 seconds
Context Notes: Add where you met, what you discussed, follow-up reminders
Beautiful Profiles: Visual card-style profiles (not boring lists)
Offline Mode: Works without WiFi (crucial for crowded events)
Smart Follow-up: Reminders to reconnect based on time since meeting

DESIGN ITERATION

Bringing Ideas to Life

I started with rough sketches to explore interaction patterns, then moved to wireframes and prototypes.

Rough Sketch of early ideas

Sketches and Wireframes

Rapid Prototyping on Paper

I sketched 4-5 variations for key screens:

Home screen (profile card display)
QR code sharing screen
Connection received confirmation
Network tab (saved connections)
Profile editing

Then I digitized the strongest concepts in Figma.

Wireframes

Key Design Decision: Card Stacking Interaction

The Signature Interaction

Inspired by Apple Wallet, I designed a card-stacking interface where each connection appears as a layered card. Users can swipe through connections like flipping through a deck. This made the app feel tactile and visually distinctive not just another list-based contact manager.

Why it worked:

Visual hierarchy: Recent connections on top
Familiar mental model: Like physical business cards in a wallet
Delightful interaction: Swiping felt satisfying and intuitive

Key Design Decision: Card Stacking Interaction

The Signature Interaction

Why it worked:

The decision to go with cards over a list wasn't aesthetic. It was about creating a mental model that felt closer to how people actually remember connections, by face, by feel, by context not alphabetical order. Early wireframes showed a list. It worked but felt like every other contacts app. The card stack made it feel like yours

Card screen from the design

User Flow

Mapping the Core Journey

I outlined the typical flow for exchanging info at an event:

User opens app → sees their profile card
Generates QR code OR enables NFC tap
Other person scans/taps
Profile appears → user can add context note
Connection saved to "Network" tab
Follow-up reminder sent 3 days late

User Flow

Mapping the Core Journey

I outlined the typical flow for exchanging info at an event:

User opens app → sees their profile card
Generates QR code OR enables NFC tap
Other person scans/taps
Profile appears → user can add context note
Connection saved to "Network" tab
Follow-up reminder sent 3 days later

USABILITY TESTING

Testing with Real Users

I conducted guerrilla usability testing at 3 networking events with 15+ participants to validate core flows and interaction patterns.

Testing with Real Users

I tested core flows with 20+ participants across 3 networking events. What worked: the QR exchange was completed without instruction by most participants. The card stacking got consistent positive reactions. What needed work: context notes had low adoption, users understood them but didn't use them mid-conversation. This led directly to a quick-tap prompt redesign replacing the open text field.

Testing Goals

Can users exchange info in under 10 seconds?

Is the QR code scanning flow intuitive?
Do users understand the card-stacking interaction?
Are context notes being used? If not, why?
What's confusing or frustrating?

THE PROTOTYPE

Here's the latest high-fidelity prototype with all design iterations implemented. This interactive prototype demonstrates the complete user flow, from opening the app to exchanging contacts via QR code to adding context notes and browsing saved connections. Interact with the prototype and share your feedback!

early Prototype

THE IMPLEMENTATION

I am currently building Zyllyon using Cursor and Claude Code to translate the design into a functional app. This hands-on implementation phase allows me to test real-world usability, validate technical feasibility, and iterate based on constraints I encounter during development.

Below is a small glimpse of the app in progress!

The prototype is complete and the app is in active development. I'm building it with Cursor and Claude Code, which means I'm encountering real implementation constraints and iterating on design in response.

One example: the NFC tap flow required a confirmation state I hadn't designed for, the native NFC handshake is faster than expected and users missed the moment entirely. That led to a redesigned success animation that makes the exchange feel more intentional and satisfying.

Launch is coming soon.

Making the app in claude AI and cursor

What I Learned

The hardest decision on this project wasn't a design decision, it was deciding what not to build. Early versions had social feeds, event discovery, and recommendation engines. Research kept pulling us back to the same thing: people just want to exchange info and remember why it mattered. Everything else was noise.

Being the designer and co-founder means you can't hide behind 'the PM decided that.' Every decision has your name on it. That accountability made the design sharper.

No headings found on page

Stay Updated with me

Mail

mrunalipyadav@gmail.com

Phone

+1 (520) 780-7455

Links

Work

About me

Contact

Resume

Social

Behance

Instagram

Stay Updated with me

Mail

mrunalipyadav@gmail.com

Phone

+1 (520) 780-7455

Links

Work

About me

Contact

Resume

Social

Behance

Instagram

Stay Updated with me

Mail

mrunalipyadav@gmail.com

Phone

+1 (520) 780-7455

Links

Work

About me

Contact

Resume

Social

Behance

Instagram