Standalone chrome applications - google-chrome

Currently I am exploring the possibilities and features of Google Chrome apps. As I see to run chrome apps we need to distribute them through chrome App Store. Could we develop a application as a chrome app, which will not need to release to general public or for a limited audience?
Is there anyway that we could package it to native OS executable like .exe in windows or .app in MacOS. So for users who doesn't have chrome installed will also can without any issue. Or at least could we distribute without submitting it to the App Store.
Also I am wondering whether we can run another application through chrome apps? For example I am planing to develop a java application and start with the chrome app.

You can distribute a Chrome App without using the Chrome Web Store, but you'll have to explain to users how to install it, and it's a little tricky: They have to open the Extensions window in Chrome and then drag the installation file to that window. Upon dropping it, there will be a dialog asking them if they want it installed. (They can't just double-click on a file or do anything else that's easy like that.)
Chrome Apps can't directly launch native apps, but they can communicate in various ways with native apps (or any apps) once those other apps are running.
(Some parts of your question are ungrammatical, so I can't be completely sure what you're asking, but the above is what I think you're asking.)

Chrome Extensions are only installable from the Web Store, but Applications can be privately hosted with some provisos: https://developer.chrome.com/extensions/hosting

Related

chrome.enterprise.deviceAttributes availability for force-installed PWAs in chrome enterprise

I'm trying to determine if I can access any browser api for chrome OS that will allow me to identify the device that its running on when the application has been force-installed in kiosk mode as a PWA.
We're running into exactly the same issue right now. The correct path seems to be to create a PWA and to connect it to a (pre-installed) extension that has access to the enterprise.deviceAttributes:
See https://developers.chrome.com/apps/migration:
"If there is a capability that your Chrome App has that the regular web platform can't provide, it might be available as an extension API. In this case, you use a progressive web app together with an externally connectable extension your web app can send messages to."
enterprise.deviceAttributes are only accessible if the calling App/Site is pre-installed to the device and not loaded dynamically, so it cannot run in the PWA by design.
But with this tutorial, it seems possible:
https://developer.chrome.com/extensions/messaging#external-webpage
We're looking into that right now and will post our progess here.

How to silent Install chrome extension on Windows 10 Technical Preview without using a developer version of chrome.

I have a problem getting a chrome extension to work on Windows 10 Technical Preview. I have this extension hosted in Chrome Web store. However when my i run the .exe on my pc, which is supposed to install a client on the pc and an extension on chrome, i cannot see the extension in the chrome extensions.
But when i use the developer version of chrome, i can see the browser prompting me to accept/disable the extension.
What am i missing here? I am pretty new to chrome plugins. Any suggestion/help would be greatly appreciated.
Thanks
Google Chrome (unfortunately) no longer allows private or local crx files to be installed as extensions. You must host it on the Google Chrome app store. From within the store you can make it private to a specific domain, or limit the app to only those within a Google group (they must use their Google account for access to the install).
Deployment of plugins that work within our intranet has suddenly become a major pain. I'm really surprised they couldn't come up with a better solution for this.
https://support.google.com/chrome/a/answer/2663860?hl=en

Can I deploy an HTML5 application using the WebAppRT executable?

I see that the lastest versions of Firefox come with a webapprt.exe and webapprt-stub.exe executable. I think that they are for the Open Web Apps system but I would like to know if it's possible to use the WebAppRT container with external made applications. I mean that I could distribute the WebAppRT executable, the shared libs required and my HTML files and deploy it offline without having Firefox installed.
Why?
What do you mean by "external made applications"?
Why don't you just create a web app as explained in Building Web apps - App Center | MDN ?
It will take care of the details and allow your app to reach more platform than doing it manually. For a glance see Platform-specific details of app installation - App Center | MDN
You don't have to do anything special to install apps on different platforms. All the information you need to provide, such as the app name, is contained in the app manifest. Here are some platform-specific details about how apps are installed on each platform. These details assume that Firefox has been installed on the platform.
To make that path easier, you can follow tutorials or clone an existing open-source web app that has something in common to see how it's done.
What did you mean?
If you mean to just manually locally install a some app that you write, the simplest thing to do would be to install any app, look at what's been done and replicate the steps with your app. But what's the point?
My guess is: it will work only if the local OS has a platform to actually execute the app. Then that platform will also be able to install the app properly. So, it will be simpler to you to just make a regular web app and have it installed through standard means.
Or were you thinking of something else?

Will the new Chrome extension restrictions allow local installs of a packaged app?

Google is changing Chrome's policy to no longer allow installation of extensions in any way other than through the Chrome Web Store. However, their wording is a little unclear. They state:
We’ll continue to support local extension installs during development as well as installs via Enterprise policy, and Chrome Apps will also continue to be supported normally.
But it's unclear whether they mean ChromeOS apps, or packaged apps as defined by an "app" section in the manifest.json. Do they mean packaged apps can still be installed outside the Chrome store?
http://blog.chromium.org/2013/11/protecting-windows-users-from-malicious.html
"ChromeOS apps" and "packaged apps as defined by an "app" section in the manifest.json" are one and the same thing. And yes, packaged apps can be installed outside the Chrome Store in their unpackaged form (click the "Development mode" checkbox in chrome://extensions page). Otherwise app development would be seriously hindered.

Centralizing management of chrome packaged apps in private network

Is it possible to declarative install, uninstall, update chrome
packaged apps on client machines from server (or make all this
operations with system scripts)?
Is it possible to make local shell
aplication to navigate between chrome packaged apps?
Use case: educational private network (schoolclassroom) based on chrome apps. After loading device, user see custom shell. User can navigate between chrome applications, using shell. User do not touch system, or chrome at all.
Also, aministrator could add application on every client system, using some scripted software management system...