I dont think we're discussing real solutions to the mobile computing problem here - just stop gaps.
The issue with doing real work on a tab or smartphone is that touch is not a fast or accurate input medium - mice and keyboards are much better suited for it.
However, it would be foolish to think this will always be the case. Some combination of our devices recognizing new gestures (grasp, cup, etc.), advances in interface design and voice recognition will eventually disrupt the keyboard and mouse. Since our data can basically be stored in a number of device agnostic ways already via cloud computing, user interfaces for interacting with that data are only going to iterate faster and faster.
I think the problem of creating content on the go is going to be solved in the software too soon to warrant a whole product line that merges keyboards and trackpads into our tabets.
The issue with doing real work on a tab or smartphone is that touch is not a fast or accurate input medium - mice and keyboards are much better suited for it.
However, it would be foolish to think this will always be the case. Some combination of our devices recognizing new gestures (grasp, cup, etc.), advances in interface design and voice recognition will eventually disrupt the keyboard and mouse. Since our data can basically be stored in a number of device agnostic ways already via cloud computing, user interfaces for interacting with that data are only going to iterate faster and faster.
I think the problem of creating content on the go is going to be solved in the software too soon to warrant a whole product line that merges keyboards and trackpads into our tabets.