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.
We are happy to announce that Backendless 4 has been released out of Beta. It is now the default environment and all new apps are created in version 4. Now that the Beta is over we have enabled billing in version 4 and you can choose a pricing plan for your application. This can be done using the Manage > Billing section in the Backendless Console. There are four pricing plans to choose from. The details of the plans can be found on the Backendless Cloud Pricing page.
We have introduced a few changes:
We would like to thank everyone who helped us with 4.0 beta. We are very excited about the release and have a lot of very cool features in the works.
We will continue running the 3.x environment, however, we encourage you to migrate your app to 4.0. The free plan in 3.x will be available until November 1st, 2017. After then, the plan will be discontinued. Applications on the free plan in 3.x would either need to migrate to 4.0 or switch to a paid plan before November 1st.
We have had a very successful beta release and received a lot of positive feedback. We would like to thank everyone for your contribution which helped us make the product better than ever.
As we are preparing for the GA release of 4.0, there are changes which may affect your apps. Please see the list below:
With the introduction of Deployment Models for business logic (Cloud Code), we also added support for “invocation chains”. This is an ability to chain together multiple server-side event handlers registered to process the same event. Previously, you could inject cloud code into the API invocation flow as shown in the image below:
For any API call, you could have only one before/after event handler with your own custom business logic. This is changing with deployment models and you can have multiple event handlers chained together:
This is a HUGE improvement. It promotes better design for cloud code with a clean division of responsibilities between the event handlers. It is important to note that any data received as arguments for an API call is passed from one event handler to another. If an event handler sitting at the beginning of the chain makes a change to an argument (or the return value), then all other event handlers down the chain will get the modified value.
A question you might be asking is how to configure the order of the event handlers. This is done in the Backendless Console. Consider the following example:
As you can see there are three "beforeCreate" event handlers for the "*" context (which means they apply to every data table). When Backendless detects you have more than one event handler applicable to a particular context, it displays the “handler ordering” icon:
Clicking the icon opens up a popup where you can control the execution order for all applicable event handlers:
We’ll have a video posted to our YouTube channel with a demo of the functionality soon. That’s all for now, guys. Happy coding!
We are preparing one of the final Beta builds for Backendless 4. The build should be released early in the week of June 19th. We plan to release the service out of beta shortly after that. One of the important changes in the upcoming service update will be the introduction of deployment models. When the service is updated with that build, it will be necessary to redeploy your business logic (API Services, Event Handlers, and Timers) using the latest release of CodeRunner. If you do not do that, any existing business logic in the Backendless 4 apps will stop working.
We realize it is going to cause an inconvenience – we really wanted to avoid it. However, the service is in beta and we thought you’d cut us some slack.