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.
Dropsource is an online platform for developing Android and iOS applications without coding. The platform also lets you download the source code for your app so you can make any changes to it and subsequently publish into the app store (note: downloading the source code is a paid option). If you’re looking to add support for push notifications to your Dropsource apps, Backendless fits right in with a relatively simple integration. When you add Backendless Push Notifications, you can instantly benefit from the following features:
The video below includes a demonstration of an Android Dropsource app integrated with Backendless Push Notifications followed by a detailed overview of the actual integration process. The integration instructions are outlined in detail in this post following the video.
Developing apps can be fun especially if you can do it without knowing how to write code. There is a lot of hype around the no-code and low-code trends, however, very few solutions can actually demonstrate successful examples. Here’s real proof of a mobile chat app built without any coding. The app is built using Dropsource and Backendless. Some companies will quote you thousands of dollars to built something similar, however, with the demonstrated approach, not only you can do it in a matter of hours using a beautiful UI builder right in the browser, you get the extreme scalability with the Backendless mobile backend. The video below demonstrates the app and walks you through the process of developing it:
The mission of Backendless is to simplify the app development process. We strive to empower software developers to build apps without spending any time on monotonous and repetitive coding tasks. In most cases, a developer working with Backendless should not even think about the server-side and focus entirely on the user experience. We have seen thousands of apps getting built the standard way – that is using code. Whether it is Java, Objective-C, Swift, JS or C#, developers still write, compile, debug and profile code when building the client-side of their mobile apps. Can the process be simpler? Wouldn’t it be awesome if you could build a mobile app without knowing a programming language? Or better yet, how cool would it be if you could get all the boring and annoying parts of creating a skeleton of a mobile app using an easy-to-use and a powerful UI and after that jump into the code to handle more advanced tasks at that level? Yes, that would be awesome. What’s even more awesome is that such a solution is available now and it integrates nicely with Backendless. Welcome to Dropsource – a platform for developing mobile apps without any coding. And if you want to get the code, it will generate a complete Android Studio or Xcode project for you.
As the saying goes, it is better to see something once than to hear about it a thousand times. The video below starts with a demo of a mobile (iOS) client-server app built with Dropsource. This is a classic ToDo app which uses the Backendless database to store data and demonstrates a complete set of the database operations (Create, Retrieve, Update, Delete – CRUD). Right after the demo in the video, there is a detailed walkthrough showing how to build the app. If you follow the instructions, you will be developing the same app and learn how to use Dropsource and integrate it with Backendless. Enjoy!
This is Part 2 of a series of articles where you and I build a mobile app without any coding. The app we are working on is a ToDo app. In the previous post you did the following:
In this part of the series, you will implement the following:
Let’s get started (or technically continue, since we started in the previous post).
If you played or used Data Retrieval API in Backendless Cloud you may know that the server limits the number of objects retrieved from a table to 100 in a single call. For Managed Backendless and for Backendless Pro, this limit is configurable. In order to retrieve more than 100 objects, data paging is required. Paging greatly improves your application performance, but requires you to think how to architect your app in a certain way.
In this article I’ll describe how to get more than 100 objects, while using the minimum number of API calls, and do it without writing any code at all. Using this methodology, all that is needed to retrieve all objects from the database is a single call from the client application to the Backendless server.
Development of mobile applications generally requires two parts: the Backend and the Frontend. Of course, you could limit it only to the client-side, but if there is some data which must be stored on the server, there is no way to get around having a backend. In this series of articles, you will create a native mobile client-server application – a basic ToDo app. Backendless will take care of the backend, it gives you everything you might expecting from the server-side (user management, data persistence and scalability to name a few). And for the client side you will use the Dropsource service. In case if you are not familiar with this service, you can learn more about that from their website, but in short, it is an awesome service which lets you build native mobile apps without any coding. At the end of this series, your will have a native mobile application with the User Registration/Login screen, a screen with a listing of the ToDo items and a screen to create a new ToDo Item. Here’s a brief preview of the app along with real-time changes in the Backendless database:
Suppose your app logs in a user. As a result, the app gets user-token which uniquely identifies the user’s session with Backendless. If your app uses our SDK for Android, iOS, JS or .NET, the user-token value is managed directly by our libraries. Specifically, it is added to every API call to maintain the session and tell the server about the user’s identity. There are situations when you need to get the user object when your app has only user-token. This could happen if you used persistent login in the application, which stores user-token on the device. The implementation does not save the user object, however, there is a way to retrieve the user based on the user-token value (assuming the token is still valid). In this article, I will show you how to do this.
The technique for retrieving the user object is creating an API service which accepts a user-token in the header and retrieves the current user. I will use Codeless to create the API service because it has an intuitive interface and allows you to solve these tasks very quickly, just by building the algorithms instead of writing code:
If you have any smart IoT devices in your home or office and tried controlling them with Alexa, you might wonder how it actually works. In this guide you will learn about building a custom Alexa skill which will let you control a wi-fi enabled light bulb with Alexa. You will be able to turn the light on/off and change the light colors. You can see a demo of the completed project as well as an overview of its components in the video below:
The solution consists of the following components:
This is Part 2 of the article about developing an Amazon Alexa skill without any coding. In Part 1 you learned the following:
In this part of the article, you will learn the following:
It is recommended (more like required) to go through Part 1 just so you have the basic environment setup. Also, make sure to watch the “Developing an Alexa Skill without any coding” video which shows the entire process in action.