In a previous article (Developing a Custom Skill for an Alexa Game), we showed you how to build a custom Alexa skill using Backendless and our Amazon Alexa Skill SDK. We made a game called Guess My Number that was played using Alexa. Now, we are going to show how to make the same game using our Codeless feature – in other words – without any coding!
You can read more about what Codeless is and how it works here.
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 will create a simple native mobile application with both parts, and we will be doing so with no coding whatsoever. Backendless will handle our backend; it gives us everything that we need from the server-side. For development of the client side, we will use a service called Dropsource. In case if you aren’t familiar with this service, you can read more about it on their official site. In the end, we will have a simple native mobile application with a Sign Up/Sign In screen, ToDo List screen, and Add New ToDo Item screen. The app we will be building today will be native for iOS.
Let’s do it.
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 though the Registration and Login example app available in the Code Generation section of your Backendless Console.
In a previous article (How to Save an Object with All the Children in a Single Call to Server), we examined how to simply save an object model. However, Backendless custom services give us much more flexibility when it comes to saving objects. In this article, we are going to cover how to perform complex business logic actions such as saving an object with calculated information in one API call using custom services. As we’ll demonstrate in this example, you can actually encapsulate entire portions of your business logic on the server side.
For this example, we will build a custom service that will emulate the order process for an automotive technician service station.
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.
You can download the prepared template from the author’s GitHub repo here and switch to the basicTemplate branch. Go to the root of the downloaded project and run the `pod install` / `pod update` command to install all necessary dependencies. After the dependencies are installed, open the created .xcworkspace file. The basic project contains a description of ViewControllers , table cells, resources (pictures used in this app) and the keyboard appearance logic.
From time to time, we see some developers struggle with understanding the principles of asynchronous work with Backendless. In this post we’ll try to shed more light on this aspect: describe what async calls are, why you need them and how to properly perform such calls and process the results. This post will be specific to Java and Android, but most of the principles apply to any language and environment.
Today, we are going to look at a useful and interesting, but hidden, feature of Backendless. Some features like these are not covered in the documentation, so they are not recommended for use in production because they are not supported and there is no guarantee that their implementation will not change. Still, these features can be very helpful during initial development. Using these features is not for the faint of heart!
This post will show you how to implement a kind of “expiration” for your data objects. The strategy is sufficiently abstract, so it’s applicable to any resource you need to expire, including files, logs, and so on.
Since the database does not have any built-in expiration mechanism, we’ll have to implement it on our own. Fortunately, the task is pretty easy because we have access to Backendless Business Logic. The idea is to create a Timer, which is going to run with some fixed time period and delete the resources based on your criteria.
In this article we are going to demonstrate how to create a simple chat application with the new Backendless SDK for Flutter. This will give you an overview of the process needed to integrate your Backendless server-side with your Flutter app client-side. The Backendless SDK for Flutter is currently available for Android and coming soon for iOS.
One of the final steps before you release an app is to setup proper security. Specifically, the security of your File Storage is perhaps the most important since it may contain your business logic code, your public website data, your logs, and any other assets which you probably do not want anyone from the outside to be able to see. This post will provide a few guidelines on how to structure your File Storage with security in mind and instructions on how to set up the permissions properly. The sample use-case will be a bit over-concerned with security, so you most likely won’t need all of this for your specific case, but you’ll be aware of what to do in the worst case.