What a "touch point" actually promises
A touch point is one simultaneous contact the controller can track as a distinct position. A 20-point frame can follow twenty fingers — yours, a colleague's, and two pupils' — as twenty independent cursors. That is all it promises. It says nothing about accuracy, latency or how the software uses the contacts; and yet it is the number buyers compare first, because it is the number printed largest. This guide gives the practical scale.
How many points applications really use
| Kiosk / signage UI | 1–2 simultaneous users → 10 points is complete headroom |
|---|---|
| Single presenter teaching | 1–2 hands + palm behaviours → 10–20 points |
| Two pupils / two players at a board or table | 4 hands → 20 points is the working floor |
| Multi-user tables (4+ people) | 32–40 points |
| Exhibition walls, group interaction | 40–64 points, platform maximum |
Where the catalogue sits
Ten points is the standard on compact panels and kits in this catalogue; twenty points is the frame line standard from 43 inches up; the frame platform is supplier-specified for 16/20/32/40/64-point builds, which is why large-format quotations ask about simultaneous users explicitly. Paying for 64 points on a single-user kiosk buys nothing the user can feel; specifying 10 points for a four-person table buys a queue of merged touches and a support ticket.
The numbers that matter as much
Response time — listed from 10 ms class down to under 8 ms on selected frames and 5 ms on component modules — decides whether ink follows a pen. Tracking continuity decides whether a fast drag stays a line or becomes dots. Software decides the rest: an operating system and application that only consume one or two contacts will never use your twenty. Specify the trio together — points, response, software — in the inquiry, and the model recommendation will be defensible in front of your own engineering review. For the underlying mechanism, read how infrared touch works.