Announcing Browserling: Interactive cross-browser testing in your browser

- Bigger browser window

- More responsive UI. It shows a message saying a plugin was not run (flash) but it took forever to be able to click the X on the message to hide it and it locked up the browser (not my browser but the browser in the browser.)

- There was a lot of waiting in the queue and it suggested paid plan... but no paid plan available.

- I was able to access other parts of the machine, including the printing and devices section (usually visible when you right click the computer icon and click properties. You might want to lock down the machine a bit more.

I'm guessing you're aware of most of these.

The only other thing I'll say is that how are you dealing with the Windows licensing? You probably don't want to ignore dealing with that if you haven't yet as it could be painful in the future.

Overall, very interesting technology. Kudos!

Unforutantely it looks as though Microsoft was none-too-pleased with their inclusion of Internet Explorer as one of the virtualized browsers and has forced them to shut it down. Hopefully you can elude the same fate...

Also, while I'm typically ok with the cartoonish trend of most startups these days, I'd have to say browserling might have gone a bit overboard with the whole thing. I know your only in beta and I'd have to assume things will change as you continue to develop.

Best of luck to you guys!

The toolbar is prefixed "http:// -- is there support for https? If not, is that on the roadmap?

You may not want to answer this, but how will this service scale? Booting an individual VM for each user seems incredibly resource intensive.

(disclaimer: I interned on BrowserLab)

I entered the URL for a site I'm building, wanting to see if IE9 was going to screw me up (I'm still on WinXP), and I was sent to a queue.

My only real complaint about the queue is that you give absolutely no indication of how long the expected wait time will be. This would be reasonable, except for the countdown clock, which simply read 00:00 the whole time I was waiting.

When I got out of the queue, the countdown clock set itself to 01:30 (quick question: why the leading zero on the minute portion if it's only going to be a single digit value? Is it aesthetics? I actually liked it but I was just wondering...). Unfortunately, for the first 10-15 seconds or so, I was just faced with a blank screen, save for the border around what I assume should be my browserling. After waiting for these 10-15 seconds, I was told that my time was up. The countdown was still running down while this message was shown.

Going back to the queue, I'm assuming that the 1:30 I saw counting down on the other page is a standard time limit for a free user, so why can't you give me a reasonable estimate based on something like (users-in-queue * 90seconds) / number-of-available-machines-or-vms-or-whatever?

http://i53.tinypic.com/6z3qyp.jpg

Otherwise, developers can do everything that Browserling does and more with a combination of Virtual Machines, Multiple IEs, and Internet Explorer Collection, etc. Having developer tools is the key.

I think that the queue is an interesting concept. I understand that you have to tier your system, but it made me bounce, and not want to go back. If you keep it, find a way to make it clear and seamless.

I'm using Chrome, as requested.

Now i goto grok the stack vm code. ;-)

There appears to be several issues to work out. I've not been able to get a page rendered. I get "Nexus is down. Try again shortly." "No API for group null" and "You are not signed in!" when I am signed in.

Its a neat idea though!

Good idea though - if you can get the pricing model to a point where it's appealing to my infrequent but bursty usage (and you make it reliable), I'd definitely be interested.