It was something that had been discussed for a long time, and it seems that now the time has come for it to occur: Google intends to migrate applications from Chrome from desktop devices to mobile phones and, in this way, make the terminals that use them more useful.
Apparently, and on GitHub you can see a sample of what could be done (link), different tools have already been launched for independent developers to start working on these types of applications, initially operating systems Android and iOS the chosen ones. In addition, those already existing and those of Mountain View would be migrated.
By the way, there is a detail that is clearly indicative that this creation would be official by Google: the repository of tools is run by Michal mocny, one of the programmers of the company that created Android and Chrome. Additionally, it should be noted that in the documentation that has been published the name that appears for the project is Chrome Package App, and it would be available for use on the usual platforms used by the creators: Windows, Mac, Linux and also Chrome OS (using Apache Cordova for this). It is expected that the first results will begin to be seen in beta versions, as indicated Joe marini, Google developer.
Some more specific data
In principle, and as we have indicated, everything would be prepared for the creation of applications to begin for Chrome in the Android and iOS operating systems, and it is expected that the designs that appear will be published in the online shops corresponding to each of the operating systems. Regarding Android, everything indicates that the version that must be installed in the terminal is 4.x, although it could be lowered in some cases to 2.2.
Therefore, the specific creations for the Chrome browser, which are written in HTML, JavaScript and CSS, and that are capable of running outside of it could be in the game before too long. This would obviously give a major boost to Google's browser in terms of applications, which would become much more powerful and offer a very well-structured ecosystem: desktop and laptop computers, mobile devices and equipment that use Chrome OS (Chromebook). This way, your dependence on other third-party work would be significantly reduced.
The fact is that everything indicates that the bet is real and serious, and that the necessary steps are already being taken so that the applications for Chrome are a reality in the phones and tablets And even Google's own creations could be seen in their test versions. Will all Android devices be able to run these types of programs? What hardware will be needed to run them properly? We'll have to stay tuned to find out.
Today, the modern approach to bringing Chrome apps to mobile is through progressive web applications (PWA): are installed from the browser, can work offline, send notifications, access the system files and show insignia on the icon. Although they work offline, some functions require a connection.
Chrome on Android: What you can do today
Chrome for mobile integrates tools that increase productivity and security: Google Search with hands-free voice search, Google Lens to search for what you see with the camera and Google Translate to translate entire sites in one click.
In security, they stand out Enhanced protection to block threats in real time, Security check with proactive alerts and Google password manager to generate and save keys and notify you if there are leaks.
For continuity, Chrome allows synchronize Bookmarks, tabs, and passwords on your phone, computer, and tablet; create tab groups and use autocomplete of payments and addresses to save time.
Install and manage web applications (PWA) with Chrome
On your computer, install a PWA by opening the site in Chrome and choosing the option from the menu. Install page as an application (Some sites may have an Install button in the address bar.) To uninstall, open the app and select uninstall and, if applicable, also deletes associated data. In chrome: // apps you can create Shortcuts, configure that it is open when logging in and adjust the setting of each app.
On Chromebook, uninstall from the applications menu by right-clicking on the icon and choosing uninstallChrome will also notify you when an app wants to change name; accept the change or uninstall if you suspect malicious activity.
Extensions on Android: real options and alternatives
Chrome on Android does not offer native support for extensions. If you need an ad blocker or to automatically accept cookies, you can use browsers that support the Chrome Web Store on mobile:
- Yandex Browser: enter the accessories store, press Add to Chrome in the desired extension and manage the add-ons in your Extensions catalog.
- Kiwi Browser: opens Extensions from the menu, press + (from store), choose the extension and tap Add to Chrome.
- Flow: includes a standard ad blocker on YouTube and WOT; add more by opening the store and using Add to Chrome.
If you value privacy and native blocking, Brave is another alternative; it offers a built-in blocker and its own synchronization. Keep in mind that No. You can sync data from Chrome mobile to Brave using your Google account; the full import is usually done from the desktop.
There is also a variant of Chrome for Android with extension support Experimental. It's not on the Play Store and requires manual installation. Loading extensions involves downloading files. .crx and enable them in chrome: // extensionsThe experience is limited and many extensions they do not work correctly.
For administrators: policies and app deployment
From the Google Admin console you can force the installation of web apps, IWAs, Chrome extensions, and Android apps. Installation policies include: Force installation; Force and even fix on the shelf from ChromeOS; Allow installation; Block; and, for kiosks, Installed o Not installed. You can define settings at the level of users and browsers, kiosks y managed guest sessions.
Advanced settings include: extensions mandatory incognito (check the incognito availability policy), start automatic of PWA/IWA on ChromeOS, inclusion in collections from the Web Store, company verification and specific policies in JSON for extensions and PWAs.
In kiosks you can allow the app to manage the Energy, Activate unified desktop on multiple monitors, enable on-screen keyboard, to allow plugins, convert the top row to Function keys, Open one full-screen window per screen and define a maintenance window. It is also possible monitor the status, go up system logs and configure the rotation from the screen.
Troubleshooting: If the icons do not load (for example, in Demo mode), use EnterpriseCustomLabel y EnterpriseLogoUrl to define a custom icon and name. For a reliable first-time installation, use dedicated URLs for Google PWAs (Gmail, Chat, Calendar, Drive, Docs, Sheets, Slides, Keep, Meet) and avoid redirects.
On the page Apps and extensions You will see the name and ID (Android, Chrome, Web or IWA), the installation policy applied and if there is fixed versionsTo remove an app and associated data, locate it in Users and browsers and changes the policy to Block.
Via: Android Authority. Chrome continues to evolve: between powerful PWAs, cross-device syncing, and alternatives to using extensions on Android, it's now possible to cover most use cases without losing to maximise security and your enjoyment. nor control, and organizations have advanced policies to deploy, set and audit applications throughout its park.
Google and related marks and logos are trademarks of Google LLC. Other company and product names are company brands with which they are associated.