There are a lot of ways to get text from your computer to your Android device, but perhaps none of them are quite so simple as the new Belt.io app and service. Simply install the app on your phone and you can send text and links from the web service after signing up. Naturally Belt.io also offers browser extensions for Chrome and Firefox, so you don't even have to go to the website to use the service.
Did you know that the web browser on your phone or tablet waits three tenths of a second after you tap something to actually perform that action? You did if you're a web developer - it's a de-facto standard for mobile browsers, a built-in delay for the double-tap zoom function. But if you're on the newest Chrome beta, you won't see the delay, at least on mobile sites.
Why is this?
Google has provided the tools for developers to create desktop Chrome apps for a while now, but it's looking like Chrome apps are going to be hitting mobile devices too. A GitHub repository managed by a Googler contains tools and documentation for the project. Google isn't really keeping it a secret, but neither is it discussing any official details.
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.
If you're a Chrome Beta user who was getting bored with their weekend web browsing, we've got a tip for you - Chrome Beta for Android has an experimental "Accessibility Tab Switcher" flag that'll allow you to switch tabs in a compact, pleasing interface, also enabling you to bring back closed tabs with a handy "undo" button. That should take a little pressure out of your tab management experience.
To turn the Accessibility Tab Switcher on, just open up Chrome Beta and head to chrome://flags.
PushBullet has made a name for itself by making it painless to move files from your computer onto your phone. Now the app is taking a bold step towards making it just as easy to move data in the opposite direction. The latest update to version 11.3 introduces push-to-Chrome, a promised feature that should make it possible to get links, notes, pictures, and other content onto any computer running Chrome. The update also introduces the ability to push lists for the first time, and when you create a new push using the app, you can now select what you want to push directly.
A few weeks back we pointed out a neat little trick in the Chrome Beta for Android. By toggling the NTP flag, you could get a spiffy new tab page with a search box and scrollable list of recent sites. The last update to the app seems to have killed it, but now we know why – Chrome 31 will make that UI the default in Android.
Starting with the upcoming version 31, Chrome for Android Beta will support adding web apps to the home screen via an option in the overflow menu. These apps will still run in a sandboxed Chrome environment, but they will also be integrated with the operating system in a few interesting ways.
Adding a supported web app to the homescreen will place a custom icon on the device, but this is more than a bookmark shortcut.
A beta release is, by definition, and unfinished product. They're not always perfect - that's kind of the point. So it is with the latest beta version of Chrome for Android: many users are reporting that the latest build available on the Play Store is unexpectedly and repeatedly causing their devices to reboot. Users on the official Chrome blog and the Chromium code hub are citing the problem on the Nexus 7 and Nexus 4.