concept input in category design

This is an excerpt from Manning's book Usability Matters: Mobile-first UX for developers and other accidental designers.
Input encompasses all the ways of supplying data and instructions to the app. It’s the first of the components that relate to the high-level structure of the app. Figure 1.2 shows these components (in bold) and their relationships.
Figure 1.2. How the five structural components of an app relate to each other, the user, and external systems
![]()
Input for a mobile app can be about much more than tapping a screen and filling out a form. An assortment of input sources and mechanisms are available from the device, the person using it, and remote sources. For the people using the app, it’s rarely their aim to use an app just to gather input. Whether saved for later use or to give an immediate reward, aim to optimize the input-gathering elements of an app to the point where the people using the app can receive the maximum benefit from their input.
The most frequent approach to giving input and interacting with an app on a mobile device is touching the screen. Many such devices are referred to as touch-screen devices. This ubiquity of use can lead to complacency when creating apps for these devices. People touch the screen of devices a lot, but there’s value in taking a metaphorical step back and asking why and how they’re doing so. Assuming people touch the screen because they must interact with your app risks overlooking the understanding or intention behind the interaction. By not thinking about what you’re asking them to touch, you may also overlook considerations for alternative input methods.
Although a finger is the most common “device” used to interact with a mobile app, its use isn’t always possible or appropriate. In this case, the input is commonly provided with a stylus. The next section looks at the second most common form of input: a stylus (a digital pen or pencil), which is popular on larger devices and for certain types of apps.