Backendless provides a powerful and convenient tool for working with Backendless services through REST API (read all about our REST APIs in the documentation here). In case you need to quickly test a REST API’s functionality, another tool may come in handy for you – the Backendless REST Console.
In this series of articles, we are going to show you how to make a beautiful chat app that supports sending, editing, and deleting messages with both text and images.
When working with data, particularly user-submitted data, you often need to validate it. For example, if we are creating a database in which there is a “site” field and corresponding IP address field, it would be very useful to ensure that the data written to these fields is in the appropriate format.
In this article, we’ll consider some practical examples of how to use the Backendless Data Collection library to its fullest extent. You can find code documentation and sources for the library here.
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 another post, we describe how data tables in Backendless map to the client-side classes whose instances contain persisted data objects. However, there are scenarios when the default mapping is undesirable. In that case, Backendless client libraries provide an API to override the mapping.
In another article, we wrote how to load the first object from a data table using API. For the purpose of symmetry (and out of common sense), there is also an API to load the last object from a data table in your Backendless Database. The last object is determined by the time when it is…
Data objects in Backendless can be connected to related properties not only in other tables, but also with Geopoints. These relationships may be declared programmatically or using Backendless Console. In this post, we will review the process of declaring a Data-to-Geo relationship in a data table schema.
Whether you develop with IntelliJ IDEA, Eclipse, or Android Studio, the Backendless library (jar) for Java/Android must be referenced as a dependency. The library includes all the APIs that provide access to the backend functionality. The library is deployed to the centralized Maven repository, which makes it easy to import it to any Backendless-powered app.