Nope, you are right - not every platform does. But there are lots of companies coming up with a mobile version of their site that does work on a multitude of devices.
And I agree - a native app would be great (and preferred), but in reality a decent mobile web version would be just fine. At this point we are about a year and a half in and no signs of anything that will work on the tablets I am seeing more and more of at the gaming table.
Those new mobiles sites, and having them working in multiple devices do not come for free, they come up with development hours. And I see no indication anywhere that WotC would had done that extra support work if they had gone with a web app, so we would be probably in the same situation: tools only working in a few platforms.
Correct. But there are choices that would minimize the development hours needed to make the adjustments and provide a choice in platforms to access the data.
Anything can be done with enough development hours. Smart choices and a strategy just require fewer development hours.
I can agree that porting with a web app takes less time than porting with a native app. But developing a complex web app takes longer than a native app, so I don't think development would have been minimized overall. Maybe the project would had died under the weight of the initial development and we would have no character builder at all.
Either way, in the end it seems your problem is not so much with using .NET (as C++ would have had the same problems you comment for example) but with doing a native app. And the debate of native apps vs web apps has no clear winner.