I am confused about Chrome hosted app vs packaged app.
Hosted app
- is where we hosted our web in server side
- Required internet
Packaged app
- hosted the website in client site
- Just like a native app
- No internet require.
I am interesting in Packaged app but can I make the packaged app just like drive.google.com or gmail?
When they are offline then using packaged app and when they are online and start syn the pending offline files to server. Or packaged app is just everything in offline?
This might help you out.
https://developer.chrome.com/webstore/choosing
Anyway you will have to host Packaged App if you want it cross platform i.e. web, mobile etc.
If you want any functionality offline and online you want to go with the Packaged App. One way you can think about it is Packaged App download all the files required to run to the local machine. With Hosted Apps, all those files live on a web sever somewhere.
Packaged Apps are just like like regular web apps, but they have extra capabilities that allow them to run offline.
Also, Packaged Apps are not required to support offline.
Related
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.
I have a web app and have built a respective Electron app for Windows. I want to do the same thing for both IOS and Android without dealing with stores. The app is fully web but it will be hosted only locally, both front-end and back-end. So every client will have its own server in its own intranet.
The problem is that I do not want to open the local IP in every client browser and do 'Add to homescreen' manually.
The ideal approach would be to have an automated way to create and install the PWA on various local IOS, Android devices just as you would install an application in Windows.
My question: Is it possible to automatically create a PWA without having to go through the manual 'Browser' way?
I have an app to which I'd like to add cloud sync for the application's data files.
The desktop version of the app is written in Java and runs on Windows, OSX, and Linux. mobile version is an Android app. To further complicate matters, the Android app is available in two versions, free and paid, with different package names.
Google Drive API allows files to be stored and manipulated in an application data folder. Is it possible for all of the above versions of the app to share the same application directory? What exactly constitutes an "application"?
If the Android app is uninstalled, will the application folder be removed?
A drive app is distinct from an android/desktop/web app. All of those can use the same drive app. The drive app is the entry in the developer console. Just use the same developer console app id and credentials in all your variants.
I have (had) a hosted app in the Chrome Web Store, built using the following Developer documentation:
https://developers.google.com/chrome/apps/docs/developers_guide
After being in the Chrome Web Store for years, I recently received an email saying my app does not comply:
Your item did not comply with the following section of our policy:
Do not post an app where the primary functionality is to install or
launch another app, theme, or extension. For example, if your app’s
primary function is to launch a desktop app that the user has already
installed, that is not allowed. Another example is a packaged app that
just launches a website.
My question is: Did the rules change? A Hosted App IS an app that launches a website. Does anyone know what to change in a Hosted App to make it compliant again?
A Hosted App, a Chrome App (successor to Packaged App), and a Chrome Extension are three separate things, distinguished by how their manifest.json file is set up. What this email appears to be saying is that you're not allowed to have a Chrome App (which they call a packaged app) whose only purpose is to launch another app or a web site. They are saying nothing about Hosted Apps, which continue to be allowed, as far as I know. (I have one in the Chrome Web Store myself.)
Is your app truly a Hosted App? Or, is it a (legacy) packaged app or a Chrome App?
I know what is metro app (just did some research) my question is where metro app runs. By my understanding :
Detktop app: running on your local machine with .net framework, and present data to user, you can launch/close it.
Web app: Publishing on IIS server, running from server render html to client, user can send request and get result.
Now, Metro app: is it just distributed on windows store, user can download/install it and run from local as same as desktop? or run from store, render something to user like web? or maybe some new working styles, can user close it?
Metro Style App was a working name before Microsoft settled on Windows Store Apps.
Windows Store Apps just like desktop apps run on local machine, but are often architected in more modern ways where the app would often connect to web services or push notifications that run in a data center. The UI though usually runs on local machine even if it is written in html/js with winjs.
The biggest difference is distribution - web apps run on the server so you only need to navigate to them in your browser to run the latest version. Desktop apps need to be installed - either with xcopy-style install, Windows installer or perhaps the ClickOnce technology. Store apps are distributed through the store which makes them easier to install and update than desktop apps as well as monetize, but are sandboxed (have limited access to local machine resources) for security.