Mobile App Launch 01

First step

Conducted deep qualitative interviews with Enterprise sales reps across the US and Europe. Concurrently analyzed 100+ support tickets from the past year and scraped App Store and Google Play reviews. Leveraged AI tools to accelerate data clustering, categorizing pain points by frequency and severity.

Research methodology & insights

• Due to legacy app crashes, reps defaulted to opening the web app in mobile Safari. Missed taps and sudden session timeouts occurred directly in front of prospective clients.
• Generating a trackable link on web required 5 steps and manual email entry. In live pitch environments, this took up to 2 minutes—forcing reps to send un-tracked public links or skip sharing altogether.
• 8 out of 12 respondents confirmed losing tenders against Showpad and Seismic specifically during mobile capability demonstrations.

Key takeaway

The mobile app had to be architected for high-stress environments: extreme time constraints, high background distraction, and a customer attention span measured in seconds.

Analysis

I performed a comparative UX teardown of market leaders Showpad and Seismic. I mapped out their key workflows to identify industry standards and uncover strategic opportunities for our MVP.

Benchmarking methodology

Secured demo access to both platforms, mapped out their core journeys in FigJam, and built a comparative matrix analyzing three criteria: taps-to-share, navigation paradigm, and offline file handling.

Key competitive insights

• Competitors placed link generation front and center: document selection to copy link takes just 2–3 taps. This validated our thesis on aggressively minimizing interaction steps for flipbooks.
• File discovery relied on prominent visual cover cards, using text lists only as secondary filters. This proved the inefficiency of SalesPal’s text-list layout for field work.
• Competitor suites were bloated with legacy features like built-in chats, social feeds, and LMS modules—degrading performance and complicating onboarding for field reps.

We needed to focus resources on building a lean, hyper-specialized tool optimized for rapid, single-handed document sharing.

User motivation layers

Deconstructed user motivations across three distinct JTBD tiers.

• Functional Job: “Standing in front of a buyer at an expo, I want to send a personalized trackable link in 30 seconds so I lock in the deal before the conversation ends.”
• Emotional Job: “During high-stakes pitches, I want total confidence that the app won’t crash or prompt for password re-entry so I can focus entirely on selling.”
• Social Job: “Presenting materials from a tablet, I want to project a modern, tech-forward brand image that builds buyer trust.”

Core hypotheses

1. Compressing the sharing flow to 3 steps will drop median task time to 30 seconds, enabling real-time pitch sharing. We expect a multi-fold reduction in Task Success Time during usability testing.
2. Replacing text lists with a visual cover grid will accelerate document discovery, reducing Search Time and eliminating mis-clicks.
3. Bringing Trackable Links to mobile will drive feature adoption above 50%, directly lowering B2B churn.

Impact

These hypotheses aligned the cross-functional team on eliminating friction at the highest-leverage touchpoint.

Tech stack selection

Collaborated with product leadership and the agency tech lead to evaluate cross-platform (Flutter / React Native) versus native development (Swift / Kotlin).

Strategic trade-offs

• Cross-platform offered speed up front but introduced risks around UI responsiveness, fluid native gestures, and tablet layout adaptations.
• Native development required higher upfront investment but guaranteed 60fps interaction polish and seamless integration with OS native Share Sheets.
• Partnered with backend engineering to design bulletproof auth persistence: long-lived refresh tokens (2+ months) and Enterprise SSO integration.

Killer features

Concurrently, engineering and QA validated offline architecture: caching flipbooks upon first open. Once confirmed feasible for MVP, I greenlit offline access as a core user journey for immediate design.

Outcome

While native development demanded more engineering bandwidth, it was the only architecture capable of achieving our 30 seconds sharing goal. We needed a rock-solid tool reps could rely on during live pitches.

Trimming scope

The initial wishlist spanned 12+ major features: folder management, inline document editing, public links, analytics dashboards, and push notifications. Building the full scope in 6 months would have guaranteed missed deadlines.

Scoping negotiations

Applied a strict prioritization filter: “Can a sales rep close a deal in a meeting without this feature?” Combined with RICE scoring to rank core capabilities.

Facilitated an alignment session with the PM and CEO, stripping the backlog down to four essential capabilities: visual cover grid, Trackable Link creation, engagement tracking, and offline access.

Scope trade-offs

• Deferred from MVP: Content creation & editing, flipbook styling customization, deep analytics dashboards, and folder management.
• Calculated trade-off: Excluded basic public links. Focused 100% of engineering bandwidth on 3 core pillars: visual navigation, Trackable Links, and offline storage.

Retrospective note

Cutting public links created post-launch friction—support received a surge of user tickets expecting basic links out of the box. Detailed breakdown in Reflection.

Designing for simplicity

Designed the mobile workflow preserving web platform logic while compressing interaction into 3 frictionless actions:

1. Tap “Share” on the document card.
2. Enter recipient name (required for lead tracking).
3. Dispatch via native Share Sheet to email, chat, or AirDrop.

Prototyping & testing

Built a high-fidelity interactive prototype in Figma and conducted guerrilla usability sessions with 8 participants, including field sales reps and product marketers.

Simulated an unscripted trade-show pitch, asking participants to send a trackable link to a prospect while timing task completion with a stopwatch.

Validation metrics

• New 3-Step Flow: 8/8 success rate, ~25 seconds median completion time
• SalesPal Legacy (5+ steps): 5/8 success rate, ~2:20 median completion time
• Visual Cover Grid: 8/8 found documents within 1–2 scans
• Text List Navigation: 6/8 found, averaging +12s search time

Key takeaways

Usability testing proved the 3-step flow reduced user actions from 5 steps to 3 taps. Median link creation time dropped from 2m 20s (web Safari) down to ~25 seconds. Workflow execution speed surged by 82%, reducing task completion time by 5x.

Core concept

Eliminated product walkthroughs, onboarding carousels, and setup overhead in favor of instant time-to-value.

Instant operational readiness

Upon authentication, the app instantly hydrates the active publication library. Sales reps jump straight to work with zero learning curve.

Robust offline mode

When network connectivity drops (common at convention centers), reps maintain uninterrupted access to cached publications.

Adoption results

By matching mental models from the web app, we eliminated onboarding friction and maximized first-share conversion.

As a result, ~60% of MAU regularly download and share cached flipbooks offline, validating the critical necessity of offline storage.

Design system & workflow

Architected a cross-platform design system in Figma adhering strictly to HIG and Material 3 guidelines, establishing a transparent design review cadence.

Driven by sprint cycles: spec → build → design review → fix. As the PM managed timelines, product quality oversight remained entirely under my leadership.

Pixel-perfect QA

Installed every pre-release build via TestFlight and Android APKs, personally auditing spacing, typography, motion curves, and layout fidelity against Figma specs.

Bug tracking & triage

Documented layout discrepancies in Figma and logged precise, actionable tickets in the agency’s Jira backlog.

Governance impact

Rigorous design governance prevented UI design debt from accumulating and ensured polished, production-grade release builds.

Go-to-market

Shipped V1 right on the 6-month deadline. Instead of a hard sunset of SalesPal, leadership executed a phased migration campaign with dedicated customer demos.

Business impact

Our core objective was removing the enterprise blocker. In Q1 post-launch, the sales team leveraged native mobile as a key differentiator, closing multiple major accounts and reducing Enterprise churn by 20%.

Engagement metrics

Feature Adoption Rate surpassed 60% within Month 1, demonstrating rapid time-to-value: over half of active users successfully created and dispatched a Trackable Link.

Usability & retention

D30 Retention reached 45%, significantly outperforming target benchmarks. The 80% reduction in Task Success Time (~25 seconds) observed in labs was fully validated by production telemetry.

The MVP achieved all strategic business goals, proved product-market fit for mobile tracking, and laid a solid foundation for V2 scaling.

Roadmap

Following V1 deployment, we kicked off V2 product strategy. Objectives focused on addressing MVP trade-offs and building advanced security controls for Enterprise accounts.

Grid architecture redesign

V1 featured a tight 3-column card layout, pushed by the PM to maximize screen density. However, interaction analytics revealed severe UX friction: small tap targets led to mis-clicks, wrong document opens, and inflated search times.

For V2, I built a data-backed case persuading the PM and CEO to pivot to a prominent 2-column grid. The change dramatically improved cover legibility, expanded tap targets, and streamlined document discovery on the move.

Enterprise privacy & security controls

In V2, we also introduced public link generation, pairing it with advanced Privacy Settings. Reps gained full control to set passwords and restrict access to client corporate domains directly from mobile. Meeting security compliance accelerated expansion deals within Enterprise accounts.

Design retrospectives

• MVPs demand ruthless compromises. Deliberately withholding desktop baseline features to focus exclusively on mobile tracking enabled us to hit a non-negotiable business launch date.
• Trust usability evidence early. Layout friction surfaced during initial prototype testing. My key takeaway: advocate more aggressively for lab test findings to convince stakeholders before shipping V1.