In this article I will show you how to connect your desktop and mobile applications to a mobile backend as a service (mBaaS) with Delphi 10.1 Berlin. I normally use Parse.com as a backend but as they announce that they will close their mBaaS service I will use Kinvey instead.
If you are interested in Parse.com you can read my previous articles about creating your own self-hosted Parse server and deploying a Parse server to Heroku which achieves similar result to what I want to explain you today (basically having your data hosted anywhere in the cloud either using Kinvey as an mBaaS or Parse + Heroku as a PaaS).
There are plenty of articles online about these topics and I just want to give you my input and how I dealt with some of the challenges I faced during development.
Join Kinvey and create your App environment
First step is to join Kinvey and create your application environment. Kinvey offers a Free plan for developers that it is ideal to test your applications. It includes the core mBaaS features and 1GB of data storage. Once you move your solution into production you can switch over one of the other plans available.
Once you are in the console management, press "New App" and enter the name of your backend:
Now you should see your enviromnent created:
Click on the Development label and the dashboard will be shown:
At this moment in time, you should know what data you are going to store. In this example I have created a simple collection that includes several fields for a sample application that I'm building and that the source code can be found here:
Here is my collection of values:
*Note that if you POST data to a non-existing collection, this will be created automatically.
Now it's time to start using the collection and querying/adding data via Http REST. For this task you will have to identify the required headers that are needed for your GET/POST requests. You can see one example here for Parse.
Kinvey follows a different approach than Parse in terms of security. Kinvey offers basic and session authentiation. Basic authentication uses the HTTP header "Authorization" with the components "Basic" and Base64Encode(AppId:MasterSecret). Session authentication sends a login request to collct an auth token from Kinvey backend and then this token is used in subsequent REST requests.
I will focus on Basic authentication as Session authentication is as simple but with more steps.
The first example is by using REST via IdHttp so you can see how GET/POST are handled manually and the second example is just by using the Kinvey provider component available with our Delphi 10.1 Berlin that will make our life easier.
Here it's my Win64 example that uses Kinvey BaaS:
Add action, adds data into the collection and reload just brings the data back from the cloud and displays it in a listview component.
Here is the code behind it:
As you can see, each method uses a POST/GET command to baas.kinvey url with some arguments, headers and options. I find this way really useful as you can clearly see what's going on and easily map what you could do via curl:
If you want to run this example successfully you'll need to include libeay32.dll and ssleay32.dll from OpenSSL.
You can test this app and its mobile companion app using the source code here.
Using Kinvey Provider component
Delphi 10.1 Berlin has a KinveyProvider component that we can use directly without having to worry about the request details. You'll see below that to do the same as the code sample above we will need just few lines of code:
Then connect the BackEndStorage component to the KinveyProvider component.
Now, here is the code to Add items to the collection and to load the collection via components:
As you can see now it's way simpler.
And here my android app up and running:
Win64 app and an Android app that share the same back end using Kinvey BaaS.
And the data in Kinvey:
Although this article it's quite long I'm sure you will find it quite interesting if you still haven't played with these components and the cloud.
Note that this BackEnd service will cease to exist shortly (as the appkey is hardcoded in the android app and the source code is available).
Do not hesitate to contact me if you have any questions.