One missed tap, one ghost touch, or one delayed swipe can make an expensive phone feel broken.

In this episode, Satish uses a simple real-life example first, then turns the idea into a practical technical mental model for engineers and curious builders.

In Simple Terms with Satish: daily tech trends explained simply, with enough technical depth for builders.

Production note: This episode uses authorized synthetic narration based on Satish's own voice. The topic, script, and final editorial approval are by Satish.

Engineer notes:

Exact technical references:

- Core technical object: projected capacitive touchscreen sensing.

- Main architecture pattern: conductive grid -> capacitance measurement -> scan controller -> coordinate estimation -> filtering and palm rejection -> gesture recognition -> OS input event -> app response.

- Useful mental model: a touchscreen is an invisible electrical grid plus a real-time signal-processing pipeline.

- Rough timing anchor: at 120 Hz, samples are about 8.3 milliseconds apart; at 240 Hz, samples are about 4.2 milliseconds apart. Actual device rates vary by hardware, power mode, stylus mode, and operating-system pipeline.

- App-layer mapping: platforms expose interpreted touch or pointer events rather than raw capacitance maps. Android `MotionEvent` exposes coordinates, pointer count, touch size, pressure, tool type, and historical points; W3C Pointer Events similarly define hardware-agnostic pointer input with coalesced and predicted events.

- Main limitation: capacitive touch can be affected by gloves, water, electrical noise, screen protectors, palm contact, latency smoothing, and device-specific sensitivity tradeoffs.

Sources:

- https://arxiv.org/abs/1612.08227

- https://developer.android.com/reference/android/view/MotionEvent

- https://www.w3.org/TR/pointerevents3/

- https://developer.apple.com/documentation/uikit/handling-touches-in-your-view