android populer

There's something very annoying about Chrome. It now keeps all the old versions of your extensions and apps. I remember that Chrome used to only keep the current version and the previous version, just like it handles Chrome releases.

If you've installed many extensions and apps, it's likely that the Extensions folder from your Chrome profile uses many hundreds of megabytes. Some apps are pretty big now: for example, the latest version of Polycraft uses 76.6 MB. It's obvious that a single application could use 1 GB after a few updates.

Here's another example: the LastPass extensions. I've checked my profile folder and Chrome keeps 11 versions of this extension since October 2013. Total disk usage: 107 MB, instead of 9.6 MB for the latest version.


Obviously, the old versions are useless and this is a bug. There's a bug report from a Google employee here and it mentions that "the Google+ Photos app is a fairly large app (56MB) which updates frequently (weekly?). It does not appear that older versions get deleted. For the G+ photos app which takes 56MB, I had over 700MB of old versions on my drive."

Until Google fixes this bug, you can manually delete the old versions. Go to your profile folder and open the Extensions folder. Every extension and app has its own folder with a cryptic name (the extension ID), so you can open each one and delete all the subfolders except for the most recent one. For example, LastPass's folder is named hdokiejnpimakedhajhdlcegeplioahd and it has a subfolder for each version. You can sort them by name or by date and keep the most recent version (3.0.22_0).

Chrome will replace the new tab page with a simplified version of the Google homepage. Sure, it doesn't have the search button and the footer, but it's the Google homepage. You'll see the app launcher grid, which replaces the black bar, you'll see the Google+ notification and share buttons, you'll see Google doodles.

Most of the features of the new tab page have been removed and replaced by a huge Google logo. Chrome apps are in the app launcher, recent tabs are in the Chrome menu.

I've never liked browser homepages, but Chrome's new tab page was really useful. It loaded quickly and had a lot of links to pages you were likely to open. Now it only shows 8 of your frequently visited pages and a fake search box that sends you to the omnibox.


When Google shows an animated doodle, the new tab page shows same the animation and you're forced to see it each and every time you open a new tab. Sometimes the doodle uses a lot of resources:


There are some great extensions that replace the new tab page, but you shouldn't have to use an extension for this. The new tab page should be fast, simple and useful.

Here's a quote from Chromium's site:

"The new tab page is the default starting point for all tabs - it is designed to get the user where they want to go, and is not meant to be an information resource like the user's home page; that is, the new tab page is not intended to be a destination, but rather a jumping-off point to other destinations - we strongly want to avoid cognitive load and distractions for the user, especially those creating new tabs for other purposes."

So it shouldn't include distractions. That's exactly what the Google homepage does and the new tab shouldn't do. Animated doodles, Google+ notifications - all of them are distractions that don't belong in a page you open so often.

For now, I'll switch to the empty new tab page.

This post varies with device. It can't be displayed because there are so many devices and each one is different.

This paragraph varies with device. It's just a placeholder for a paragraph that should have revealed a lot of useful information. Unfortunately there are so many devices and they have different characteristics, so it's hard to write a paragraph that encompasses their complexity.

This screenshot varies with device. It should show some important information about the Google+ app for Android, but it doesn't because there are multiple Google+ APKs and each one is different.


On a more serious note, there are many Google Play apps that show the uninformative "varies with device". The size of the app varies with device, the current version varies with device and so is the required Android version. That's because Google Play allows developers to upload multiple APKs for the same app:

Multiple APK support is a feature on Google Play that allows you to publish different APKs for your application that are each targeted to different device configurations. Each APK is a complete and independent version of your application, but they share the same application listing on Google Play and must share the same package name and be signed with the same release key. Android applications usually run on most compatible devices with a single APK, by supplying alternative resources for different configurations (for example, different layouts for different screen sizes) and the Android system selects the appropriate resources for the device at runtime. In a few cases, however, a single APK is unable to support all device configurations, because alternative resources make the APK file too big (greater than 50MB) or other technical challenges prevent a single APK from working on all devices.

Even though Google doesn't encourage developers to use this feature, most Google apps use it: Google+, Google Chrome, Gmail, Google Maps, Google Search, Google Play Books, Google Play Movies & TV, Google Translate.

Since Google knows which devices are associated with your Google account, it could show a drop-down that lets you select one of your devices and show the appropriate information. For example, you have a Nexus 7 running Android 4.3 and a Galaxy S3 running Android 4.1. Select one of the devices and replace "varies with device" with something more useful.

AppBrain manages to show some useful information:

I don't know about you, but I like to write the title of the post at the end. It makes sense to pick a title only after writing an article because the title usually summarizes the text. Sometimes I have no idea what's the right title, but it reveals itself after writing the last paragraph.

This post is not about finding the right title for a blog post, it's about a new Blogger feature (or a bug?) that shows this message as soon as you start writing a post: "Required field must not be blank". The warning is placed below the title field, but it's not obvious that it refers to the title. Click "ignore warning" and the warning is displayed again in a few seconds.

You can't save, preview or publish post if you haven't picked a title. This is really dangerous: what happens if you write a long post and the browser crashes? Until now, Blogger automatically saved the post as a draft and you could find it later. Now it's no longer saved until you write a title.


You could write a temporary title and change it later, but why use a workaround? The title should not be a required field. Blogger could show a warning before publishing the post and that should be enough. It's important to mention that Blogger has never required post titles before. You could even publish posts without a title.

To sum up: here's a feature that's annoying, not useful, dangerous and hard to understand. It's really difficult to come up with something like this, but someone did.


What if Gmail had a similar feature?


Update (July 8th): The feature has been removed (or the bug has been fixed).

{ Thanks, Beben. }

It's sometimes helpful to read some instructions, especially when you use advanced features. What happens when you can't dismiss these instructions and you have to see them every time you use a service?

Google Trends shows an annoying box every time you click the search box: "Explore Trends. Separate terms by commas to compare. Some examples: [GMC, BMW, Honda], [Swine Flu], [Madonna, Adele]."


Google Trends used to display this information on the homepage, but now the homepage shows a list of hot searches.


Here's the old Google Trends homepage: