There aren't more popular client-side APIs because there aren't more popular client-only applications, and there aren't more popular client-only applications because developing the user experience is hard. I think, if you used one of these systems to figure out a good UX, then it would give you the impetus to chase down a good client-side solution for speech recognition.
Now, I am sure Dragon V1 would be quite underwhelming to my modern notions of how computers should work. But I would even say my smartphone is better than a middle-of-the-road PC from 2010. It's better than my PS2, and even my PS2 had a few games that had speech interface (some Navy Seals game, it worked pretty well).
What factors are at play? Is it the noise cancellation? Seems like a stationary device in a home has the ideal chance to create a reusable noise cancellation profile.
.NET seems to be built on the technology that has shipped with Windows for a while, and yet Cortana etc still reach out to the mothership for their speech recognition, so there are probably significant benefits to doing so, otherwise someone would have made theirs work offline and touted it.
I'm guessing that matching a pre-specified pattern with some amount of error is easier than transcribing arbitrary voice, which you need for search.
But I definitely agree, I regularly wish I could stop google maps' directions with a voice command when I get to a part of a route that I already know well enough to complete myself.