How-tos

The fast track for enterprise mobile apps: IBM MobileFirst Platform for iOS

Share this post:

Do you want to take the fast track to building a mobile app for iOS without worrying about IT infrastructure? Now you can because IBM MobileFirst Platform for iOS offers a powerful backend that runs on Bluemix, complete with a set of services that cover common backend needs, including data, push notifications, security, and analytics. To get started right away, use the MobileFirst Services Starter app in the Bluemix catalog.

If you already got familiar with MobileFirst Platform for iOS during the beta period, read on to learn about new pricing and how to transition your apps.

New pricing plans

Pricing plans for the MobileFirst Platform for iOS beta are now expired. The Bluemix catalog is updated with new, general availability pricing.

Pricing plan for Advanced Mobile Access

The MobileFirst Services Starter contains the services listed in the following table.

Service name Beta Plans (Expired) New Plans
Advanced Mobile Access Free Bronze, Gold
Cloudant No SQLDB Shared
Push for iOS 8 Standard Basic

How does this affect my existing apps?

While you can no longer create new service instances from the beta plan, apps that were previously bound to beta service instances will continue to work until April 10th, 2015. To continue using your existing apps without interruption, replace any beta service instances with the new service plans before then.

How do I replace beta service instances in my apps?

There are a few simple steps to replace a beta service instance in your app:

  1. Unbind the beta service from your app.
  2. Create a new service instance that is associated with one of the new plans available.
  3. Bind the new service instance to your app.
  4. Delete the beta service instance from your space.

Updating the SDK

You can download the current version of MobileFirst Platform for iOS SDK and incorporate it in into your existing apps. If you are using the CocoaPods dependency manager to manage your SDK, use the following steps:

  1. Update the existing podfile. (The new podfile includes IMFData.) An example podfile follows:

source 'https://github.com/CocoaPods/Specs.git'

# Copy the following list as is and remove the dependencies you do not need
pod 'IMFCore'
pod 'IMFGoogleAuthentication'
pod 'IMFFacebookAuthentication'
pod 'IMFURLProtocol'
pod 'IMFPush'
pod 'IMFData'

  1. [Optional] Delete the Pods directory and Podfile.lock file from your Xcode project.
  2. Run the pod install command.

Updating iOS client code for Data for iOS 8

In any file where the IMFDataManager API was referenced, add the following import:
#import <IMFData/IMFData.h>

Updating iOS client code for Push for iOS 8

The current working environment setting has been removed from the IMFPush API. To prevent compile errors, remove the following line from your code:

push.environment = IMFPushEnvironmentSandbox

Limitations and known issues

There is a known issue with Cloudant NoSQL where queries for data types that contain non-indexed fields fail. To avoid this issue, ensure that the indexes you create include all fields of all data types.

More stories
May 1, 2019

Two Tutorials: Plan, Create, and Update Deployment Environments with Terraform

Multiple environments are pretty common in a project when building a solution. They support the different phases of the development cycle and the slight differences between the environments, like capacity, networking, credentials, and log verbosity. These two tutorials will show you how to manage the environments with Terraform.

Continue reading

April 29, 2019

Transforming Customer Experiences with AI Services (Part 1)

This is an experience from a recent customer engagement on transcribing customer conversations using IBM Watson AI services.

Continue reading

April 26, 2019

Analyze Logs and Monitor the Health of a Kubernetes Application with LogDNA and Sysdig

This post is an excerpt from a tutorial that shows how the IBM Log Analysis with LogDNA service can be used to configure and access logs of a Kubernetes application that is deployed on IBM Cloud.

Continue reading