> With a touchscreen all those dependencies go away
Not quite. You need a rough idea of where the controls are going to be so you can make sure that the user can reach them. The placement of that "iPad sized capacitive touch screen" is incredibly important, especially if the user has to search for the control.
That's no less true with hardware controls, and I'm probably splitting hairs, but it's not as simple as just allowing for it. There is still hardware to consider early on.
And when manufacturers do forget to plan for it, and shovel a touchscreen into an old-design cockpit, it's super-obvious, and awful.
Not quite. You need a rough idea of where the controls are going to be so you can make sure that the user can reach them. The placement of that "iPad sized capacitive touch screen" is incredibly important, especially if the user has to search for the control.
That's no less true with hardware controls, and I'm probably splitting hairs, but it's not as simple as just allowing for it. There is still hardware to consider early on.
And when manufacturers do forget to plan for it, and shovel a touchscreen into an old-design cockpit, it's super-obvious, and awful.