Mobile App Performance (MAP) SDK - Frequently Asked Questions (FAQs)


  • I already use ION to optimize my application traffic. Why do I need Mobile App Performance (MAP) SDK?

    • There are no edge servers between a mobile tower and a smartphone. This is called the mobile last mile where the network is interference-susceptible, low-bandwidth and degrading in nature. MAP SDK improves performance over the mobile last mile by intelligently pre-positioning, pre-caching and optimizing the network conditions to reduce latency between the edge and the device.


  • Where can I get the details on the latest release and features of MAP SDK?

    • You can track our latest release either via Bintray (for Android) or Cocoapod (for iOS). More insights, documentation and developer enablement resources are available at our developer landing page.


  • What is the SDK size ?

    • Please check our integration guides for both Android and iOS to understand the latest sizes.


  • Does the SDK function require push notifications turned on in the mobile app code, or can it function without it?

    • No, it is not mandatory and the SDK can function without it. However, support for silent push notification is available with Firebase Cloud Messaging (FCM) to aid the SDK to conduct policy updates and to preposition content even when the app is in the background. For example turning features on and off or purging content can all be done via silent remote notifications. If push notifications via FCM are off then these changes would simply occur when the app comes to the foreground. Nothing breaks and background notifications are not "required" but are recommended for maximum performance.


  • Why is it necessary to add the Android package name and iOS bundle ID in the SDK policy control interface?

    • For security reasons the Android package name and iOS bundle IDs are required while creating an SDK policy in Akamai Control Center. This is captured for verifying if your app is authorized to use the SDK. For example, if you run the SDK registration code in the app with the license key and if the bundle ID from your iOS app does not match the bundle ID for the SDK policy in Akamai Control Center then our servers will deny the registration. NOTE: If registration is denied, there is no impact to your app traffic, registration denial means the SDK will not apply any of the performance features or record analytics.


  • What are the minimum versions of IOS and Android that our SDK supports?

    • MAP SDK requires iOS 8 or higher. For Android the SDK supports API 15 and above (minSdkVersion). The target/compile SDK should be atleast set to API 28.


  • Does MAP SDK have support for Hybrid apps?

    • Yes, we have support for React Native and Cordova. Read more about it here.


  • How do I generate a license key to initialize MAP SDK?

  • How do I check and confirm if my app integration with MAP SDK is working correctly?

    • Please refer to our troubleshooting guide which explains the process of validating your app build integrated with MAP SDK and reach out to us at incase of any further questions.


  • What is the difference between pre-caching and pre-positioning?

    • Pre-caching works at a domain level by learning what type of objects/responses are most frequently fetched by the app and then pre-caching them at the device to enhance offload. Pre-positioning on the other hand requires you to ingest content into segments and then have the app subscribe to those segments based on user actions to enhance offload at the device based on user behavior/persona. You can read more about pre-positioning here.


  • Will MAP SDK risk overloading device storage?

    • MAP SDK is designed intelligently to have a total cache pool size of 300 MB on the device. The SDK also does not cache any response/object larger than 3 MB to remain sensitive to device storage. We are also sensitive and smart enough to not write data to cache when disk storage or battery is low to avoid any additional stress on the device.


  • Will MAP SDK have an impact on our end users battery usage?

    • MAP SDK is a very lightweight framework and one of the core functions of this solution is to enhance offload at the device and reduce unwanted network calls over the WiFi and Cellular radio. This has a positive influence on battery life instead of bringing any negative impact.


  • What do I do if the SDK has cached something which was not meant to be cached?

    • MAP SDK only caches objects/responses which have a valid TTL and cache control header defined. For some reason if something that was not meant to be cached had a valid cache control header and TTL, then you could use our purge mechanism to clear it from the device. Please read our configuration guide to understand how purge works with MAP SDK.


Contact us

Questions ?

If you have any questions, feel free to drop us a line!

Please contact us through our community page or via if you need assistance in debugging integration/upgrade issues.