When building a mobile application, as a rule, you will need to implement two parts: a backend and a frontend. Of course, we can confine ourselves to only the client-side (frontend), but when we have some data that should be stored on the server, we need to have the capability to capture it.
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.
As you may have noticed in our release history, the EXTENDED STRING data type was removed from Backendless Database almost a year ago. To be precise, it was more a merge of the STRING and EXTENDED STRING data than the removal of the latter.
In this edition of Backendless Spotlight, we take a dive into a business-supporting mobile software company called Inkscreen and their application CAPTOR.