mobile-analyzer

Mobile Analyzer

Deep-dive into mobile user experience — touch events, viewport issues, responsive design bugs, and mobile-specific conversion patterns.

When to Use

• "How does our mobile experience compare to desktop?"
• "Are mobile users having trouble with the checkout flow?"
• "Find sessions where mobile users encountered viewport issues"
• "Is the new responsive design working on tablets?"
• "What percentage of rage clicks happen on mobile vs desktop?"
• "Show me mobile sessions where users pinch-zoomed repeatedly"

Mental Model

Mobile users are different from desktop users:

• Input: Touch targets, swipe gestures, virtual keyboard
• Viewport: Smaller screen, variable sizes, landscape/portrait
• Context: On-the-go, distracted, slower connections
• Expectations: Faster, simpler, thumb-friendly

A design that works on desktop can fail catastrophically on mobile — elements overlapping, touch targets too small, keyboard covering form fields, horizontal scroll appearing.

For visual checks, follow session-review: open with fullstory:review-open, pass its client_id to fullstory:review-snapshot at the target timestamp, and always call fullstory:review-close, including on errors. Delegate repeated captures to session-replay.

Use free fullstory:discover_groups and fullstory:get_opportunity_stats for live signals. Discovery accepts one scope at a time (page_id, domain, app_name, segment_id, or funnel_id); use a segment for device/user filters and the live schema for time ranges. Use computed metrics for exact custom windows.

Workflow

Step 1: Quantify mobile vs desktop

Start with the split:

fullstory:build_metric(
  query="sessions by device type",
  output_type="top_n"
)
→ "68% desktop, 28% mobile, 4% tablet"

Then compare key metrics across devices:

fullstory:build_metric(query="checkout conversion by device type", output_type="top_n")
fullstory:compute_metric(metric_id)

Step 2: Mobile-specific frustration signals