akemiiwaya at May 13th, 2014 16:00 — #1
Originally published at: http://www.howtogeek.com/189144/what-are-the-benefits-of-chrome-apps-that-duplicate-a-website/
There are quite a few web apps for Chrome that seem to be nothing more than ‘prettified’ shortcuts to our favorite websites, but is that all they are, or is there more to them? Today’s SuperUser Q&A post has the answers.
michaeltunnell at May 14th, 2014 00:25 — #2
It seems to me that the only benefit they have provided is the removal of the Browser Chrome.
I would also point out that these are bit useless when you take into consideration Image & CSS Caching.
They don't even allow for independent sessions...basically what real problem do they solve? Other than removing browser chrome, what function do they provide worth bothering with? I suppose they are easier to install than doing it with other browsers but without the individualized sessions, I just don't see the point.
wilsontp at May 14th, 2014 11:29 — #3
Conceptually, it's just another shortcut menu, but if I understand correctly, it's also the only way to distribute web apps that use the Native Client.
The Native Client allows web sites to distribute compiled applications written in C or C++ that operate directly in the browser. This sounds similar to a plugin or ActiveX component, but unlike plugins and ActiveX components, native client apps allow you to run your code on any architecture: ChromeOS, Windows, MacOS, Linux, or whatever else supports Native Client apps.
jlee1 at May 14th, 2014 14:53 — #4
I use to create "apps" as a link like a bookmark. I didn't know how they "guess" which webpages I use the most and display them at the base screen. I wanted more control and that gave me that. For those who don't know how to do that, it's nice that some sites can do it for them. I think it is going to be an actual function in the latest version of chrome.
michaeltunnell at May 14th, 2014 20:47 — #5
It allows you to use them on any platform but only in Chrome. Firefox users like myself don't benefit at all so it is taking something like the web that is meant to be universal and locking it to a browser.
They don't work on mobile which regular websites do...they are almost entirely pointless.
I am using my phone right now and discourse works great...require a chrome app and then I'm pointlessly left out.
wilsontp at May 15th, 2014 13:17 — #6
You're bashing Chrome because the desktop features don't work on a mobile browser?
There are some advantages to using the app store - some are just marketing, and some are technical. You don't have to launch apps from the app store (going to a URL can launch exactly the same code as using the store link), but some Chrome apps do require the security model offered by the Chrome app store, and I'm perfectly fine with using that when it's needed.
michaeltunnell at May 17th, 2014 15:18 — #7
You picked one aspect of the issues I pointed out of which were many issues. If you to refute my points you have to refute or acknowledge them all not just pick one and try to boil my comment to a single issue that you think you can break apart.
Besides you failed to break it...The web is meant to be flexible meaning desktop and mobile at the same time which is possible without these chrome apps but not possible with them.
What runs on your phone is different code than what runs on the desktop.
Actually no it isn't. Responsive Design was invented to allow the same code to generate websites for all devices including phones and only reordering or replacing content through stylesheets. The core code stays the same.
wilsontp at May 18th, 2014 03:07 — #8
Again, Chrome has API's that Firefox doesn't, and those API's are restricted to applications that have been submitted to the Chrome App store so that users can voluntarily
This isn't any different than ActiveX plugins, which only run in Internet Explorer.
This isn't any different than Frames, back in 1995, which only worked in Netscape.
The web evolves and changes. There will always be some new API that only works in one browser. Not that long ago, it was HTML5... next week, it'll be something else.
system at May 23rd, 2014 16:00 — #9
This topic was automatically closed after 10 days. New replies are no longer allowed.