Message:

Backendless Blog

Subscribe rss
Blog categories

In my post yesterday I wrote about support for multiple environments for your apps’ mBaaS backend. These could include development, testing, staging and/or production. As backend advances through its 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 the environments. Take a look at the following interface:

Continue reading

Posted in Feature-a-Day

As application is progressing through its lifecycle, there are different teams involved in interacting with the app and its backend. These teams include developers, testers, security auditors, system administrators ultimately customers and the users of the app.

Traditionally, application goes through the stages of development, testing, staging and production. Each stage has its own group of users. It is important that each stage has its backend with all the data, security policies and business processes in an isolated from other stages environment. Backendless provides support for multiple app environments through a feature called Versioning.

Continue reading

Posted in Feature-a-Day

One of the hidden gems packed with features is Backendless REST Console. It is a part of Backendless console and is located in its own tab on the Data screen. The console does exactly what it sounds like – lets you run REST requests against your data tables. Let’s review how fetching your data (AKA running HTTP GET requests) works in REST Console:

  1. Login to Backendless Console, select an app and click the Data icon.
  2. Select a table that has some records.
  3. Click the REST Console tab.
  4. The table you selected in step (2) is the context of all subsequent operations in REST Console. Try clicking another table and notice the change in the Request URL field. Make sure a table with at least one record is selected.
  5. Click the GET button. REST Console makes an HTTP GET request to the server, receives the response and renders it in the Response Body area. You can also see the request headers if you click the show headers link.
    Continue reading

In my previous post I reviewed the user registration API. Now that you know how to use the registration API and have a registered user, the next step is to review the login functionality. The video below focuses on the apps’ login screen and the Backendless Login API.

In the previous post I described how to obtain file’s public URL using the Backendless developer console. Even though one may obtain a public URL for a file or directory, it is very easy to change the permissions to restrict file download for anonymous (not authenticated) users. To restrict access:

  1. Login to the Backendless developer console, select an app and click the Files icon.
  2. Navigate to the file or directory for which public access should be denied.
  3. Click the lock icon to switch to the Security screen.
  4. Click the Roles Permissions menu.
  5. Click the checkmark icon in the cell at the intersection of the row for NotAuthenticatedUser and the Read column until you get a red X icon as shown in the screenshot below:
    Continue reading

Any file in the Backendless File storage is also accessible through a public URL. This functionality can be restricted by changing security settings. Public file URL can be built using the following format:


where <application id>   <path> and  <filename> should be replaced with the specific values. Another way to obtain file’s public URL is by using Backendless console:
Continue reading

In the video below I review the code for the User Registration screen of the RestaurantToGo sample app. Additionally, I discuss the usage of the Backendless Registration API. In the previous post and video, I reviewed the process of setting up the development environment for the application.

This is the first post in the series documenting a sample Android app we built to demonstrate various Backendless features. (You can read/watch project overview posted earlier) The video below demonstrates the following:

  • Retrieving project from its github repository.
  • Running the app in emulator.
  • Creating a Backendless account.
  • Importing app data to your Backendless backend.
  • Configuring the project to use your backend.

Posted in Uncategorized

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 which provide access to the backend functionality. The library is deployed to the centralized Maven repository which makes it trivial to import it to any Backendless-powered app. Below are the instructions for referencing it in Android Studio:

Continue reading

In my previous post I described a feature for conditional pub/sub message delivery using SQL selectors. With that (selector) approach the publisher must attach headers to the message and the subscriber uses an SQL-based condition which references header names and values. In addition to selectors, Backendless supports another type of conditional delivery – subtopics. Consider the following example:

A message with an announcement from Microsoft is published to topic stocks.nasdaq.msft. Another message from IBM is published to stocks.nyse.ibm. Suppose a subscribe wants to receive all messages related to stock announcements. In this case, it subscribes to the stocks.* subtopic. Another subscriber is interested in all Nasdaq announcements. That subscriber subscribers to the stocks.nasdaq.* subtopic. Finally, to receive Microsoft announcements, a subscriber would use the stocks.nasdaq.msft subtopic. As you can see Backendless uses the federated subtopic structure for message filtering/delivery. The sample below shows how to use subtopics in the Backendless messaging API:

Continue reading