LWCIntermediatemobileperformanceux
Optimize mobile LWC touch targets and scroll performance on record pages
Real World Scenario
Field service LWCs fail QA on iPhone: buttons too small, momentum scroll janky with nested scroll regions.
Expected Answer
• Minimum 44px touch targets per mobile HIG alignment
• Single scroll container per view—avoid nested overflow scroll
• Passive scroll listeners where supported reducing main thread blocking
• Reduce wire count on mobile flexipage placement audit
• formFactor Small conditional layout in meta xml or @api
• Test on physical devices not only Chrome devtools mobile emulation
• Lazy load below-fold sections on mobile record page
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Minimum 44px touch targets per mobile HIG alignment. Single scroll container per view—avoid nested overflow scroll. Pick based on your integration pattern and team capability. Mobile record page is constrained environment—separate mobile flexipage audit from desktop. Balance speed of delivery with maintainability.
Architect Perspective
Mobile record page is constrained environment—separate mobile flexipage audit from desktop.