RockMelt browser – initial thoughts

I’m not sure where I heard of the RockMelt browser (almost certainly on Twitter), but I signed up for early access and, today, got around to grabbing the ZIP file and installing it (Mac version).

I’m not going to repeat all the features here, which are readily viewable in their blog post.

So far I’ve found it to be fast and bug free, which is good. Here’s a quick list of (very personal) pros and cons so far:


  • Personalised, cloud-based browser – history is universal and accessible from any RockMelt browser I log into. (Not tried this yet, though.)
  • ‘Click-through’ search results – use keyboard to traverse the search results in a side bar whilst the main page changes to show the result you are on.
  • Facebook & twitter share in-browser.


  • It uses it’s own “” URL shortener. I want to use my own, please. (If you want to know why, see my post earlier this year.)
  • The help page shows a number of twitter accounts in the right-hand side panel, but I can’t see how to add more than one. Probably me, but I’ve already spent too long searching. (Sorry, can’t link you to their help, as it’s built into the browser.)
  • And whilst we’re on the subject, what about twitter searches / lists?
  • It’s build on the Chrome browser. It is, indeed, fast, but I really don’t like the UI.

There’s more experimentation to be done: obviously it doesn’t replace other Social Media desktop applications, like TweetDeck and Seismic, and I don’t think it’s built to compete with them; nor is it a simple ‘share this website’-based browser – it’s got more functionality and complexity. Rather, it’s somewhere in between the two, and I personally think that this is to its disadvantage.

Thanks for reading this far,

Please note: I reserve the right to delete comments that are offensive or off-topic.

2 thoughts on “RockMelt browser – initial thoughts

  1. Agreed with you Ady on the UI – it was the one thing that turned me off the other social media browser, Flock.
    But the customisation and speed of the browser certainly mean you give it some serious consideration.
    From my part, I already have embedded tools (that I quite enjoy and don’t want to change) so the idea that I will need to convert all of my activity to a new browser doesn’t massively appeal to me!

    • Thanks for your reply, Donald.

      I missed out mentioning about the required change to working practices, that you pointed out. There do seem to be a lot of people out there trying to get us to use their framework – which is great, competition-wise, but the amount of time and effort required to move to the new environment is very off putting. Not that I’m averse to change – I’ll give something a fair shot and if it’s too much work, I’ll stick with what I’ve got. Market competition means that features in one product eventually make their way into the others. At least the relevant, useful ones do.


Comments are closed.