Google, please fix Chrome for Android

Back when I reviewed the Nexus 7, I mentioned that I was disappointed with Chrome for Android. It often felt slow, would hang, and typing in the address bar and input fields on webpages would lag. Scrolling wasn’t always optimal, and sometimes, it would simply freeze up altogether. We’re several months down the line now – has the situation improved for me?

This is what I wrote about Chrome on the Nexus 7:

Force closes I haven’t seen yet, but during page loading, the browser still often becomes unresponsive, and the loading itself will often take longer than it should – especially considering the quad-core processor and 120Mbit/s connection I’m on. This is not just the case with notoriously slow and sluggish sites like The Verge, but also prim ‘n’ proper sites like OSNews or Daring Fireball.

Furthermore, typing in the address bar is an exercise in frustration, as it will often take seconds for the device to catch up with your typing (it seems searching through bookmarks, history, and relevant Google search queries slows everything down). The close tab button is also far too small, and will often not register your touch – or it will register, but only a few seconds later. This kind of touch delay is only found in Chrome, and nowhere else. It’s puzzling.

I then expressed hope the situation would improve with updates, but, and let’s just get it out of the way, it hasn’t. Chrome on the Nexus 7 is still laggy, websites make it unresponsive, loading is slow, typing in the address bar is an exercise in frustration due to input lag, and the interface is still very touch-hostile – small targets – and whoever came up with the idea to put the small close tab button right next to the small new tab button ought to be fired on the spot.

I was already unhappy about this when I got my Nexus 7, but now that we’re months ahead, and several Chrome updates and one Android update later, there’s simply no excuse. Google needs to get its – yes, I’m saying it – shit together and fix this mess of a mobile browser. The entire Android experience on the Nexus 7 is pretty awesome and has few issues, but Chrome ruins everything. The browser is a crucial aspect of a tablet for me, so this seriously diminishes the Nexus 7’s user experience for me.

On my Galaxy SII, it’s even worse. All the same issues – but all of them way worse, and to boot, the odd force close or complete Chrome crash. However, my SII runs alpha code – CyanogenMod 10 nightlies – so I can’t blame Google blindly for that one. However, I am actually assuming this is all Google’s fault too, since the rest of CM10 is pretty damn good.

Yesterday, I finally had enough. My SII has made the full switch to the Firefox beta, and while I dislike Firefox’ horrid interface and miss the tab synchronisation with my iMac and ZenBook, the browsing experience is just so much better. Faster, smoother, more stable. My Nexus 7 will remain on Chrome for a while (tab synchronisation is more important for me on a tablet than on my smartphone), but if everything on my SII goes smoothly with Firefox, the N7 will follow in its footsteps.

If the issues with Chrome persist beyond the coming months, I will look into dumping Chrome for my iMac and ZenBook as well. I like the cross-device integration in modern browsers, and as much as I like desktop Chrome, I will dump it in a heartbeat if Google continues to refuse to fix mobile Chrome.

Google, please fix Chrome for Android. It’s a massive blemish on an otherwise great mobile operating system. I happened to play with an iPhone 4 yesterday, and was instantly reminded of what a good mobile browser is like. Take notes, Google. Apple is eating your lunch there.


  1. 2012-11-07 5:20 pm
  2. 2012-11-07 5:25 pm
  3. 2012-11-07 5:35 pm
    • 2012-11-07 5:37 pm
      • 2012-11-07 5:51 pm
        • 2012-11-07 6:03 pm
          • 2012-11-07 7:11 pm
          • 2012-11-08 12:58 am
        • 2012-11-07 8:04 pm
          • 2012-11-08 1:04 pm
          • 2012-11-08 6:05 pm
        • 2012-11-07 8:35 pm
          • 2012-11-08 3:31 am
    • 2012-11-07 6:21 pm
  4. 2012-11-07 6:07 pm
  5. 2012-11-07 6:18 pm
    • 2012-11-07 8:07 pm
    • 2012-11-08 2:40 pm
  6. 2012-11-07 6:20 pm
  7. 2012-11-07 6:22 pm
  8. 2012-11-07 6:25 pm
  9. 2012-11-07 7:03 pm
  10. 2012-11-07 7:10 pm
  11. 2012-11-07 7:30 pm
  12. 2012-11-07 7:39 pm
  13. 2012-11-07 7:54 pm
  14. 2012-11-07 8:12 pm
  15. 2012-11-07 9:42 pm
    • 2012-11-08 6:09 am
  16. 2012-11-07 10:00 pm
  17. 2012-11-07 10:05 pm
  18. 2012-11-07 10:37 pm
  19. 2012-11-07 10:45 pm
  20. 2012-11-07 11:35 pm
  21. 2012-11-08 6:15 am
    • 2012-11-08 7:40 am
      • 2012-11-08 1:36 pm
    • 2012-11-09 8:47 pm
  22. 2012-11-08 11:47 am
  23. 2012-11-08 2:48 pm
  24. 2012-11-08 3:06 pm
  25. 2012-11-08 3:34 pm
  26. 2012-11-08 4:10 pm
  27. 2012-11-08 4:20 pm
  28. 2012-11-08 5:27 pm
  29. 2012-11-09 8:29 am
    • 2012-11-09 5:09 pm
      • 2012-11-09 7:15 pm
        • 2012-11-11 11:05 am
  30. 2012-11-10 4:51 pm
  31. 2012-11-12 10:40 am