Backendless Push Notifications are getting a much-needed facelift. Today, with the release of version 4.3.0 you will start noticing some improvements. Specifically, you will see the  DeviceRegistration data table:

Backendless supports two approaches for saving data objects in the database: class-based approach and map/dictionary approach. With the class approach, you declare a class, instances of which represent individual objects stored in the database. With the introduction of Swift 4, it is important to add a new attribute to your Swift 4 classes. For example:

Notice the @objcMembers  attribute declaration in the class. The attribute allows Backendless SDK (which is written in Objective-C) to access object’s property values. If you do not add the attribute, objects retrieved from the server will not have properties initialized with the values.

It is also possible to set a project-wide configuration property. When you do that, you do not need to add @objcMembers  attribute, however, you will see warnings when the project is built. To set the project property, open “Build Settings” for the project target, locate “Swift 3 @objc inference” and set it to “On”.

For additional information on the @objcMembers attribute, see the “inheriting from Objective-C Classes” section in the Swift 4 programming guide.

Data retrieval in Backendless has gotten significantly more powerful with the release of version 4.2.0. We added support for subquery into the syntax of whereClause . The improvement allows your apps to run two queries in the context of one request. The first query identifies a set of objects which is fed into the second query. Consider the following data schema:

Suppose your app needs to get all blog posts where the person who posted a comment has a specific email address (say @backendless.com ). Using subqueries, it can be done with the following whereClause sent to the BlogPost table:

Let’s review how this whereClause is processed by Backendless:

1. Backendless detects that the query at the top level uses the in()  operator.
2. It checks if the contents of the  in()  operator have the format of a subquery and if so, evaluates it accordingly.
3. The subquery contains an “internal whereClause”, which is:
   author.email LIKE '%@backendless.com'
   The internal whereClause is applied to the objects in the Comment table.
4. For all found  Comment objects, Backendless gets a list of values for the blogPost.objectId column.
5. The resulting set is fed into the  in()  operator which fetches the final set of objects from the  BlogPost table.

General SubQuery Syntax

The general syntax for subqueries is:

How it works:

1. If internalWhereClause  is present, it is executed in the table identified by TableName.
2. In the resulting set of records, values must be selected for the column identified by columnOrRelatedColumnName.optionalColumnName.
3. If internalWhereClause is not present, the contents of the IN operator have the following syntax. It represents the entire set of values identified by the specified column: TableName.columnOrRelatedColumnName.optionalColumnName 
4. The resulting set of values is used in the  IN operator, thus the final query ends up being:
   searchColumnOrRelatedColumnName IN ( value1, value2,, valueN ) 

Additional Examples

Consider the following data schema:

1. Get all OrderItem  objects for a customer from New York :
   objectId in (Order[customer.address = 'New York'].items.objectId)
2. Get all Customer  objects who spent more than 1.99 on an item:
   objectId in (Order[items.itemPrice > 1.99].customer.objectId )

Please let us know if you can think of additional examples you would like us to demonstrate.

Enjoy!

We believe that Backendless is great. We know that many of developers building with Backendless think so too. This is why we added support for referrals. It is built right into the Backendless console and every Backendless developer got his/her own invite code. There is a convenient way to access the “Invites” page by clicking the “Send an Invite” link:

The Invites and Referrals page is self-explanatory. It shows your own personal invite code and lets you send out an invite to anyone. You do not have to use the invite form, simply share the invite code and ask your developer friends use it when they create a Backendless app:

The referral system follows the rules below:

1. You cannot send out an invite while your app is on the free trial for the Cloud99 plan. Keep in mind that every app starts with a 14 days trial on the Cloud99 plan.
2. The developer you invite may already have an account with Backendless. If they do not, they would need to register.
3. An invite code can be entered only at the time when an app is being created. The “New App” popup has been modified to allow an invite code.
4. Invite codes apply only to new apps. You cannot apply an invite code to an existing app.
5. When a developer you invited upgrades their app to a billing plan, they get 25% off the plan’s price for the first 6 months. At the same time, you will get a $10.00 credit for your app, even if you are on the free plan.
6. The referral discount does not apply to the Marketplace purchases.
7. You (the inviting developer) can accumulate an unlimited number of credits and they will be automatically applied when you upgrade to a paid plan or make a purchase.

That’s all, it is a pretty simple system. Spread the Backendless love!

Codeless Programming is a general approach for creating programs without writing any code. When combined with the power of the Backendess mBaaS, Codeless becomes a powerful and super-efficient tool. In this post, I will describe how to use Codeless to create a custom Amazon Alexa skill. In the first part, you will develop a basic Alexa skill which replies with a static greeting to a voice command. The second post will delve into a more complex implementation.

You can see a demo of what you will build over the course of both posts in the video below:

Mark your calendars, we will be conducting a webinar to talk about Codeless. Get all the information about this exciting technology straight from the source. There will be a technical walkthrough and demos showing how to build with Codeless.

When: Aug 22, 2017, 1:00pm US Central Time
Host: Mark Piller, Backendless founder and CEO

Registration is required. Register now.

The core of the Codeless technology we released last week is the Codeless Logic Designer. It is a visual environment for composing logic of your API/IoT services, Event Handlers, and Timers. The system uses “blocks”, a jigsaw puzzle-like UI components placed into categories. When you create a codeless service, you snap blocks to create the logic. As you do it, Backendless automatically generates the source code which will be executed once the logic is deployed. Check out the video below for an overview of the Codeless user interface:

With the release of Backendless Cloud v4.1.0 we added an amazing new feature called Codeless Programming. Using Codeless anyone can develop in Backendless without any knowledge of a programming language. The environment is fully visual and lets you create API/IoT Services, Backendless API Event Handlers and Timers. The system can be used to create programs of any complexity. Created logic can be deployed to become an instant API service accessible via REST API as well as dynamically generated native SDKs.  Codeless programs can be either independently standing services or can extend and enhance a Backendless application.

With the recent update of the Backendless service (version 4.0.8) you can now add your app’s icon and the appstores links in Backendless console. This is done so we can make it easier for you to identify the app and also to help us build a gallery of apps powered by Backendless. We are also planning to provide templates for your app’s web-based home page to help you market your Backendless apps.

When you login to console, you will see a form where you can upload the icon and enter the URLs for Apple’s and Google app stores.

Quite often you need to run a test query or send an API request to see the server response. Our REST docs show examples using curl , but at times it may be inconvenient. You may need to play with the API request arguments, change the body, etc and modifying your curl  command is not as straightforward. To make it easier, we create a collection of our APIs for Postman. If you are not familiar with Postman, it is a desktop tool that lets you run API requests, see the server responses, you can easily change the endpoint URLs, request headers and body. Adding our APIs collection into Postman is now as simple as a click of a button because that button is integrated directly into Backendless Console. Check out the video below for an overview of the integration.