Occasionally, and less often recently, the browser plug in will crash. In fact, it happened today when an employee had two Blue Jeans tabs open at the same time.
We have not tried Safari or Firefox yet.
Blue Jeans isn't intended to be used more than one at a time on a particular machine. So, the earlier comment about having "two Blue Jeans tabs open at the same time" is a bit of unintentional mis-use. Some devices like cameras and microphones can often only be used by one application at a time so it wouldn't work to try to join two different meetings at the same time. If you managed to join the same meeting twice it could result in echo. Also, the browser plug-in makes assumptions about CPU availability based on only one instance running. Blue Jeans provides browser service for any of the most popular browsers, so you should use whatever browser you prefer... Firefox, Chrome, Safari (on Mac), & IE (on Windows). Blue Jeans is intended to be used on a "native" browser on the local PC... So doing something like MS-IE running on "Parallels" on a Mac is not guaranteed to work well.
I've found only one quirk with Chrome 32.x and OSX 10.9.x.
I can't change the calendar on which to receive an invite because of a screen display issue. I'll submit details separately.
I use Chrome almost exclusively because I can easily switch (command-tilde on OSX) between my Google Apps and Gmail accounts. I've got each account color coded icon in the upper-right and use the same color for my mail background, so I always know if I'm in my personal or work window.
Personally, I switch between different browsers without giving it too much thought. We did have some trouble with video when Chrome 32.0 first came out and had to push out a quick update to remedy that. Google seems to like to do frequent & automatic Chrome updates, and is making changes intended for "other platforms" (like Chromebox) that can sometimes cause changes in behavior that we must accommodate. From that standpoint, Safari, IE, and Firefox are a bit more "stable" than Chrome, but Chrome is evolving more rapidly than the others.
Hi Ben -
We are happy to look into the specific issue with Firefox. Please upload your logs on Firefox at bluejeans.com/loguploader. We will open up a support case now as well to have a support engineer look at the issue (with your logs). We will post the resolution back to this thread. Thanks for your patience.
Also - if you want to follow progress on Google x64 please follow this thread here