Where can I download the nuu:bit SDK?

The SDK can be found here:


How can I signup for nuu:bit?

Self Service Signup:


What is the purpose of the nuu:bit SDK?

The SDK is a simple way to connect a mobile application to nuu:bit's global content acceleration and analytics platform.

The nuu:bit SDK provides 3 main areas of functionality designed to provide the optimal mobile app experience. These areas are:

  1. Mobile analytics designed to provide key backend and network performance  data back to application developers
  2. Network-level optimization backed by nuu:bit global acceleration network designed to speed up the delivery of content through changing mobile network conditions
  3. App-level control of the nuu:bit caching network using Device-Insight(™) to provide an optimized CDN-caching system regardless of location or network conditions.


Is the SDK suitable for any mobile application?

The SDK might be not effective if your mobile application:

  1. Does not use any data back-end/API for send/receive information required for the application to operate
  2. Has a very low-performing data back-end (with response time higher than 300-500 ms for dynamic requests). Such apps can still benefit from nuu:bit edge caching for static objects (like images) and traffic analytics.


How to I use the nuu:bit SDK with my mobile App?

The nuu:bit SDK is provided as a library to be included into the development environment. You only need to initialize the library in your Objective-C or Swift application, and it will transparently accelerate and report the app's data requests without any additional modifications in your app code.

Please see iOS SDK Quick Start Guide for additional information.


For which platforms and OS versions is the SDK available?

Currently the SDK is available for the iOS Operating System (minimal version 8) on the Xcode development platform (starting from 7.x).


What are the expected results of using the SDK?

The SDK’s individual pieces of functionality can be enabled and disabled independently of each other. The nuu:bit CDN caching layer and network-level optimization typically provides gains between 30% and 500% depending on network conditions and content cache ability.


Why the SDK include file mentions only one method? How do I use the SDK?

The provided method is used to initialize the SDK in your application, and the rest of activity (traffic acceleration and reporting) is happening behind the scene without any additional changes in your application.


Does use of the SDK affect other functionality of the App in any way?

No, the SDK does not harm the functionality of the mobile App.  In the off chance there is a problem, the SDK can be disabled by a configuration parameter in the nuu:bit portal.


How do I ensure that I’m using the latest version of the SDK?

An alert indicating that a new version is available will be generated to the provided by you contact email alias in the nuu:bit support portal.


How does nuu:bit achieve acceleration?

The SDK leverages custom patent pending protocols to achieve acceleration. The protocols are UDP-based NMP (nuu:bit Mobile Protocol) or TCP-based DOTS (Dynamically Optimized Transport System). The SDK determines, which protocol provides better performance for that particular App, device and wireless network at that moment in time. Once the appropriate protocol is selected, that protocol then senses network, device and App conditions, and adapts its own behavior in real time to provide the fastest possible transfer of data overall.


Why would I not want to always have my Initial transport protocol set to NMP?

Using NMP first could cause the App to start slower in some network conditions, such as using Wi-Fi in an enterprise environment. NMP is a UDP based protocol and in many enterprise environments UDP could be blocked.   The blockage of UDP packets could slow down the initial connection setup.  NMP will provide faster performance for the App on initialization outside of the UDP blockage corner case.


How does the nuu:bit SDK handle third-party content and requests?

The nuu:bit platform will cache 3rd content based on the contents caching headers.  No object will be cached if for example the object has a “Cache-Control:max-age=0, private” or “Cache-Control:no-cache, no-store” HTTP response header. In these cases that the content is dynamic and is in fact from a third party, it is recommended to use the black list to exclude the interception of that content.  If the content is dynamic and in control of the App developer, it is recommended to leverage nuu:bit’s DSA service and provision the domain in the nuu:bit platform.  


What is the purpose of the white and black lists and how are they used and configured?

By default, the nuu:bit SDK will intercept all traffic and accelerate the traffic to the nuu:bit edge. In cases you do not want traffic to be intercepted, the black list basic access control mechanism will send all content to the nuu:bit edge except the domains listed in the black list JSON array.

The white list will intercept only those domains listed in the white list JSON array. 


What is the purpose of the provisioned domains in the nuu:bit Portal?

When the developer provisions a domain in the nuu:bit portal, the domain now can leverage the full functionality of the nuu:bit platform.   The nuu:bit platform offers a fully functional CDN as well as DSA services.   Please see the the Quick Start Guide. This will also include the full functionality of the Caching rules and APIs.


What protocols do you support with the SDK?

Currently nuu:bit supports any HTTP or HTTPS based protocol requests from the NSURL call in the App. AFNetworking,  NSCache, RestKit as well as anything built on NSURL will all be intercepted. The SDK allows for configuration for what domains and/or sites are intercepted. By default, all requests are intercepted and sent to the nuu:bit edge using DOTS or NMP.

Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk