Hybrid Apps - End of the Desktop-to-Web War
The idea of confronting the web platform and the desktop platform may not be entirely true. Some experts believe that now we are not seeing a confrontation, but a merger of these two platforms. Confirmation of this - the emergence of hybrid applications that combine those and other properties. Web platform, in principle, can not exist without a desktop.
“During my career, I heard many predictions that I did not believe in,” writes well-known programmer and entrepreneur Brent Simmons on his blog. “Apple will go out of business, six or seven websites will remain on the Internet, browsers will die soon, we will all be working on thin clients, Java will replace C / C ++ everywhere.” And now a forecast of the same kind has appeared: that desktop applications are dead and soon everything will work around the Internet.
In principle, there is some truth in this forecast in the sense that over time there will be less and less programs that do not use the web platform. The prediction is partly true, but the very idea of ​​“confronting” the desktop and the web does not make sense.
Let's see, Simmons says, what a desktop application and a web application are from such positions: where is the code executed? What type of code is allowed to execute here? What resources are allowed to use the program?
')
In the case of a web application, part of the code is executed on the server, but a large chunk is executed on the client, too. The browser — the desktop program — is assumed to be the default. And this browser renders HTML, runs JavaScript, performs network requests, plays audio, video and flash, stores some data locally, knows how to run other programs, etc. That is, any web application executes a large piece of code on your desktop. In fact, it will not work without a desktop program.
If we are talking about a web platform, then we mean a browser. But this browser also supports the installation of extensions and plug-ins. All these are real desktop programs , albeit created to work on the web.
Or take the desktop widgets. They are based on HTML and JavaScript, as web applications, but they have access to local computer resources, and in general can work offline without any need for the Internet.
Offline RSS reader is another example of a hybrid application.
What a modern desktop program you can take - almost everything works through the Internet. For example, the iPhoto photo manager is a typical desktop program, but if you connect a special module to it, it will read and generate RSS feeds.
Text editors understand HTML, can generate websites and update blogs. Graphic editors save pictures on remote servers. Google Desktop is looking for emails directly from the desktop, Webmail is a special browser for Gmail. We see how desktop programs extend functionality towards the web.
In the opposite direction, the process also goes. Look at Apollo , Silverlight , Slingshot , DjangoKit and POW — these systems implement the idea of ​​launching web applications on the desktop.
Here they are - hybrid applications. No predictions, they are already here.
via Inessential
“During my career, I heard many predictions that I did not believe in,” writes well-known programmer and entrepreneur Brent Simmons on his blog. “Apple will go out of business, six or seven websites will remain on the Internet, browsers will die soon, we will all be working on thin clients, Java will replace C / C ++ everywhere.” And now a forecast of the same kind has appeared: that desktop applications are dead and soon everything will work around the Internet.
In principle, there is some truth in this forecast in the sense that over time there will be less and less programs that do not use the web platform. The prediction is partly true, but the very idea of ​​“confronting” the desktop and the web does not make sense.
Let's see, Simmons says, what a desktop application and a web application are from such positions: where is the code executed? What type of code is allowed to execute here? What resources are allowed to use the program?
')
In the case of a web application, part of the code is executed on the server, but a large chunk is executed on the client, too. The browser — the desktop program — is assumed to be the default. And this browser renders HTML, runs JavaScript, performs network requests, plays audio, video and flash, stores some data locally, knows how to run other programs, etc. That is, any web application executes a large piece of code on your desktop. In fact, it will not work without a desktop program.
If we are talking about a web platform, then we mean a browser. But this browser also supports the installation of extensions and plug-ins. All these are real desktop programs , albeit created to work on the web.
Or take the desktop widgets. They are based on HTML and JavaScript, as web applications, but they have access to local computer resources, and in general can work offline without any need for the Internet.
Offline RSS reader is another example of a hybrid application.
What a modern desktop program you can take - almost everything works through the Internet. For example, the iPhoto photo manager is a typical desktop program, but if you connect a special module to it, it will read and generate RSS feeds.
Text editors understand HTML, can generate websites and update blogs. Graphic editors save pictures on remote servers. Google Desktop is looking for emails directly from the desktop, Webmail is a special browser for Gmail. We see how desktop programs extend functionality towards the web.
In the opposite direction, the process also goes. Look at Apollo , Silverlight , Slingshot , DjangoKit and POW — these systems implement the idea of ​​launching web applications on the desktop.
Here they are - hybrid applications. No predictions, they are already here.
via Inessential
Source: https://habr.com/ru/post/7636/
All Articles