What are some drawbacks to using CrossRider as platform for developing extensions for multiple browsers?

Question

I've read a lot of positive insights in using CrossRider compared to its competitors but I haven't read anything related to any of its limitations (functions, speed, integration with third party services, etc.).

Answer 1

The biggest drawback of using any framework is the fact that you are bound to the limitation of that framework.

However, if you see that what you are looking to achieve is feasible using the framework (and most likely Crossrider will fit your needs) then you will find out that it is going to save you a tremendous amount of time and effort, in comparison of doing all the hard work yourself.

I would suggest that you will check their cross-browser development framework and see what can be done and can't be done. And if what you are looking for can be done - obviously go for it. Instead of learning the Firefox and Chrome APIs along with C++ for IE development, you only need to be familiar with Javascript (and jQuery).

Crossrider has an online IDE which lets you dive right into the code in matter of seconds. No need to download any development SDKs (unless you really want to), and you will see your code changes take affect in real-time.

Other benefits that are worth mentioning are their publishing tools, such as direct download links, the widget generator and the dynamic Window installer that can install your extension on all browsers automatically.

(disclosure: I am one of the employees of Crossrider)

Answer 2

A few drawbacks that I found:

In my case, the extension is not the main part of your application (I have a desktop solution that downloads and converts Flash videos to other formats, and CrossRider is used just to add Download links in pages that contain Flash videos). Let's call my application FVD (Flash Video Downloader).

Drawbacks:

1. FVD and the CrossRider code are installed as 2 separate entries in "Add Remove Programs", which is confusing to users (ideally it should be only 1 entry, FVD in my case, or at least have a way of hiding the CrossRider entry)
2. FVD can be configured (for example users don't want to have links shown on sites A and B), but passing the configuration to the CrossRider extension is not easy/straightforward (since you have only one extension for all users, you can't pass an argument to customize it based on each user's choices). You could use sockets (for example making a request from the extension to localhost:8181, and have a socket listen on port 8181 from your main application), but that just seems hackish and prone to errors.