Enter the password I sent you.
Hi, I'm Kyle.
Consumer software used by 18M+ people, in a $60M ecosystem built from pre-revenue. I design it end to end, web to native, and build hands-on with AI. Currently SVP of User Experience at Sovren Technologies.
Kyle McCarthy · Dallas
The products I'm proudest of are the ones I'd hand to the people I love. I sweat the details until they feel right, because at scale the smallest decisions carry the most weight.
A creator-first network had to scale from someone's first post to a full-time creator without ever feeling heavy. I designed the core surface: feed, Stories, Bursts, live Lounges, profiles, messaging, plus the Studio and ad tools behind it. Part of an ecosystem reaching 18M+ people.
Read the case study →

A non-custodial wallet that doubles as a social network, and the checkout that powers Shop. Self-custody, made social.
View case →
Short-form, long-form and livestream creation, plus the path to getting paid and a storefront on every profile.
View case →
A self-serve ad platform: one advertiser experience across the feed, video and beyond, built hands-on with AI.
View case →I design for the moment a product earns a place in someone's day, and the trust that keeps them coming back.
Most recently I led experience across four flagship products in one connected ecosystem: a social network, a payments wallet, a video platform and a creator marketplace, shipping on web, iOS and Android alongside a 100+ engineer org. I work end to end: the research, the system that holds it together, and the last pixel. Years inside feeds, identity and trust & safety taught me where the weight really sits.
I also build. I prototype hands-on with AI (Claude, Figma AI, Grok, Replit), turning an idea into testable product in days, not weeks.
I don't just design products. I run one. CrushSuite is a suite of Shopify apps that lets wineries sell wine online, compliantly. It handles the state rules, age gates and shipping fees that make direct-to-consumer wine so hard, right inside Shopify's checkout, and runs wine clubs with releases, subscriptions and member management. I designed and shipped it end to end, from first prototype to a 5.0-rated app on the Shopify App Store. Next up: a conversational-AI wine assistant we're building now.
Visit CrushSuite ↗Whatever it takes to get it right. For the person using it, and the business behind it.
Designing the core social surface for a creator-first network: the daily habit that everything else in the ecosystem is built on top of. Part of a platform reaching 18M+ people.
Visit the live product ↗
Home feed · web & native
The home feed: the surface a creator returns to every day, and the front door to Stories, Bursts, Lounges, Pay and Shop.
A creator-first network lives or dies on one thing: whether people come back tomorrow. The feed is where that habit is won or lost.
The same screen had to welcome a first-time poster and give a full-time creator the tools to run a business: short-form video, live audio, stories, messaging, payments, a storefront. Pile it all on and the surface collapses into noise; hide it and creators leave. And on a platform under real scrutiny, trust and safety weren't a feature, they were the reputation. My job was to make all of it feel like one calm daily habit, not a control panel.
At scale, the smallest decisions carry the most weight.
I led the whole social surface end to end on web, iOS and Android. But with a 100+ engineer org building against my designs, the real deliverable was a shared design system precise enough that dozens of engineers could ship the feed, the creation tools and the safety affordances consistently, without me in the room.
Native on web, iOS and Android, without fragmenting into three different products.
Feed, Stories, Bursts, Lounges, profiles and messaging had to add up to one daily loop, not a drawer of disconnected apps.
Moderation, reporting and identity designed into the core flows from the first sketch, not bolted on at the end.
I mapped what a creator does in a day, arrive, catch up, create, get paid, come back, and made that loop the spine, with the feed as the place you always return to.
I prototyped the friction points (first post, going live, switching between watching and creating) as flows, so the seams showed before they shipped.
Recurring patterns became documented components so 100+ engineers stayed consistent. Where a surface stole clarity, I cut it: judgment, not feature count.
Bursts · short-form video
Lounges · live community & rooms
Each surface was designed to launch from the feed and return to it, so the product gained range without gaining weight.
Discover · finding the next creator
Profile · identity that reads at a glance
Discovery and identity: how people find new creators, and how creators show up, designed so the signals that build trust are legible at a glance.
The shipped product makes the powerful stuff feel optional and the everyday stuff effortless.
The feed as home base. One legible stream of posts, Stories, Bursts and live Lounges, no four interfaces to learn. Creation is always one tap away, never crowding the read.
Lightweight creation. Stories and Bursts for the in-between moments, the same tools a casual poster and a serious creator reach for at different intensities.
Safety woven in. Reporting, controls and identity cues live inside the flows people already use, present without being in the way.
Stories · the in-between moments
Stories: lightweight, full-screen posts for the in-between moments, the same tool a casual poster and a serious creator reach for at different intensities.
A creator network is only as strong as the tools that pay creators and show them what's working. I designed Studio too, and built it hands-on with AI.
Studio gives creators their balance, payouts and a clear read on what's landing. I built it myself with AI, idea to working tool in days, proof I can design the system and ship the thing.
Studio · mobile
Studio on web and mobile: the same earnings, payouts and analytics on any screen, designed and built hands-on with AI.
The deeper engagement and revenue numbers, I'll walk you through in person.
Designing a non-custodial wallet that doubles as a social network: send to people instead of addresses, chat, follow, get paid and stake, with the hard parts of crypto kept calm and out of sight. Built on crypto settlement, designed to extend to fiat.
Visit the live product ↗
Home · balance, assets & quick actions
The home screen: balance, assets and one-tap send, receive and stake, with friends only a tab away. Money and the people you move it with, in one place.
Money is the most sensitive thing a product can ask people to trust it with. One confusing moment and they never come back.
A non-custodial wallet hands people real control, their keys, their funds, settlement that can't be undone, and that power is exactly what makes it terrifying: seed phrases, gas, addresses, the fear of one wrong move. Most wallets answer that fear with more controls, which only makes the cliff edge feel closer. My job was to make self-custody, sending and settlement feel as ordinary as any banking app, for people who'd never touched a blockchain, without lying about what was happening underneath.
Trust is designed in the moments just before someone taps send.
I led the entire wallet end to end on web, iOS and Android. Because a 100+ engineer org was building flows where a mislabeled button could cost someone real money, the shared design system had to be exact: every state, every confirmation, every edge case specified, so nothing was left to interpretation.
People held their own keys. The interface had to convey safety and control without burying anyone in cryptographic detail.
Crypto settlement shipped first, but the model put dollars and tokens behind one calm way to hold and move value.
A mistaken transfer can't be clawed back, so confirmation and clarity were designed into every value-moving flow from the first sketch.
I mapped where trust broke: first-time setup, sending to a stranger, seeing a balance move. Those fear points set the priorities, not the feature list.
Keys, gas and addresses moved to the background, surfaced only when they mattered, simplicity that never became a lie about what the wallet was doing.
I prototyped the high-stakes flows (send, receive, payout) and pressure-tested the confirmation moments. Where an option seeded hesitation, I cut it: in payments, confidence is the feature.
Send · to a person, not an address
Asset detail · hold, send & stake
You send to a person, not a 42-character address, and drill into any asset to see what you hold, send it, or put it to work, all on one consistent pattern people learn once.
Moving value feels ordinary now, and it feels social, which for a non-custodial crypto wallet is the whole hard-won point.
Send to people, not addresses. Balance, assets and quick actions read at a glance, and you send to a name or a face on one legible flow, with the cryptography out of sight and the confirmation moment built to create confidence, not friction.
A social layer. Chat, a follower network, profiles and a money activity feed make payments a place you connect, not a cold utility you visit and leave.
Safe by default, fiat-ready. Recovery, confirmation and clear identity cues live inside the flows, and the model was designed so fiat could sit beside crypto in the same wallet, even though crypto settlement shipped first.
Onboarding · social by default
From the very first screen, Pay frames itself as a secure wallet you use with your friends, so the social side is the promise, not an afterthought.
Chat · talk to who you pay
Network · follow & find people
Chat and a follower network turn isolated transactions into relationships, so paying someone is the start of a thread, not the end of one.
The deeper engagement and revenue numbers, I'll walk you through in person.
Pay isn't only peer-to-peer. It's the checkout behind Shop: when someone buys from a creator's storefront, they pay with crypto through Pay, so commerce settles inside the same wallet people already trust.
Unifying short-form, long-form and livestream creation, plus the path to getting paid, into a single tool instead of a drawer of disconnected apps. One workflow from idea to income.
Visit the live product ↗
A livestream on the web: the video, a live chat and the tip and store actions all in one view, so watching, talking and supporting a creator never split across screens.
The act of making video had been split into pieces, and creators paid the tax every day.
Short-form lived in one app, long-form in another, livestreaming in a third, monetization off to the side. A creator who wanted to post a clip, drop a full video and go live had to learn, manage and switch between separate worlds, each with its own rules, exports and dashboards. Every handoff lost momentum, quality, or the thread of how anything made money, and capped how much a creator could produce and earn. So I set out to collapse all of it into one path from idea to income.
The workflow is the product. Everything else is a feature.
I led the whole video product end to end on web, iOS and Android. The player, the uploader and the live tooling are wildly different surfaces, so the shared design system was what let a 100+ engineer org build all three without them drifting into separate products.
Short-form, long-form and live each have different rhythms. They had to share one coherent way to create rather than fork into three separate products.
The same person flips between viewer and creator constantly. Moving between watching and making had to feel like one continuous motion, not a mode switch.
Earning couldn't be a separate dashboard. It had to be a visible part of the creation flow, so the route from publishing to getting paid was obvious.
I traced what a creator does across clips, long videos and live sessions, and marked every place the old tooling forced a context switch. Those seams became the design targets.
Underneath the three formats was one repeating shape: capture, shape, publish, earn. I designed that spine once so each format became a variation, not a separate app.
I prototyped the risky transitions (clip to long-form, recorded to live, watching to creating), designed playback and discovery so watching fed back into creating, and made the upload-to-payout path visible at the moment of publishing.
Live · broadcast & interact
Tip · support a creator in a tap
Clips, full videos and live broadcasts branch off one spine, and monetization rides along with it: a viewer can tip mid-stream without ever leaving the moment.
A workflow that used to span three apps now feels like one continuous motion.
Unified creation. Short-form, long-form and live share one creation flow, so the format is a choice, not a different app, and switching needs no exports or re-uploads.
Watching that feeds making. The player and browse experience are designed so watching flows naturally into creating, keeping people inside one loop.
Monetization in view. The path from publishing to getting paid is part of the creation flow, not a separate dashboard, and it holds together across web, iOS and Android.
On the web, the same video sits inside Parler itself, with its own tabs, store and featured rail, so Play isn't a separate destination but a layer of the ecosystem.
Earnings & payouts. Creators see fiat and token earnings per video and cash out through Pay, so the line from publishing to income is one they can watch fill up.
A store on every profile. A creator's Shop storefront lives right on their Play profile, so the audience a video earns can buy without ever leaving.
The earnings dashboard: all-time fiat and token earnings, broken down per video, paid out through Pay.
Profile · a store tab on every creator
A Store tab sits alongside Videos and Bursts on every creator's profile, so Shop is woven straight into Play, not bolted on beside it.
The deeper engagement and revenue numbers, I'll walk you through in person.
Designing a self-serve advertising platform that turns attention across the ecosystem into revenue: one advertiser experience that runs the feed, video and beyond. Designed and built hands-on with AI.
The advertiser home: every campaign, budget and result in one place: the monetization engine behind a feed reaching 18M+ people.
A creator ecosystem is only as durable as the business under it. The ad platform is where attention becomes revenue: the thing that funds creators, infrastructure and everything else.
An advertiser shouldn't need a sales rep or a manual to spend money well. They had to build a campaign, set a budget, choose who sees it and read whether it worked across very different surfaces (feed, video, sponsored posts) without learning a different tool for each, and every number had to read honestly, with no dark patterns nudging spend. The mandate was to make a serious ad system feel as approachable as posting.
Make spending money feel as simple as posting.
This is the clearest example of how I work now: I didn't hand off a spec and wait. I designed the advertiser experience end to end and built it hands-on with AI tooling, taking it from idea to a working platform in days, not weeks, then refined against what real campaigns needed.
Feed, video and sponsored formats have different mechanics. The advertiser had to manage them all from one consistent flow, not a separate console per format.
The whole loop (create, budget, target, launch, measure) had to be learnable in one sitting, without a sales call.
Budgets, projections and results had to read clearly and truthfully, so a marketer could trust what they were spending against.
Build a campaign in one guided flow: objective, audience, budget and creative, with the surface chosen inside the same path instead of a separate tool.
The shipped platform lets anyone launch and measure a campaign without help.
One campaign flow. Objective, audience, budget and creative in a single guided path, with the surface (feed, video, sponsored) chosen inside the same flow instead of a separate tool.
Budgets you can feel. Spend and projected reach update as you set them, so the tradeoffs are visible before you commit, not buried in a report afterward.
Performance in plain language. Live results framed around what a marketer actually wants to know: what it cost, what it reached, what it returned, instead of a wall of raw metrics.
The deeper engagement and revenue numbers, I'll walk you through in person.