ATTENTION: This sample has been deprecated and is no longer supported. Please visit Bluemix Mobile and choose a starter to add Push, Analytics, and Authentication capabilities to download and start coding with a working project.
This helloTodo sample app contains an Objective-C project that communicates with a StrongLoop-based mobile backend that was created with the MobileFirst Services Starter Boilerplate on IBM® Bluemix®.
You can either watch the video tutorial or follow the instructions that take you step-by-step through the process of creating a mobile backend and running the sample.
Before you start, make sure that you have:
- A Bluemix account
- XCode Version 7.1
Use the following steps to configure the helloTodo sample for Objective-C:
- Download the helloTodo sample
- Configure the mobile backend for your helloTodo application
- Configure the front end in the helloTodo sample
- Run the helloTodo sample application
Clone the sample from Github with the following command:
git clone https://github.com/ibm-bluemix-mobile-services/bms-samples-ios-hellotodo
Before you can run the helloTodo application, you must set up a mobile backend for your app on Bluemix.
If you have already created a mobile backend with the MobileFirst Services Starter boilerplate, you might want to skip to the Configuring the front end in the helloTodo sample section.
The following procedure shows you how to create a MobileFirst Services Starter application. Using the boilerplate to create your app automatically performs the following actions:
- Provisions a Node.js runtime and populates it with with a default helloTodo application that was created with StrongLoop. This application uses the LoopBack framework to expose the
/api/ItemsAPI, which is used by both the Web UI and the helloTodo app sample from this Github repository. - Adds the following services to the app: Cloudant® NoSQL DB, IBM Push Notifications, and Mobile Client Access.
- In the Boilerplates section of the Bluemix catalog, click MobileFirst Services Starter.
- Enter a name and host for your mobile backend and click Create.
- Click Finish.
- Get information about your app.
After the provisioning process is complete, you will see a a page for your newly provisioned mobile backend. Click the Mobile Options link in top right part of a screen to find your appRoute and appGUID. Keep this screen open in your browser; you will need these parameters in the next steps.
- Open the appRoute URL that you copied from the Bluemix dashboard in your browser. You will see the web interface for the helloTodo backend.
- Start by following the guided experience steps that are described in the web UI.
Eventually, you will try to DELETE a todo item and will discover that this action can only be complete when using the helloTodo mobile apps sample from this Github repository.The mobile backend is protected by a Mobile Client Access by default. Mobile Client Access is a Bluemix service that provides security and monitoring functionality for mobile backend applications.
Tip: Click the View API Reference button on web UI to see the API specs.
The following steps will guide you through obtaining and running the helloTodo mobile application.
- In a terminal, navigate to the
bms-samples-ios-hellotododirectory where the project was cloned. - Navigate to the
helloTodofolder. - If the CocoaPods client is not installed, run the following command:
sudo gem install cocoapods - If the CocoaPods repository is not configured, run the following command:
pod setup - To download and install the required dependencies, run the following commmand:
pod install - Open the Xcode workspace:
open helloToDo.xcworkspace. From now on, open the xcworkspace file because it contains all the dependencies and configuration. - Open the
helloToDo/AppDelegate.mfile and add the corresponding ApplicationRoute and ApplicationID values (found in the Mobile Options link on the Bluemix Dashboard) in the applicationdidFinishLaunchingWithOptionsmethod:
(BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
//initialize SDK with IBM Bluemix application ID and route
//TODO: Enter a valid ApplicationRoute for initializaWithBackend Route and a valid ApplicationId for backendGUID
IMFClient *imfClient = [IMFClient sharedInstance];
[imfClient initializeWithBackendRoute:@"<APPLICATION_ROUTE>" backendGUID:@"<APPLICATION_ID>"];
return YES;
}In Xcode, click Product > Run.
The helloTodo sample is a single view application with a simple list of to do items. If you previously added data through your web application, you will see the data is automatically pulled into the application.
You can create, add and modify items directly in the application. This sample uses Bluemix Mobile Services SDK, which knows how to handle Mobile Client Access security. Therefore, unlike the web application, you can also DELETE items from mobile app by swiping them. You can also mark items as completed by clicking to the left of the corresponding to do item. When you update an item in the mobile app it will automatically be updated in the web app (you need to refresh the web app). If you make a change in the web UI and want to see it reflected in the mobile app, pull down the todo list to refresh.
As you recall, the DELETE endpoint can only be accessed by mobile applications because it is protected by the Mobile Client Access service.
By default, Mobile Client Access is not configured to require any interactive authentication (for example, to ask for username and password).
The next step is to learn how to configure authentication with the Mobile Client Access dashboard and instrument your app with required components. For more information, see the Mobile Client Access documentation and HelloAuthentication sample.
Note: The project has bitcode support disabled because the Bluemix Mobile Services SDK does not currently support bitcode. For more information, see: Connect Your iOS 9 App to Bluemix
This package contains sample code provided in source code form. The samples are licensed under the under the Apache License, Version 2.0 (the "License"). You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 and may also view the license in the license.txt file within this package. Also see the notices.txt file within this package for additional notices.