Posts Tagged Chrome
Google has started the process of rolling out an update to the Camera app that is included in ChromeOS. The updated app features a new user interface that puts more emphasis on the content, which in the case of a Chromebook is probably the user. While that is nice, most users will probably be more interested in the features that are described as “in the pipeline:”
- video recording
- the ability to upload to YouTube and Google+
- Syncing of pictures across Chrome devices
Unfortunately, no timeline for the availability of these new features was provided. The new version of the Camera app is being rolled out to users in the typical Google phase fashion. However, users impatient for the update can head over to the Chrome web store to grab the update.
Come comment on this article: Chrome OS camera gets update to interface, framework for more features
Via: The Next Web
Source: Mobile Chrome Apps (Github)
Chrome apps have been seeing a lot more attention as of late, thanks to Chromebook sales and Google themselves pushing web-based applications. There’s definitely some good stuff that is only useable on Chrome, however it looks like Google may be working on a tool that will help them convert these Chrome apps to work on both Android and iOS.
Dubbed ‘Mobile Chrome Apps’, the project is being worked on by Google Software Engineer, Michal Mocny, and was spotted on GitHub. Utilizing Apache Cordova, the tool will package up all the web-based code of the Chrome app into something that will look like a standard mobile app on whatever platform is being used. A pretty nifty tool for developers who want to port their web apps across, particularly as these packaged apps will be able to be submitted to the app stores on the mobile platform.
The tool isn’t expected to be in beta till January next year, but seeing as its on GitHub, you can probably take a gander yourself if you’re a bit of a code monkey. Do you see this kind of tool being useful? What about a tool that converts mobile apps to Chrome apps? Let us know what you think in the comments.
When Google introduced Android 4.4 KitKat to the world, one of the benefits they touted was Project Svelte, a concerted effort to minimize the memory footprint to encourage the system’s deployment to older or less powerful hardware. Trying to make Android run easier on more hardware is not the only way Google is trying to reduce fragmentation and in effect “flatten” the world. They are also working on efforts that blur the line between the desktop and mobile platforms like Android and iOS. The latest example is news that Google is poised to enter the beta stage in January 2014 with “Mobile Chrome Apps,” a project to build a toolkit for developers so they can more easily deploy the apps they have built for Chrome on the desktop over on mobile operating platforms like Android and iOS.
The bottom line for developers is a way to streamline the process of coding apps that can run on several different platforms. Another benefit may be encouragement for consumers to settle on a single app to use for a task no matter what device is used.
The current effort can be found in a GitHub repository maintained by Michal Mocny, a Google software developer, that is named Mobile Chrome Apps. At this time the documentation suggests Android 4.x will be supported initially, but older versions, as far back as 2.2 or 2.3, may eventually be supported. Meanwhile, iOS support is only listed as TBA.
Come comment on this article: Chrome apps on Android and iOS may be as close as January 2014
Google is set to bring Chrome packaged apps to mobile, as well as desktop. The apps in question, which recently launched as “Desktop apps” in the Chrome Web Store for Chromebooks (or “Offline Apps” elsewhere), act just like web apps except they operate outside of a web browser, and don’t need an Internet connection. While we’ve long expected Google to bring Chrome extensions to mobile, this represents a new frontier in Google’s platform functionality.
The project was discovered by The Next Web, who stumbled across a GitHub repository named Mobile Chrome Apps. Innocuous at first, it quickly became interesting when the project was found to be led by a Google software developer, Michal Mocny. The project is designed to give Developers a well rounded experience in programming and launching Chrome apps across platforms, and includes everything from bug fixes to testing.
Interestingly, the apps are meant for both the Play Store and App Store, but no nation of Windows Phone is made. The requirements suggest that Android 4.0 and up will be supported, with iOS functionality marked as TBA.
Chrome apps are written in HTML5, which has traditionally been reserved as a web-centric markup language. By offering HTML5 apps for offline use, Google is pushing the boundaries of operating systems, essentially challenging the need for one altogether. We see tho currently with Chrome apps finding a home on the Windows home screen and menu bar. By crossing into mobile, Google is continuing to push boundaries with the simplest of technologies.
The apps are said to be ready for beta testing as early as January, and we’ll be sure to watch for them in the Play Store. We’d like to think a Play Store update would serve as a precursor for a launch, as these would likely get their own section within Google’s storefront.
- Chrome Beta for Android updated, brings fixes and a new ‘Vibration API’
- Chromecast may be going international, according to Google job postings
- Chromecast SDK hackathon scheduled for December, Android app updated
- Always listening “OK Google” feature lands on the desktop via Chrome extension
- Chromecast-compatible apps now earmarked in Google Play Store
Developing a mobile-friendly website can be daunting. How do you account for the many, many devices that will see your page? If you grab Google’s new Chrome 32 beta, that kind of testing should be trivial. The desktop browser’s DevTools for Mobile can now emulate the behavior of mobile gadgets down to their display resolutions, sensors and touch input. Those who need to test on real hardware will have an easier time, too — Chrome 32′s new USB support lets you screencast an Android device’s browser to see how code runs without leaving the developer environment. Many of us normal web denizens won’t see the benefits of the updated DevTools, but site builders eager to save time will want to visit the source links.
Via: The Next Web
Google’s Account Access Page has been given a facelift today, bringing a better way to see which Chrome apps and Android devices are accessing your information. Often times, we download an app and don’t think twice about what it’s asking for, only to later wonder just which of our apps and services are accessing things like contacts or web search history.
Whatever operating system you’re using, if it accesses your Google information, the Account Access Page has you covered. The page now shows larger thumbnail images, and lists which devices are linked to your account. It also shows all devices that have been given access to your information, and allows you to revoke that access. We were a bit surprised at how many older devices we had listed!
Of course, if you want to access individual Android app permissions, that has to be done via the device itself. You can revoke access to devices or Chrome apps, but not alter them in any way. Like anything else, it’s a bit of an all-or-nothing proposition with permissions.
The updated page does clear things up a bit, and makes it really easy to manage what is accessing your info. We hope this paves the way for further advancements in managing your device and apps in a macro sense, especially via Android. We like Android Device Manager, but that’s an emergency utility.
- YouTube fighting spam and impersonations in update to Google+ comments
- Always listening “OK Google” feature lands on the desktop via Chrome extension
- Visa introduces V.me, an online payment solution to rival Amazon and Google Wallet
- Google Play for Education gets Nexus tablet setup app
- Chromecast-compatible apps now earmarked in Google Play Store
If you head over to the Chrome Web Store now, you can add an extension that activates voice search by using the ‘Ok Google’ hotword. On their Google+ page, Google unveiled the new desktop extension with a GIF showing just how effective this new feature can be. While prepping your Thanksgiving dinner, Google exclaims that “rather than stopping midway through to wash your hands and type in a search, you can just speak to your laptop” by simply using the hotword. If you have a Moto X or Nexus 5, then this feature should be very familiar to you.
Hit the break to see the ‘Ok Google’ hotword in action, a video, and a link to the Chrome Web Store.
Come comment on this article: ‘Ok Google’ hotword heads to Chrome, just in time for your Thanksgiving cooking
Ever wanted to have that hands-free experience of activating Google Search with your voice but are currently confined to working on your computer? Google has you in mind when it made this Google Voice Search Hotword extension for the Chrome web browser which brings the now iconic “OK, Google” phrase to desktops and laptops.
Simply install the extension, which you can download from the link below, and you’re good to go. Of course, you’ll need to have a mic installed on your system, but a lot of laptops come with those nowadays. This will allow you to then simply use voice commands not only for searches but also for things like setting reminders and calendar events, doing unit conversions, and more. You can always type in these search terms or commands yourself, but speaking out commands to your computer is much more convenient and cooler, at least if you’re not in a situation that would make it awkward.
The extension is currently in beta and is definitely far from perfect. It does have some limitations, aside from being unsurprisingly exclusive to Google’s web browser. The hotword only works when you have a Google search tab open in Chrome and when Chrome is the currently active window in the foreground. Thus, the feature doesn’t work when you’re doing something else, but it shouldn’t be much of an issue for people who work and live inside the browser, which is perhaps Google’s primary target anyway.
This Chrome extension is definitely no Motorola Moto X or Open Mic+ Android app. But when you’re stuck with using a computer and need a quick and easy way to start a search, then this Google feature might just do it in a pinch.
Download: Google Voice Search Hotword Chrome extension
The “Ok Google” hotword — the phrase spoken to perform a Google Voice Search — is slowly growing into a pop icon. We’ve watched as its evolved, making its first appearance in Google Glass (albeit under the slightly modified Ok Glass command), to today where it’s made its home on our Nexus 5 homescreens.
Today, “Ok Google” has finally landed on the desktop via Google’s all new extension for the Chrome web browser. Once installed on Chrome, the Google homepage will automatically begin listening for the familiar “Ok Google” command to perform hands-free voice searches. Pretty neat. Oh, and to avoid sucking battery life out of laptops, Google.com will stop listening for the hotword after 5 minutes of inactivity.
To show off Chrome’s all new feature, Google uploaded a new video onto YouTube for easy sharing with friends and family. Help spread the word, and try out the extension for yourself.
Download in the Chrome Web Store: Google Voice Search Hotword (Beta)
Updated Chrome extension supports rich notifications
Yet another Motorola-specific app is making its way from being pre-loaded to now being managed on the Play Store, and this time it's Motorola Connect. Falling in right behind the move of Motorola Assist to Google Play, the latest version of Motorola Connect will be available to update on Motorola's Android 4.4 devices, and have a few new features.
The app, which lets you manage calls and texts in conjunction with a Chrome browser extension, will now work even if you've integrated your SMS into Hangouts and can be updated independent of the OS now that it's in the Play Store. You'll need the latest version of the Motorola Connect Chrome extension as well, which now supports Chrome's rich notifications, to complete the system. The latest Android app can be found at the Play Store link above, and the Chrome extension is downloadable from the source link below.
Chrome Beta for Android has seen another update, this one bringing it to version 32. It fixes a few known issues, and brings to light a few that still need fixing. Like most updates, it’s incremental, but interesting.
To start with, there are two known bugs. The first has to do with scrolling, as the Chrome team lets us know that coloration can occur in the background. Oddly, it notes vertical scrolling, not horizontal. The other bug has to do with the double-tap-to-zoom feature getting stuck at times. That’s a little known gesture allowing us to double-tap the screen, hold on the second tap, then drag to zoom in. This, of course, works just like the pinch-to-zoom, you just don’t need to use both fingers.
The upside is pretty interesting, where we find that adding a shortcut to the home screen is back. That’s a feature in which we can take a mobile website, and add it to the home screen, just like an app. This is really nice for those sites you love that don’t have a native app, or when their app is just plain terrible. Web apps also load faster in some cases, so give it a shot.
The second update is one we’re excited to see, as a new API is out for Chrome. This one is a vibration API, which allows some web apps to make your device vibrate. This could deb useful for gaming, accessibility, you name it. It also adds a depth to mobile web pages not yet seen, so it will be interesting to see what Developers do with it.
If you don’t already have Chrome Beta for Android, go ahead and grab it from the Play Store. It puts you on the cusp of what’s next for Chrome on mobile devices, and can be a lot of fun to try out newer stuff.
- Chrome “Supervised Users” feature arrives as beta channel preview
- Tesla Model S to get Chrome browser and Android emulator
- Chrome beta gets new tab switcher, meant for lower-end KitKat devices
- Google Chrome to block extensions from outside the Web Store
- Chrome for Android update aims to ease online checkouts
Noticeable visual updates and a few under-the-hood changes as well
The Stable channel of Chrome OS has just been bumped to 31.0.1650.61, bringing several user-facing changes. First up is more customization of the Shelf (the status bar and dock at the bottom of the screen), which can now be moved to either the left or right side — It can still be auto-hidden as well.
In the Shelf you'll also notice the app launcher has been pinned to the leftmost spot (or topmost if the Shelf is side-mounted) so that it doesn't move as you add more pinned apps to the Shelf. The launcher icons, app icons and status tray have also been slightly redesigned to be more touch friendly. A nice little visual touch can also be seen in your profile picture for logging in changing to be in sync with your Google+ picture, if you've chosen to have that feature.
This latest release of Chrome OS is available for all Chromebooks out there, except for the original Acer C7, the HP Chromebook 11 and HP Pavilion Chromebook. Your Chrome OS device will pull down the update automatically, or you can always check for the update manually by typing chrome://help in the URL bar.
More: Chrome Releases
If you’re running the Chrome Beta on your Android device, prepare for an update. Chrome v32 is rolling out to the Play Store, and it includes a few improvements and fixes. Being a beta, there are also some known issues to be aware of.
Here’s the good stuff from Chrome 32 for Android:
- Application shortcuts: Ability to add shortcuts to home screen is back
- Vibration API: An API that allows web apps to make devices vibrate
- 285066: Reenabled canvas anti-aliasing
And the not so good:
If you want to try the Chrome Beta, use the link below as it won’t show up in searches.
- Chrome Stable Updated To v28 With Fullscreen On Tablets, Translate Bar, And New Languages
- Chrome For Android Updated, Brings Better Scrolling And Pinch-to-Zoom, Background Audio Playback, More HTML 5 Features, And More
- Google Releases Chrome Beta Channel For Android
- Chrome For Android Beta 30 Has One More Trick Up Its Sleeve: An Easy Double-Tap Zoom Gesture
Android 4.4 may be coming to Developers with some curious strings attached. According to a few reports, Android is free to use, but Chrome now requires licensing. The software ships without Chrome for those who haven’t yet licensed it from Google, leaving them to find their own browser, or create one from near scratch.
Of course, they could simply license Chrome (our preference), but this scenario begs a question about control. Chrome, like any other Google App, requires hardware partners and Developers to license it from Google. The interesting part is that Chrome is now the default browser for Android, so it simply ships with nothing in the way of a web interface. There is an older version of the terrible WebView on the Android Developers site, but that dates back to the Gingerbread days.
The choice to leave Chrome out of Android 4.4 is a curious one, though. It opens the door for other browsers, like Firefox or Opera, to be preloaded. It also opens the door for those browsers to grow their ecosystem by virtue. As users, we can still download Chrome from the Play Store, but be honest: would you even consider a device that didn’t have all the Google stuff preloaded, or had other stuff you couldn’t remove? We probably wouldn’t. If Chrome isn’t on there, it probably means none of the other services are, either.
The move also seems like Google taking a bit more control of Android, leveraging their popular services against compliance. Unlike Android, Chrome isn’t totally open source. Chromium, the source code for Chrome is, but the final build is not. Like Maps or Gmail, Chrome is a Google product, and meant to be licensed. Thinking of Android without Chrome is odd, just as considering Android without Maps is. It’s Google’s world, though — we’re just living in it.
Web technology and the right browser engine bring the land of dwarves and hobbits to life in the latest Chrome Experiment
Tapping and selecting a location from the map brings up another layer, with parallax scrolling, pinch-to-zoom, and great performance on the desktop, mobile and ChromeOS. Again, this is all built with standard web technologies.
Finally, each location offers a sort of mini-game, where user input and swiping (or mouse and keyboard action if you're not on a phone or tablet) allow you to outwit trolls, spring forth greenery at Rivendell, or run away from spirits at Dol Guldar.
This is a serious time-waster, but it also shows what can be done with the right tools and the right browser engine. When you have half an hour or more, you need to check this out from your Android device or any computer with Chrome, Opera or Firefox. Jump past the break for a short trailer.
Source: Google Developers Blog
Google is pushing out another update to one of their highly used and popular apps. The staged rollout has already started and brings the Android Chrome browser app to version 31.0.1650.59. In this update their are a couple of little things that are definitely welcomed, but it is the cloud print support for KitKat devices that is probably a bit more useful to many. The rest of the changes are as follows-
- Printing from Chrome on Android KitKat devices
- Enhanced auto fill for a faster checkout experience on sites supporting request Autocomplete.
- Stability, performance, and security updates
- ‘Add to home screen’ for web apps
- Updated New Tab Page
Or you can get this app and any others you might be missing over at our download site.
Both the stable Chrome for Android and Chrome Beta applications for Android received updates yesterday. The updates aren’t completely major by any means, but the stable version of Chrome did receive some much needed Kit Kat support. Once updated, the mobile browser is compatible with printing right from your device, thanks to Android 4.4′s built-in cloud printing function.
In addition, Google has enhanced the autofill feature in Chrome, which allows mobile shoppers to checkout even faster than before. Google also performed a long list of stability, performance, and security tweaks to make the app run more efficiently.
Chrome for Android:
- Printing from Chrome on Android Kit Kat devices
- Enhanced autofill for a faster checkout experience on sites supporting requestAutocomplete. Try it on betabrand.com/#rac
- Stability, performance, and security updates
As for the Chrome Beta app, the changelog is mostly big fixes and other miscellaneous tweaks to increase performance. Nothing too special to note.
Go grab the updates from Google Play.
There are two types of people in this world: those who like the convenience of autofill, and those who don’t think a browser should double as a PA. For the former group, Google’s updating its mobile Chrome apps today, and autophilics will be pleased to hear the feature is being added to iOS, with form data from other devices synced up for immediate use. Chrome for Android received autofill abilities earlier this year, but today’s update should “further streamline online forms” to save you a little bit more time. Retailers need to adopt this “faster checkout flow” on their end (Betabrand is in from the get-go), but with the holidays coming up, we’re sure several sites will want to make those last-minute purchases as painless as possible. Now, we’re off to order some Catan socks.
A new version of Chrome for Android is rolling out in the Google Play Store. Officially Chrome 31, the latest build gets version number 31.0.1650.59. The update addresses a number of bugs, performance, stability, and security issues, but is most notable for the addition of the ability to print from Chrome (on devices running KitKat) and enhanced autofill for forms.
Simultaneously, Google has launched an update to Chrome Beta for Android. Pegged at version 31.0.11650.60, it addresses instances of the browser crashing as well as removes the ability to to add an application shortcut. A blog post detailing the launch says this functionality will be added back in a later build.
Head over to Google’s blog posts for the official changelogs and more details. Follow the links below to download the latest versions of Chrome to your device.
The Chrome browser for Android has come a long way since it was first launched in the Google Play Store. The browser gets constant support from Google with new features and bug fixes and we have another such update for the browser today. Most notable of the new features is the ability to print webpages right within the browser, if the users have a wireless printer hooked up on their home network.
Printing has made its way to Nexus devices by default through Android 4.4, so it’s no surprise that it has arrived on Chrome as well. The browser now brings better experience for people relying on autocomplete or autofill for purchases and other information. The browser is also capable of storing your credit card details if you’re willing to do so, thus saving you the trouble of manually entering the credentials every time. Google has also fixed some security bugs which were discovered recently. Head over to the Play Store to check for an update if the notification hasn’t popped yet.
Via: Android Community
The post Chrome 31 for Android fixes security bugs and brings improved autofill functionality appeared first on The Droid Guy.
Google has just rolled out a double release of the mobile version of its Chrome web browser. While the latest stable version of Chrome for Android contains a variety of stability and bug fixes, the improved Autofill form feature takes this release’ spotlight.
First and foremost, Chrome for Android, which is now updated to version 31.0.1650.59, is kept up to date with the latest Android version by adding printing support from the browser on Android 4.4 devices. While originally only available on the Nexus 5, Android 4.4 has started to roll out to the more recent Nexus devices. Google has even put up new factory images on its support page.
But the highlight for this release is the improvements to the Autofill system for forms. The Chrome web browser on the desktop is able to store information such as names and addresses that you use in forms, which is then synced to other Chrome browsers. It can even store credit card information, of course, at your discretion and risk. This feature is now snaking its way, slowly and surely, to Chrome for Android as well. This will make things like checking out items from online stores faster and easier, as you have less information to type in using virtual keyboards. At the moment, very few retailers use this on their mobile websites, but Google is working on quickly resolving that.
The latest stable Chrome for Android is now up on Google Play Store. Chrome Beta for Android users may already be enjoying these features, but Google also has a treat for them. There’s nothing major in the new 31.0.1650.60 version of the app, though, but the source code changelog is available for browsing for those interested.
Chrome 31 For Android Moves To Stable Channel, Includes Support for KitKat Printing, Accelerated Checkout, Security Enhancements, And More
Earlier today, a post on the Chrome Releases blog announced Chrome 31 is moving from beta to the stable. The update is coming in with a number of exciting features, including: printing from Chrome on devices with KitKat, support for requestAutocomplete to auto-fill payment details with online stores, ‘Add to home screen’ for web apps, and more.
If you’ve been following along with the beta channel, you’re probably already familiar with a few of these changes.
- Chrome For Android (Stable) Update: Autofill And Password Sync, Standard Performance And Stability Improvements
- Google Chrome Beta 31 For Android Brings ‘Install To Homescreen’ For Web Apps With Support For Full-Screen Mode And Task-Switcher Integration
- [Update: Changelog] Chrome For Android Gets An Update to 0.16.4215.215
- Chrome Beta For Android Now Supports Password Sync And Autofill [Updated]
For those of you rocking the stable (ie not beta) version of the Chrome browser, be aware that an update is headed your way. Chrome 31 has been promoted to the stable track, and it brings forth the ability to print from a device running Android 4.4 KitKat (though it appears that's also in Chrome 30 on the Nexus 4 — but whatever), a better autofill/autocomplete experience, and the requisite stability and security enhancements.
And speaking of security, Google also announced it forked over (another) lump of money to Pinkie Pie after a couple more exploits were uncovered. Gotta love pwn2own.
In an ongoing effort to tighten their control on services, Google has announced that their Chrome browser will no longer support extensions loaded from outside the Web Store. Google says they’ve had complaints lately regarding the security issues brought on by such extensions, with things like browser settings being altered without permission. The new policy will go into effect starting in January.
Currently, this only affect Chrome users on Windows, but could see a wider swathe should Google get further complaints. Saying that the extension were using the existing security mechanism to alter browser settings, among other things, Google Engineering Director Erik Kay also said the changes would affect both Stable and Beta channels of Chrome.
While troublesome, Chrome always has the backup feature of sandboxing to prevent widespread malice. Kay also suggests that any Developer with an extension currently not in the Chrome Web Store submit it for approval, which typically takes no longer than a few days. Once submitted, the extensions can run without incident on browsers, even if loaded before the January cutoff.
This serves as further notice that, when loading apps or extensions from outside sources, it’s wise to be confident in the source. We’d like to think this is strictly a Windows issue, but we also wonder if this is a measure to shore up compliance ahead of the anticipated — dare we say expected — arrival of extensions for the Chrome mobile app.
With Android 4.4, one major, underlying goal is to get the operating system on a variety of devices. Specifically, lower end devices that have languished on older versions of Android. While the initial footprint for KitKat is smaller, and lends itself to that end, there are other Google services to consider.
One of those is Chrome. The go-to browser for Android is getting slimmed down a touch as well, although this one is by choice. In the new Chrome Beta for Android, users can activate a flag that makes tab switching a little more pared down. Rather than fancy animations and previewed tabs, the new method is a simple header of which tabs are open.
It’s a lot like the (very) old method for tab switching, and one that is absolutely necessary for lower-specced devices. This new method is meant for those devices that will get KitKat, and limited memory means something like fancy tab switching is a luxury. It may not be fancy, but it gets the job done, and that’s the goal of Android moving forward: bridging the fragmentation gap, by any means necessary.
Via his Google+ page, Francois Beaufort notes that anyone can try this out by activating the Accessibility Tab Switcher in Chrome Flags. We’re guessing this will be a default feature on lower-end devices, with flagship phones and tablets using the fancier method. A positive step forward for one of Google’s bulkier functions, it will still be a little while before this reaches the stable channel for Chrome.
KitKat's low-memory focus extends to Chrome's latest beta release
Behind all the visual changes and feature additions, Android 4.4 KitKat is all about optimizing the way Android uses memory, including a new API for handling devices with as little as 512MB of RAM. And it seems this focus has extended to Google's Chrome browser too — Googler François Beaufort points out on Google+ that the latest Chrome Beta includes an alternative tab-switcher for low-RAM phones.
Beaufort says the new layout is designed to be simpler and is specifically targeted at "low memory KitKat devices." In the current Chrome 31 beta it can be enabled by navigating to chrome://flags/#accessibility-tab-switcher and flipping the switch manually. The idea, presumably, is that when entry-level KitKat phones begin shipping this new tab-switcher will automatically replace the traditional card-based layout, while leaving the standard interface in place on beefier phones like the Nexus 5.
Source: +François Beaufort
For those of you who don’t know, Android WebView is the feature that opening web content within an application. This feature can be a bit faulty, though. This is why Android 4.4 KitKat brings a huge improvement by powering WebView with Chromium. The new Chromium-based WebView will improve the experience by supporting many of the features you can find on the Chrome browser.
I don’t know about you, but I am glad to see this coming. I have found WebView to be pretty faulty as it is. I often find that pages load much slower in WebView compared to the Chrome browser. If they load at all, that is.
This is one of those improvements that will be much more exciting for developers at first, but users will be able to benefit by the Chromium-based WebView indirectly. After all, that is what it’s all about. We should get current features right and smooth before we focus on the larger, experimental goodies.
The Tesla Model S is already a pretty cool vehicle in an almost sci-fi way, and it’s about to get just a little bit better thanks to some Google integration. Tesla CEO talked about ways to improve the model S, and one thing on the road map was to add a Google Chrome browser to the 17-inch touch-screen interface in the center console of the car. The computer behind it already runs a version of Linux, which Chrome already runs on, so it’s not too much of a jump to see that happening in the next few years. That would be very useful for navigating with Google maps and the like, or just giving the passenger something to do on long road trips.
Aside from Chrome integration, Musk talked about possibly setting up the console to run an emulated version of Android, giving users access to apps in windows on the console. I’m not entirely sure how well everything would work without an internet connection, but assuming they can get the kinks worked out past that, it could be really cool to have different travelling apps running in your car.
If you’re interested, you can check out the full interview with Musk below. The Android discussion starts at about 37 minutes, but the entire piece is very interesting.
source: Android and Me
Come comment on this article: Tesla Model S to run Chrome browser, possible Android emulation in the future