If you have logged into your Parse Dashboard recently, you will have seen this.
Parse will be shut down on January 28th 2017. If you have developed a mobile app that relies on Parse for backend data storage or push notifications, then you need to take action now to ensure the users of the app do not experience any interruption in service that could lead to bad reviews and unhappy clients. This guide outlines the steps you need to take to migrate from Parse to Kumulos, including:
- Getting Started by signing up for a trial, creating a client and adding an app
- Importing your Parse data objects into the App Build feature of Kumulos and accessing via our APIs and SDKs
- Using Kumulos Push Notifications and configuring your APNS and GCM certificates
- Migrating Cloud Code jobs to Kscript methods
- Social authentication (for example: Facebook)
Signing up for a free trial¶
First things first - you'll need a Kumulos account! Head over to www.kumulos.com and signup for a free trial. Kumulos features are free to use on up to 25 test devices for up to 30 days while you complete your app migration.
Creating a client¶
Kumulos groups your Apps under Clients, usually the name of the company you are building the app for. To add a new client click the primary action button.
Fill in the name of the client. If you are building an app for someone else, you can enable the Client Portal so they can get read-only access to the analytics and reports for their apps. You can also share files and links with them during the migration project. If you choose not to enable it now, you can edit the client enable the client portal for them at a later date. Click "Save" when done.
You will now be redirected to the client dashboard.
Adding an app¶
Now, you can add an app for that client by clicking primary action button. Fill in the name of the App, and optionally, add a brief description and upload an icon. Click "Save" when done.
You will now be redirected to the dashboard for that app.
Migrating your data to Kumulos¶
Enabling App Build¶
The App Build feature in Kumulos provides cloud-based, relational database storage. If you used the Parse Core Backend-as-a-Service, then this is where you will migrate your parse data objects to. Click "Start" on the Build feature.
This will prompt you to choose your preferred data hosting option. Choose "New Managed Database".
Creating tables for Parse classes¶
Your data in Parse was stored in classes. Your data in Kumulos will be stored in tables. You will need to create a table for each Parse class used by your app. Login your Parse Dashboard, select the app you want to migrate and then select "Core". Under the browser you can see all of the classes used by your app. Click on a class to see the columns and their type for that class.
In Kumulos, select "Build" and then "Tables" from the left menu and click on add button on the right to create a table for that class.
Give your table a title, which will automatically be pluralised by Kumulos as a matter of convention. Now, for each column in the Parse class, drag and drop a field of that type from the right hand column into the middle table editor pane as required:
- For String columns, use the Text/String field type
- For Number columns, use a Number field type (e.g. Float or Integer) as appropriate
- For columns that contain Parse Files, use the Data field type
- For Boolean columns, use the Boolean field type
- For Date columns, use the Date/Time field type
Give the field the same name as in Parse, although note that Kumulos will convert field names to
lowerCamelCase for consistency.
When you're happy with the schema you've defined, click the "Save" button. Repeat this for each of your Parse classes. More information on modeling data in Kumulos can be found in our relational data modeling guide.
Importing parse data objects¶
If you have a lot of data object to migrate, our awesome technical support team are standing by to import this for you. First, export the objects for the class you want to migrate. In the Parse Browser, click "Edit" and, ensuring you have no filters applied, select "Export this data".
Click "Export" when prompted to request an export by email.
Save the attachment and repeat this for each class you want to migrate.
Once you have exported all the data objects, contact technical support who will import the data for you. For smaller amounts of data, you can just attach the exports to the email. For larger amounts of data, our technical support team will arrange the transfer.
Accessing your data from your app¶
To access your data you can use the RESTful API from any HTTP client or use the drag-and-drop API editor to create RPC API Methods that you can access by integrating one of our SDKs. While the RESTful API may be more familiar to developers who are used to Parse, which approach you use for your app, will very much depend on when and how you access your data (and personal preference). The following video will give you an overview of each approach.
Accessing your data with the RESTful API¶
To access your data via the RESTful API, you first need to generate an API key. To do this, select "Build" and then "API" from the left menu. Now, click on the "REST" tab.
To add a new API key, click the primary action button on the right, you will then be shown the create API key form. Select the permissions you would like the key to have and click "Create".
You can now use the RESTful API to access your data as shown in the Integration Guide.
Accessing your data with RPC API Methods¶
You can also use the drag-and-drop API editor to create RPC API Methods that support filtering, sorting and joining on related data. Please see the API Methods section of our docs for full details on creating and testing RPC API Methods.
Once created, in order to make your API available to your app, you need to deploy the API methods. This step is important and turns your methods into native server-side code and also native client bindings. When you build your API, all methods you've added or deleted since the last deployment are synchronized so the changes are live.
To deploy your API, select on "Deploy" from the left hand menu. Select each of the client SDKs you want to use in your app and click the "deploy" button.
You can now download the SDK bundle(s) that have been generated from "Download" in the left hand menu.
Please refer to the appropriate integration guide for each platform for details of how to integrate each SDK into your app project.
Submitting your updated app to the store¶
At the end of your 30 day trial, once you have migrated your data to Kumulos and updated your app to use the Kumulos RESTful API or integrated one of our SDKs to call RPC API Methods, you need to add build to your subscription to ensure uninterrupted API service.
On the client or app dashboard, click
Buy next to the 'Build' feature. You will be asked to confirm that you wish to add Build to your subscription.
If this is the first feature you have bought, you will need to create a billing subscription by adding payment card details. Click on the drop-down menu by your login and select "Account Settings" and then "Billing". Enter your payment card details to create a new Kumulos subscription.
Kumulos features are free to use on up to 25 test devices for up to 30 days while your app is in development. After this, you must either switch features off or add features to your subscription to remove these device and time-based limits (and also allow you to create a staging environment for your app).
This should be done prior to store submission (so that your app is not rejected due to exceeding device or time-based usage limits during the approval process).
Using Kumulos push notifications¶
If you used Parse to send Push Notifications to your app, you need to update your app to use the Kumulos Push Notifications instead.
Enabling Push Notifications¶
To start a 30 day free trial, either select Push from the left menu or click the
Start button next to Push on the App Dashboard.
You will now see some more information about the Push Notifications feature.
Enable when prompted. You will be asked to confirm that you wish to begin a 30 day free trial.
Yes, proceed when prompted. Your 30 day trial of push notifications will now begin.
Configuring Push Notifications¶
In order to send push notifications to iOS and/or Android devices you must configure the Apple Push Notification Service (APNS) and/or Google Cloud Messaging (GCM) and upload your push certificate to Kumulos.
CONFIGURE NOW or the cog icon next to the platform you would like to configure. This will open the platform configuration dialog where you can enter the required information to send push notifications to iOS devices via APNS and/or Android devices via GCM.
In order to send push notifications to Android devices with Kumulos, you'll need to set up a GCM project and configure push for your app. These steps are shown in the following video guide.
After configuring Kumulos and GCM, refer to the Android SDK integration guide for instructions for integrating Kumulos into your app project.
In order to send push notifications to iOS devices with Kumulos, you'll need to create certificates in the Apple Developer Member Center. The steps to complete this are shown in the video guide.
Sending Push Notifications¶
Once configured, the dashboard will change to a summary view of trends in your subscribers and notifications history along with a summary of recent notifications that have been sent.
To send a push notification, click the primary action button to display the Compose Push Notification dialog.
Please refer to the Push Notifications section of our docs for more details.
If you use the Kumulos Build feature, then you can send notifications programmatically from your app via Kscripts. Please refer to the API reference for KScript for more details.
In addition, you can send notifications by building an integration with the REST interface of the Kumulos Push API, allowing you complete flexibility when defining the business rules that generate notifications.
Migrating Cloud Code to KScripts¶
KScript is not enabled by default as the majority of use cases can be satisfied via API Methods. If you wish to add server-side jobs, please contact technical support who will be happy to enable KScripts for you.
Once you receive an email confirming that KScript has been enabled for your app, you can then create KScript methods by selecting "Build" and then "API" from the left hane menu. Underneath the "Create API" button, there will now be a "Create Some KScript" button once its enabled on your app.
Writing KScript Methods¶
In Parse Core, click on "Cloud Code" to see your methods.
If your application requires users to authenticate in order to access content, then you can either build your own authentication mechanism in Kumulos or you can use Kumulos to integrate Facebook Login or the Google Identity Platform to support social login for your users.
The following section of the migration guide will show you how you can write a KScript to allow your users to login with their Facebook credentials and then use the Facebook Graph API to retrieve details about them.
This assumes that you have a Facebook developer account and have registered your app.
Click the 'Create Some KScript' button and create a new KScript method called
setFacebookAccessToken to upload the user access token and save this in the KScript session.
K.session.fbAccessToken = K.params.fbAccessToken;
Click the 'Create Some KScript' button and create a new KScript method called
_facebook_ to encapsulate the initialization of the Facebook SDK.
var FB_APP_ID = ''; var FB_APP_SECRET = ''; // Assume session storage of access token set by setFacebookAccessToken K.initFB(FB_APP_ID, FB_APP_SECRET, K.session.fbAccessToken);
include('_facebook_'); var userProfile = K.FB.api('/me'); K.log(userProfile); K.setResponse(userProfile);
A similar process can be implemented to integrate the Google Identity Platform]
A full reference guide to the Facebook Graph API can be found on the Facebook Developer Site. Some methods may require the Facebook User ID. This can be retrieved via the
K.FB.getUser() method (for which further information can be found in the KScript Reference Guide).