What is the benefit of Crossrider?
The Crossrider platform has many ways for you to publish, maintain the extension, and do fine-grained tracking of both downloads and usage. Our platform is also complete with tools for monetisation.
Our platform is in constant development. As new possibilities emerge, or in response to ideas and suggestions from our very active community of users, we perform tweaks, upgrades and incremental improvements.
What programming language do I need to know in order to develop Crossrider extensions?
How much will it cost me to use the Crossrider platform? Actually, it's completely free, unless you plan to use your extension to make money. In that case (or in case that you wish to monetise through another party) please write to us at firstname.lastname@example.org regarding licencing.
Is Crossrider open source? Crossrider is not fully open-source, however we give a free license to open source projects. Contact us.
Where do I begin?
Just visit the sign-up page. Recommendation: Visit the Developer Centre to see a Demo App. Find documentation at Docs. Or watch a video to walk you through the process.
How are Crossrider extensions different from regular browser extensions/add-ons?
There is no appreciable difference for the user, other than the advantage that s/he will not be left high and dry when a new browser version appears. For developers, the main difference is that they will need to create the extension only once. It will work across browsers and automatically update on the appearance of new browser versions.
Does Crossrider include every feature present in native extensions?
The great majority are supported. But if there's a feature you need and find missing, please let us know.
Which browsers are supported?
The following browsers are supported under our framework:
- Internet Explorer 7 and up (32 and 64 bit versions)
- Google Chrome
- Firefox - from 3.6
Upward compatibility with new browser versions is assured.
How does 'Auto Update' work?
This works in either of two ways. In the majority of cases the extension can update automatically without having the user restart the browser. The extension simply checks for updates at regular periods. (If the default interval is not suitable, this can be adjusted.)
In the case that modifications to the extension are more extensive, the browser may need to re-install the extension and sometimes this requires a browser re-start in order for the changes to come effective.
How can I monetise an extension?
This function is built into the platform, and provides you with a number of options. Tell us your needs and we will make the monetisation tools available.
Is the Crossrider platform secure? Crossrider extensions are more secure than ordinary extensions, due to the rigours of our security control. The safety of users is uppermost in our minds. That we are looking after security removes some of the burden from the developer.
Is the auto-update framework secure? For safety's sake, these run over SSL. We check developer updates for harmful code and actively eliminate anything that poses a threat to the user.
How can I use Crossrider's API? The API fields communication between your extension and the web browser. It permits you to save data locally, make GET and POST requests across domains, adds keyboard shortcut functionality if desired, binds events, and more. Full documentation of our API can be found at Docs. The API is one of the most frequently updated components in the Crossrider platform.
How do my users install the extension? The most usual scenario is that end-users will find the extension displayed prominently on your website. We provide a choice of installation widgets that you can add to your site. We can also provide you with a custom installation page on the Crossrider site. A number of other installation methods are available.
Is there integration with Chrome Web store? Yes. Please visit Extension Settings => Export to Chrome WebStore and follow the instructions there.
Do I have to use the online IDE? No, you can also develop on your local computer. Our debug package will assist you, for which, see the 'Debug Mode' section in your extension for step by step instructions. As soon as you have everything set up properly, it should be just as easily to do your extension development offline.
Please explain 'Production' and 'Staging' modes.
Once your extension goes live, any ongoing development work on the extension could negatively impact user experience. Because this is undesirable, we have created an optional (but highly recommended) separate mode for 'staging'. This is where you perform your development work, and where you can see the real-time results of your actions without bothering users. Once you are confident that the extension is working properly again, you simply click a button within staging mode to 'sync with production' and users will instantly see your changes.
How does the extension code work within the browser? A Crossrider extension operates within two 'scopes' of execution. One of these, the Page code, kicks in just after the DOM has loaded and just prior to the loading of additional elements such as images or frames. The other, known as Background Code, runs constantly. It is in charge of everything that happens behind the scenes. For example it can request information at set periods from the server, and transmit this via the API to the Page code, through which data becomes available to the user. See messaging API (requires login) for more details.
If necessary, code can even be run prior to page load by performing an API WebRequest.
Can Crossrider extensions be uninstalled? Users can uninstall Crossrider Extensions just as they would any other extension. The procedure differs according to the browser.
Where can I get help? There is a very active user community forum at:
and you can contact us directly via our contact page