That's like saying there are many websites out there which have no reason to ever have been made because before browsers they would simply have been BBSes. Eventually something better comes along and things adapt to that.
Really, I fail to see a reason for using Objective-C or Java for writing mobile apps other than if it was some complex 3D game. But there are many reasons not to (code reuse between platforms!, plus IMO, as bad as people say JS is, I think it's a far more pleasant [esp. using CoffeeScript] language to program in then either Obj-C or Java).
So maybe the web browser is dead, because it's a "mobile app" accessed from some proprietary store vs a URL, but that's like saying the web browser is dead because someone pinned a web site to their desktop and uses that to access it instead of a URL. I just don't see why the distinction is needed.
I guess it comes down to ownership. If your bits are in someone else's cloud, I could see how that might cause concern for people that buy DVDs or have terabytes of stuff that most likely doesn't belong to them in the first place.
And the browser is a good target for progressive enhancement-- something that hasn't taken off on the native end of software development.