A Javascript library for developing modules for COBI.Bike – the perfect fusion of smartphone and bike.
Switch branches/tags
Nothing to show
Clone or download
Latest commit ba435f9 Sep 6, 2018


COBI.Bike DevKit

A collection of Open Source components to develop modules for COBI.Bike – the perfect fusion of smartphone and bike.

COBI.Bike DevKit

💡 Interactive Demo: Learn the fundamentals

The quickest way to learn the DevKit basics without writing any code.

Open demo button

Change location coordinates and hit thumb controller buttons to see COBI.js in action. This simulates data and interaction events that will later be provided by the COBI.Bike system when riding a bike. Bonus points for directly tweaking the code e.g. subscribing to additional data from the COBI.js data stream.

🚀 Let's get started with your first project

It only takes a few lines of javascript to turn Web Apps into a module:

Step 1: Add boilerplate code

To get your Web App ready just add COBI.js at the end of the body section of your HTML:

<script src="https://cdn.cobi.bike/cobi.js/0.44.0/cobi.js"></script>

and pass an authentication token to the COBI.init function before subscribing to the data stream. Tokens are not issued yet, so you can use any string for now:

// Authenticate your module
COBI.init('token — can be anything right now')

It's that easy: Any Web App + COBI.js = Module!

Step 2: Hook into the data stream

Enough with the boilerplate code, let's make our new module respond to the handlebar remote control:

COBI.hub.externalInterfaceAction.subscribe(function(action) {
  console.log('I just tapped the handlebar remote and instantly received this ' + action + ' in my Web App');

or visualize the cadence acquired by COBI.Bike app from an external Bluetooth sensor or e-bike motor:

COBI.rideService.cadence.subscribe(function(cadence) {
    console.log('Your current cadence is ' + cadence + ' rpm.');

There is a ton of data available such as current speed, course, heart-rate (if heart-rate monitor is connected), power, calories burned and much more. Our COBI.js reference will be your friend.

🔬 Test your module

Now that you have supercharged your Web App, you can test your module either in the Chrome browser on your machine or directly in the COBI.Bike iOS App on your bike.

Browser testing

Just install the DevKit Simulator Chrome Extension, open up the Developer Tools (⌘ + Option + i / Ctrl + Shift + j) and select the »COBI.Bike« tab.
To get the best experience, switch on the phone mode in the upper left corner and rotate the device to landscape. To simulate riding and fitness data you can play back one of our sample cobitrack or GPX files.

On-bike testing

If you don't own a COBI.Bike yet, apply for a hardware development kit at cobi.bike/devkit or purchase one at get.cobi.bike. Afterwards, register as a developer to test your module on your bike.

Become a developer button

Ready? Then open up the COBI.Bike app on your iPhone and open the edit modules screen. As developer you can now choose from a number of examples modules or add you own via »My Module«

When you open »My Module« on the home screen or the dashboard, you can enter the URL of your module (it can be hosted wherever you want, but we have some suggestions below). When you press »Open module« your module is loaded and hooked up to the app. Now you can easily test your idea on your 🚲.

COBI.Bike iOS App Home COBI.Bike iOS App Edit Modules COBI.Bike iOS App My Module

🏓 Play ping-pong with the COBI.Bike app

Take advantage of interfaces to the native COBI.Bike app to save yourself a lot of work.

Start a turn-by-turn navigation to a destination:

  'action': 'START', 
  'destination': {'latitude': 50.110924,'longitude': 8.682127}

Open a phone number picker with the list of contacts:

COBI.app.contact.read(function(contact) {

Hook into the voice feedback system:

COBI.app.textToSpeech.write({'content' : 'Can you hear my voice?', 'language' : 'en-US'});

Claim the entire screen space by hiding the clock in the top right corner:


Claim all Thumb Controller buttons on e-bikes that are reserved for motor control by default:


Check out the COBI.js reference for more.

🎛 Settings for your Module

A module can be shown in different contexts. There are three pieces of information that you should adapt to:

  1. The device orientation — your module should automatically adapt to the available screen size
  2. The value of COBI.parameters.context() — can be one of
  • COBI.context.onRide
  • COBI.context.offRide
  • COBI.context.onRideSettings
  • COBI.context.offRideSettings
  1. The value of COBI.app.touchInteractionEnabled — changes when you start/stop riding

Flexible layout

Take a look at our COBI.Bike DevKit UI Components for an easy way to create a UI for your settings.

Module context

There are 4 contexts you should support. You can check COBI.parameters.context() at any time to decide if some sort of settings should be shown (COBI.context.onRideSettings or COBI.context.offRideSettings) or if the actual module is requested (COBI.context.onRide or COBI.context.offRide). To share information between the two contexts and in between user sessions use the web standard Local Storage.

Touch Interaction Changes

While riding, the user is encouraged to use the thumb controller instead of interacting with the UI via touch. Subscribe to changes of this value to make the best out of both situations. Please note that a bar is shown at the top while touchInteractionEnabled is false — make sure it is not overlapping with your UI.

COBI.app.touchInteractionEnabled.subscribe(function(enabled) {
    // Adapt your UI

Module Contexts

🌈 Everything else about the DevKit

Debugging Tips & Tricks

  • For seing javascript errors in the native App, activate the "Show module errors" option in the "Diagnostics" section
  • To get better error messages when interacting with the COBI.js API, include https://cdn.cobi.bike/cobi.js/0.44.0/cobi.dev.js instead of the script mentioned above (please note: the dev version is considerably larger which has a big impact on the loading time)
  • To show a native dialog when running inside the iOS App, just use a normal alert("your messages") (only for debugging)
  • When developing in Chrome, use the phone button in the upper left corner of the Chrome Developer Tools and rotate it to landscape to see how it looks while riding
  • When using the Chrome Simulator, press the Print state to console button to print the current COBI.js state to the Chrome Developer Tools Console
  • To change the current context append ?context=onRide or your desired context to your URL in the browser.

Inspiration & Examples

Interface Guidelines

Read our Interface Guidelines to understand the unique challenges of developing software for bikes and to learn more about how the COBI.Bike system and modules work.

More DevKit Resources

Other Tools & Resources

  • Glitch – friendly community where you'll build the app of your dreams
  • CodePen – social development environment for front-end designers and developers

👏 Contributing to this project

Anyone and everyone is welcome to contribute to this project, the DevKit Simulator and the COBI.Bike DevKit UI Components. Please take a moment to review the guidelines for contributing.

Copyright © 2018 COBI.Bike GmbH