It has been another great year here at Backendless! Coming in 2020, we will be taking another giant step forward with the release of Version 6.

As we move toward the launch of version 6.0, we are excited to introduce new features to the Backendless platform that will make your life easier starting today. In this article, we are going to introduce you to a highly-requested new feature, Developer Permissions.

One of our key standard features is the ability to send emails through Backendless Console. We offer prebuilt email templates or you can create your own email template. In this article, we will show you how to do the latter.

In a previous post, we described how to use the custom business logic code generator to create Backendless timer code. The previous post left off at the step when the Backendless Console created the code.

In a previous post, we wrote about Backendless server-side timers – blocks of code which run on a pre-defined schedule. A timer is a Java class and can be created by hand. The most tedious part is figuring out the scheduling definition. Currently, this is done by declaring the timer’s schedule through a JSON object…

There are two types of custom business logic (Cloud Code) scripts supported by Backendless – API event handlers and timers. In this post, we will review the latter. A timer is a server-side program deployed to the Backendless server infrastructure which is scheduled to run on a pre-defined schedule.

This is an introductory post for a very broad feature – injecting custom server-side logic into Backendless. There are a lot of smaller features in Cloud Code (also known as Custom Business Logic), but it’s worth it to start with a general overview.

This article applies to version 3 of Backendless. The versioning feature in the latest version can be achieved by cloning your application to create replicas for development and staging. As an application is progressing through its lifecycle, there are different teams involved in interacting with the app and its backend. These teams include developers, testers,…

In another post, we wrote about support for multiple environments for your apps’ mBaaS backend. These could include development, testing, staging and/or production. As your backend advances through those stages, an obvious question is how to migrate the backend’s data from one environment to another. Backendless provides a very advanced facility for backend migration between…