mobile-analyzer
Skill36 starsChanged 14 days agoMITView on GitHub
Mobile-specific UX analysis — touch interactions, viewport issues, scroll behavior, mobile vs desktop patterns, and responsive design validation. Use when investigating mobile experience, responsive design bugs, or mobile conversion rates.
In this repository45 other files it gives its agents.
- a11y-analyzerSkill
- annotation-opsSkill
- anomaly-detectorSkill
- api-monitorSkill
- benchmark-analyzerSkill
- campaign-trackerSkill
- changelog-detectiveSkill
- cohort-compassSkill
- comparisonsSkill
- customer-360Skill
- dashboard-builderSkill
- deploy-radarSkill
- error-forensicsSkill
- experiment-analyzerSkill
- feature-adoptionSkill
- form-analyzerSkill
- frustration-hunterSkill
- funnel-doctorSkill
- general-analysisSkill
- heatmap-generatorSkill
- incident-responderSkill
- jira-bug-reporterSkill
- journey-builderSkill
- lifecycle-analyzerSkill
- metric-auditorSkill
- nps-proxySkill
- onboarding-tutorSkill
- page-performanceSkill
- persona-builderSkill
- predictive-alertsSkill
- privacy-auditorSkill
- query-translatorSkill
- quick-statsSkill
- report-deckSkill
- retention-analyzerSkill
- revenue-impactSkill
- scroll-depth-analyzerSkill
- segment-wizardSkill
- session-playlistSkill
- session-reviewSkill
- session-searchSkill
- slack-reporterSkill
- user-journeySkill
- webhook-healthSkill
- weekly-digestSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
Use free fullstory:discover_groups and fullstory:get_opportunity_stats for live signals.
- Distinctive: line 37
Start with the split:
- Distinctive: line 140
Always compare mobile to desktop — a rage click rate of 3/100 sessions might seem normal until you see it's 1/100 on desktop.
- Distinctive: line 143
If mobile conversion is significantly lower than desktop (2x gap or more), prioritize it.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
fullstory:discover_groups → filter by device_type="mobile"Mobile-specific signals to watch for:
- Pinch-zoom events: Users zooming in to read or tap — text too small, touch targets too small
- Horizontal scroll: Content wider than viewport — broken responsive layout
- Orientation change rage: Users rotating device repeatedly — layout broken in one orientation
- Keyboard overlap: Form fields obscured by virtual keyboard — user taps field, keyboard covers the submit button
Step 3: Compare mobile vs desktop by page
For key pages, compare performance:
Page: /checkout
Mobile: 12% conversion, 34% bounce, 3 rage click events per 100 sessions
Desktop: 22% conversion, 18% bounce, 1 rage click event per 100 sessions
→ Mobile conversion is nearly half of desktop. The gap needs investigation.Step 4: Investigate mobile-specific sessions
fullstory:get_sessions(
device="mobile",
page="/checkout",
metric_id=low_conversion_metric,
limit=5
)
→ session-context agent: "What difficulties did this mobile user face on /checkout? Were form fields hard to tap? Did the keyboard cover content? Was any text cut off?"Step 5: Touch target analysis
Identify elements that users struggle to tap:
fullstory:discover_groups → dead clicks on mobile → what elements?Common touch target issues:
- Buttons < 44px (Apple HIG minimum)
- Links too close together (accidental taps)
- Hamburger menus that don't respond to tap
- Swipeable carousels that intercept vertical scroll
Step 6: Report
## Mobile Experience Audit
### Overall Split
- Desktop: 68% | Mobile: 28% | Tablet: 4%
- Mobile share growing: +3% vs last quarter
### Mobile vs Desktop Performance
| Metric | Mobile | Desktop | Gap |
|--------|--------|---------|-----|
| Checkout conversion | 12% | 22% | -10pp 🔴 |
| Bounce rate | 34% | 18% | +16pp 🔴 |
| Rage clicks/100 sessions | 3.2 | 1.1 | +2.1x 🔴 |
| Avg session duration | 3m 12s | 6m 45s | -3m 33s |
### Critical Issues
1. **Checkout form on mobile**: The "Apply Promo" button is 32px tall (below 44px minimum). Users rage-click it 4-8 times. 73% of mobile checkout rage clicks target this button.
2. **Horizontal scroll on /products**: Content overflows viewport on iPhone SE (375px). 12% of mobile sessions on this page show horizontal scroll gestures.
3. **Tablet experience**: Only 4% of traffic, but 28% conversion — tablets convert better than desktop. Consider tablet-specific optimizations.
### Recommendations
1. Increase "Apply Promo" button to 48px minimum touch target
2. Fix horizontal overflow on /products for small viewports
3. Prioritize checkout mobile UX — closing the mobile-desktop conversion gap could add ~$12K/month in recovered revenueMobile-Specific Debugging
| Issue | How to Detect | Fix |
| Touch target too small | Dead clicks on element (mobile only) | Min 44px touch target |
| Content cut off | Horizontal scroll events on mobile | Check viewport overflow at common breakpoints |
| Keyboard overlap | Form field focused → immediate page leave | Position key form fields above the keyboard zone |
| Unreadable text | Pinch-zoom events on text elements | Min 16px font size, proper viewport meta tag |
| Accidental taps | Two different links clicked simultaneously | Increase spacing between tappable elements |
| Slow mobile page load | High bounce rate + short time on page | Check mobile page speed (not in Fullstory — use PageSpeed Insights) |
Guidelines
- Always compare mobile to desktop — a rage click rate of 3/100 sessions might seem normal until you see it's 1/100 on desktop.
- Mobile issues are often viewport-specific. Check multiple sizes: iPhone SE (375px), iPhone 14 (390px), Pixel (412px), iPad (768px).
- The
review-snapshottool shows the actual rendered page at a specific viewport size — use it to verify layout bugs. - If mobile conversion is significantly lower than desktop (2x gap or more), prioritize it. Mobile revenue is growing; a 2x conversion gap is a 2x revenue leak.
- Responsive design bugs after a deploy are one of the most common regressions. Run
deploy-radarwith mobile segment filtering after major UI deploys.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

