Why Can't I Talk to My Tools, and Why Don't They Know What to Do?
Often when writing a message to someone, I need to recall some piece of information or idea. Maybe it’s a funny meme or an interesting stat. Regardless, you typically have to leave the messaging application you’re in and navigate either to some central store or the source application (usually it’s some errant bookmark) to remember what the hell you were searching for again. Maybe you switch back to the messaging application to remind yourself, then carry out the search. You then need to download that information or copy it, paste it into the messaging application, and send.
What I’ve massively glossed over is all the friction from speed and all the distractions along the way as you open up the browser and see the tab you’re on about the potted history of some obscure bureaucrat—and proceed to resist the temptation to get distracted. All the while, you vaguely paw at the keyboard in a futile attempt to remember what you want.
Why can’t the experience be as simple as messaging your creative store and getting a nice contextual response? You could even let it peek at what you were just chatting about, and it could draw on that connective and contextual relevance. It could send directly back to you—within the messaging application—the glorious statistic you need on horse deployments in Finland in 1955.1
Allowing you to continue your chat undistracted.
Footnotes
-
Finland reached peak horse in 1955. ↩