If your native language is not English and you use Backendless to develop applications, you more than likely already know about this feature. When you log into Backendless Console, it detects the locale of your computer and switches the user interface to that locale (if it is available).

A user on StackOverflow asked how to load only the data that belongs to the currently logged-in user. This is indeed an interesting and very common use-case. Backendless handles it beautifully and this feature certainly deserves a place among our Recipes.

There are plenty of use cases when mBaaS-powered applications must use a centralized mechanism for incrementing or decrementing a value. There are several approaches for maintaining a counter – some apps use a database, others keep it in the server-side business logic (Cloud Code).

There may be instances where you need to create a user manually in your database rather than through your application. Whenever you need to quickly create a user for your app, you can always use Backendless Console. The Console makes the user creation process simple. This approach requires no coding at all, and the created…

It’s rarely ideal to allow users to sign up using fake email addresses. The best way to prevent this is to require the email address be verified before the user can log in. Following up on our article on enabling email address confirmation for app users, in this article we will show you how to…

Now that you know how to generate code for custom business logic timers (Backendless background jobs) and how to locally debug custom business logic, it is time to learn how to deploy that code to production.

In a previous post, we introduced Backendless CodeRunner – a debugging utility for custom business logic. Now that you can run your timer code locally using CodeRunner, we’d like to show how you can attach your IDE to the CodeRunner process and debug the code.

In other posts, we have described how to set up a sample Geolocation data set and how to retrieve geopoints using the API. The geopoints in your application would not be the ones from the sample data set, we used it only to make it easier to get started with Backendless Geolocation. Adding geopoints to…

The Logout API is a logical counterpart for the User Login API, described in an article here. The full documentation for the Backendless REST logout API can be found here. The logout step is not required for most apps given that the user session will expire automatically. However, some apps choose to provide the functionality, especially…