The user accounts of a Backendless application are managed by the User Service, part of our user management feature. However, the data for the accounts is stored in the Data Service storage. As a result, you can use the Data Service API to load the user objects for an application. Moreover, any search queries, paging,…
Sometimes (or in some cases, every time) when you invoke a custom API Service, you may need additional information about the context from which the HTTP request was sent/received, such as user or device information. To collect that information, we provide a class called InvocationContext.
In a previous article (Developing a Custom Skill for an Alexa Game), we showed you how to build a custom Alexa skill using Backendless and our Amazon Alexa Skill SDK. Now, we are going to show how to make the same game using our Codeless feature – in other words – without any coding!
In this article, we will show you how to write a service that will backup your application data with a time interval you specify. To do this, we will be using Cloud Code, a JavaScript timer, and the console SDK.
Today we are going to demonstrate how to create and save new data objects using the very convenient REST Console in Backendless. The console lets you easily test your REST APIs prior to deployment.
In this edition of Backendless Spotlight, we visit the Pacific Northwest where a group of local leaders has created an app to guide tourists through a historically significant part of Tacoma, Washington, known as Japantown.
Today we’re going to take another look at data security configurations in Backendless. In this article, we will talk about how to restrict direct access to your data via API and only expose your custom API endpoints.
Today we are going to walk you through the process of allowing users to register and log into your app using their Google account. The best way to showcase this is to walk through the Registration and Login example app available in the Code Generation section of your Backendless Console.
Have you ever wondered why is it often so tedious so make your simple Java app a web server, with the methods becoming the endpoints? You need to add libraries, write additional “web” wrappers, set up a server and a hosting, configure load balancing and much, much more.