| Area registry based feedback | Feedback is triggered by centralized registry, which is hosted by the feedback system. When some area with defined feedback is touched, the feedback is triggered by the system before any application even receives the pointer event. For this kind of feedback it is on application’s responsibility to add, update and remove areas to the registry according to application state. Area registry’s main purpose is to minimize the feedback latency by processing the pointer event faster than what would be possible from a normal GUI application. |
| Direct feedback | Feedback is triggered directly from the application, which receives the pointer event. |
| Feedback latency | The time that it takes from the moment when user touches the screen, until feedback is generated. This includes all the processing in touch driver and window server, as well as the time that it takes for actually starting the feedback. |
| Logical feedback type | Defines the nature of the feedback effect (e.g. “basic” or “sensitive”), but does not tell which type of physical feedback effect (vibrator pulse, sound effect etc.) is produced. Logical feedback type is decided by the UI component or application, which is using Tactile Feedback Client API for producing feedback. |