I have a very simple chrome app:
manifest:
{
"manifest_version": 2,
"name": "App Name",
"description": "Short description",
"version": "0.4",
"app": {
"background": {
"scripts": ["background.js"]
}
},
"icons": {
"48": "/images/logo48.png",
"64": "/images/logo64.png",
"128": "/images/logo128.png",
"256": "/images/logo256.png"
}
}
background.js:
chrome.app.runtime.onLaunched.addListener(function() {
window.open("https://google.com/");
});
This application is not supported on this computer. Installation has been disabled. The following problems are detected:
This app runs only on Chrome OS
Does anyone know what I have done wrong? I simply want my app to act as a shortcut to the website, nothing more.
You may refer with this Transitioning from Chrome apps on Windows, Mac, and Linux documentation. Be noted that Chrome packaged and hosted apps will be discontinued on Windows, Mac, and Linux over the course of now and early 2018. It is also stated in this Chromium Blog.
Starting in late 2016, newly-published Chrome apps will only be available to users on Chrome OS. Existing Chrome apps will remain accessible on all platforms, and developers can continue to update them.
In the second half of 2017, the Chrome Web Store will no longer show Chrome apps on Windows, Mac, and Linux, but will continue to surface extensions and themes. In early 2018, users on these platforms will no longer be able to load Chrome apps.
Hope this helps!
Related
I just want to know, if my Ionic 5 app is running in a browser, or in the webview of a compiled app.
Platform does not work: https://ionicframework.com/docs/angular/platform
It just tells about the device. But when I run it in chrome on an android device, it returns the same platforms as when I run it compiled.
Analysing the URL to check if it the webview url works, but not when using capacitor live reload. Because than it is the same URL like locally in the browser. And by the way, analysing the URL feels like an ugly solution.
Is it really that hard to get this simple and important information, or do I just miss something?
Edit:
Platform output
Chrome in Ubuntu with ionic serve: ["desktop"]
Chrome in Android: ["android", "mobile", "mobileweb"]
Android with capacitor livereload: ["android", "phablet", "mobile", "mobileweb"]
Android compiled: ["android", "phablet", "cordova", "capacitor", "mobile", "hybrid"]
Check Capacitor.getPlatform()
If returns web then it’s running as website, if returns ios or android then it’s native.
Or can also check Capacitor.isNativePlatform().
https://capacitorjs.com/docs/core-apis/web#getplatform
I am attempting to create a kiosk app for an Acer Chromebase that I have. I know the Chromebase is setup to accept and run a kiosk app successfully as I used a publically available kiosk app to test and the Chromebase ran it. So that part of it I know is good.
I have created a kiosk app by researching all available documentation and posts I could find, and I do have "kiosk_enabled":true in the manifest.json file. I have copied this app over to the Chromebase, loaded as an Unpacked app, and it ran successfully within a window. I have then taken that app and published in the Chrome store, setting the visibility to Unlisted and not Private. I can then go to Chromebase, put the link into the browser and it finds it in the store, and I can install it and run it, and it will run successfully within a browser window.
Now for the problem. When I go to "Manage Kiosk Applications" and put the ID of my app in there, it comes back with a completely useless "Invalid Application" error. It would be nice if it told WHAT was invalid about it, but it doesnt. It doesnt matter if I use the App Id, or the store url link to the app, I still get Invalid Application. Like I said earlier, I did get an app Id to another kiosk app I found out there and when I put that Id in there it accepts it and installs it, so I know it can be done, but mine is failing.
I have used the App Builder to create this kiosk app.
Here is my manifest.json file:
{
"name": "DIDI Kiosk",
"version": "1.4",
"manifest_version": 2,
"minimum_chrome_version": "37.0.0.0",
"permissions": [
"webview",
"power",
"storage",
"videoCapture",
"geolocation",
"pointerLock",
"system.display",
{
"fileSystem": [
"write",
"retainEntries",
"directory"
]
},
"accessibilityFeatures.read",
"accessibilityFeatures.modify"
],
"app": {
"background": {
"scripts": [
"js\/foam.js",
"js\/cab.js",
"config.js",
"background_main.js"
]
}
},
"kiosk_enabled": true,
"default_locale": "en",
"icons": {
"128": "img\/128.png"
}
}
And here is my config.js file:
window.config = {
"model_": "AppConfig",
"id": 1,
"appName": "DIDI Kiosk",
"version": "1.4",
"homepage": "https://v1.didi.dansmill.com:8080",
"enableNavBttns": false,
"enableHomeBttn": false,
"enableReloadBttn": false,
"enableLogoutBttn": false,
"kioskEnabled": true
};
Does anyone have any idea just what the criteria is in the "Manager Kiosk Applications" are to validate an app?
}Dan
I think It would be a nice idea to try to install as kiosk app the app that google provides as example:
See "Or, create a Chrome kiosk app with navigation controls:" here: https://support.google.com/chrome/a/answer/3316168
If you succeed, then It means your app is missing something. Perhaps on the manifest?
If not, then perhaps there is something missing on the procedure itself. Here (https://groups.google.com/a/chromium.org/forum/#!topic/chromium-apps/jztb4P_CE0c) a guy had the same problem and he finally could install the app with these extra steps
I create a account in the chrome web store.
I upload my test app and publish my test app.
And then I install my test app in chrome web store.
After these, I can start my test app on kiosk mode.
But I believe you already did that...
Anyways, I think the first thing to know if you are able to install the sample app as a kiosk app.
I have a working google app script web app and trying to migrate it as a progressive web app. I googled but found no documents on how to do it.
I found a link describing how to migrate a web app into a progressive one in the fallowing link (on the google site):
Migrate Your Site to Progressive Web App
I started applying the steps but, when it comes to change the default manifest file (appsscript.json) I got an error like "Invalid manifest:unknown property name".
The original manifest content was :
{
"timeZone": "Europe/Istanbul",
"dependencies": {
},
"webapp": {
"access": "MYSELF",
"executeAs": "USER_DEPLOYING"
},
"exceptionLogging": "STACKDRIVER"
}
The lines I added were as the above link dictates:
"name": "The Most Awesome Dragon Site",
"short_name": "MYFIRSTPWA",
"display": "minimal-ui",
"start_url": "/",
"theme_color": "#673ab6",
"background_color": "#111111",
"icons": [
{
"src": "icon-192.png",
"sizes": "192x192",
"type": "image/png"
}
]
When i check the info about google manifest file content there were no property names like name, short_name, display, start_url etc. (see the link bellow)
Manifests
So does this mean a google app scripts web app can not be migrated to a progressive web app?
İf possible , where to find info on how to?
Thank you.
These two manifests are very different and perform different functions.
Apps Script Manifest - appsscript.json
An Apps Script project manifest is a special JSON file that specifies a basic project information that Apps Script needs to run the script successfully.
This file tells Google infrastructure how it should configure and run your script.
PWA Manifest - manifest.json
This manifest file describes meta information about a site, such as how it might look when added to a user's home screen.
This is a JSON file that your HTML links to and user's browsers will download. It's similar to how you would make and serve HTML but it's different content.
I want to deploy an existing JS app as a Packaged Crome App to make it distributable in the Chrome Web Store.
In "legacy packaged apps", there is/used to be a way to specify an options_ui page (in old legacy (legacy-legacy?) apps it was options_page) which would be accessible via a special link from your app, or by automatic link from from within chrome://extensions.
There doesn't seem to be any mention about how to migrate the options_* feature, but if the manifest.json of a Chrome App has the options_ui key it generates the following warning on the extensions page:
'options_ui' is only allowed for extensions and legacy packaged apps, but this is a packaged app.
(References)
Chrome Developer: Migrating from a Packaged App to a Chrome App or Extension
Stack Overflow: Difference between a Packaged App and a Legacy Packaged App in Chrome
You can create a context menu item on your icon to open your options.
Add the "contextMenus" permission, then add something like this to your background page:
chrome.runtime.onInstalled.addListener(function() {
chrome.contextMenus.create({ id: "options", title: "Options", contexts: ["launcher"] })
})
chrome.contextMenus.onClicked.addListener(function(info) {
if(info.menuItemId == "options") {
chrome.app.window.create("options.html")
}
})
I want to write my app for Firefox OS. What kind of languages (like Java for Android and Objective C++ for iOS) and tools (like Eclipse, Xcode) to use?
Apps for Firefox OS (previously known as Boot to Gecko) are developed using HTML 5 and Javascript.
References:
http://www.mozilla.org/en-US/b2g/
https://developer.mozilla.org/en/Mozilla/Boot_to_Gecko/
You can use any web development tool you like. Firefox has a lot of built-in tools to check out: https://marketplace.mozilla.org/developers/docs/devtools The responsive mode tool is very useful for Firefox OS / mobile apps.
Besides tools, the most important skills to learn are techniques for building web apps: https://marketplace.mozilla.org/developers/docs/references
If you are a web developer, then I must say you are the master of Firefox OS already! It's all about HTML5, CSS and Javascript. Any development tool like Eclipse, Visual Studio, Notepad++, WebStorm and etc. can be used. But there is one and only difference between Web application and Firefox OS application. You have to add a manifest.webapp file in the root directory of your project. Let say your project files are like following
css
js
index.html
Now you have to add a manifest.webapp file in above and it should look like following
{
"name": "My App",
"description": "My elevator pitch goes here",
"launch_path": "/index.html",
"icons": {
"512": "/img/icon-512.png",
"128": "/img/icon-128.png"
},
"developer": {
"name": "Your name or organization",
"url": "http://your-homepage-here.org"
},
"default_locale": "en"
}
So your app is ready! What's next? App deployment ......
You can deploy your app as following ways..
Packaged App : All files will reside inside in your mobile
Hosted app : Files will be hosted in a remote server like IIS, Apache and etc. Mobile will know the manifest.webapp file URL only.
And that's all about firefox os app development. I hope this post will help future beginner as I am very late to answer this question.