HTML is used mostly on the WWW. The Internet is document format agnostic and application protocol agnostic.
My apologies if I was coming across like an idiot... I was just trying to keep things at a non-technical level to make the conversation more interesting.
... You should always capitalize Internet when referring to it.
Um, no.... I don't think it's that Important.
A browser does one thing and does it really well.
In my opinion, a browser does many things -
often really well. It plays video, it keeps bookmarks, it plays audio, it keeps passwords (or not) and other forms. Sometimes it plays Flash (capitalized because it's a proper name) and other media. It works across the internet (lower case, sorry) or it can work across a local network, or it can be used on a single machine. I can even replace the htt protocol with an ft protocol (go ahead, tell me I should have used the redundant 'http protocol' / 'ftp protocol' makes as much sense as capitalizing The Internet
)
Apps and Applications are the same thing. It's what is called an abreviation.
Not everyone agrees... I believe that there is a semantic transition happening at the moment. People are tending to use the term "app" differently than "application". So, while it may be technically true that "app" started as just an abbreviation - the meaning, imho, is evolving to reflect the nuances of the actual state of affairs. The OP was, in my opinion, using the term "app" to mean a small program with limited functionality. The question was - were small and simple programs with limited functionality going to replace browser-centric interface that we currently use?
I was pointing out that the internet (sorry, lower case) as we know today had already evolved from the internet (apologies, lower case again) that we knew of the past. My point is that we can't just assume that the internet (there's that darn lower case again, sorry) as we know it today is going to remain that way. And by "internet" - I mean the way that we interact with it.
The OP wants to know if we're regressing back to a fat client model, where every vendor and service provider has to make you download/install a proprietary application that uses the vendor's protocols in order to access data/services given by that vendor.
With respect, I don't agree that was the question. "Apps" don't have to be tied to a particular vendor and their product (even though many are). However, an app can just tell you the time here and in NFLD, or an app can aggregate data from several independent servers and present a table view (for instance the price of gas in Metro Vancouver. In both cases the HTML browser-centric view is replaced by an app-centric view.
The web browser is an application that implements a standard (http) to transfer documents formatted in a standard way (html) to present to the user. It thus doesn't require the vendor to provide and support a fat client application, only to support the open standards.
But HTML is primarily an presentation standard - it standardizes the view that is presented to the user ... not how the data was retrieved to be put into that view. In an app-centric interaction the app creates the presentation and other protocols are used to retrieve the data. As an e.g., just about any FTP program. If the FTP application was trimmed down to the point that it became an
app (perhaps it merely showed the user the document names on several different FTP servers?) then that would be a great example of where I think the internet (again, apologies... lower case) is heading.
Are you sure we want to go back to that ? Obviously not.
Maybe I do... you don't know me... I may even want to go back to the days of Big Iron and Dumb Terminals..... (VBG)
But iOS and other mobile application developers are being smart.
Yes...
Most applications that can just be a web site are just that, websites. ....
It becomes about marketing. The Web application might be quite sufficient, easier for you to manage and reach a broader audience, but Apple and Google have made their stores such an integral part of the experience that people don't go elsewhere. So you're stuck going the fat client route if you want in on the action.
But this mostly applies to commercial transactions... there is lots of data on the .... internet (wow, another lower case, eh?) that are just raw data.
Which is a sad state of affairs.
What I find sad is how much data is being commercialized. But that is another topic for another day.
ps Be glad that I don't use tHe IntErwEbZ - eH?