The Backendless Platform is built to run anywhere. We have had that vision right from the very first release of the product. Many of you are familiar with Backendless that we host in the cloud; however, the exact same technology stack is also available as an on-premises solution which we call Backendless Pro. Backendless Pro…
This is Part 2 of a series of articles where we build a mobile app without any coding. The app we are working on is a ToDo app. In the previous post, we did the following: Set up a Backendless (backend) account. Set up a Dropsource (frontend) account. Implemented (without any coding of course) an application…
In one of our previous articles, we showed how to develop a custom Alexa skill using an example of a Trip Planner app (How To Build A Dialogue Custom Alexa Skill Using JavaScript (Without Lambda). In this article, we will show you a more complex example of the interaction between Alexa and the user. Today,…
Did you know you can use the Backendless Code Generator, which is a part of Backendless Console, to easily generate a simple real-time chat application for iOS, Android and JavaScript? You get full source code and can see how to use Backendless APIs for sending text-based chat messages in real time. In this article, we will describe…
If you’ve used the Data Retrieval API in Backendless Cloud, you may know that the server limits the number of objects retrieved from a table to 100 in a single call. For Managed Backendless and for Backendless Pro, this limit is configurable. In order to retrieve more than 100 objects, data paging is required. Paging greatly…
Development of mobile applications generally requires two parts: the Backend and the Frontend. Of course, you could limit it only to the client-side, but if there is some data that need to be stored on the server, there is no way to get around having a backend. In this series of articles, you will create…
In this article, we will describe how to use the Backendless API to save multiple related records with one primary (parent) record in a table. All related records (children) will be stored in separate tables as a part of the same routine. Examples of this type of requirement might be personnel records tied to a…