CocoaPods manages library dependencies for your Xcode projects.
The dependencies for your projects are specified in a single text file called “Podfile”. CocoaPods resolves dependencies between libraries, fetches necessary code and links it together in an Xcode workspace to build your project.
This article reviews the APIs for working with relational persistent data in Backendless. By the end of the article, you will have a working application which demonstrates various mechanisms for loading related data objects from the backend-as-a-service data store. To avoid any terminology confusion or overlap, let’s define related data as multiple objects referencing one another in the object-oriented data model. For example, suppose there is a class called Order. The class aggregates (references) a collection of OrderItem’s. This is a one-to-many relation. The OrderItem class has a one-to-one relation with a class called Manufacturer. Consider the following diagram:
The goal of this post is to let you quickly become familiar with Backendless custom business logic feature. At the end of the instructions provided below you will have a Backendless application with a custom API event handler published into production – that is running on our servers.
It feels amazing to begin writing this post. I have been waiting for a long time to say it and I finally can – Backendless goes out of Beta! And boy, aren’t we doing it with quite a bang. Over the weekend we pushed a new release with a ton of fixes and some amazing functionality. It took us quite a while to get to this point, but I am quite sure the wait was worth it. The new release includes support for custom business logic, code generation, data validators, multi-environment (dev, test, stage, prod) support and many more. Please see below for details:
Establishing relations between user objects and other entities in an application is a very common use case. This post describes various scenarios and shows sample code using Backendless SDK for Java/Android and Backendless SDK for iOS. Make sure the version of the client libraries are at least 1.5 for Backendless Java/Android and 1.11 for iOS.
Tizen is an open source platform residing within the Linux Foundation. It includes an operating system which can run smartphones, tablets, netbooks, onboard devices in smart cars as well as smart TVs. We wanted to see what it would take to integrate a Tizen app with Backendless because the benefits of such integration would be huge. For instance, data can be easily shared between different implementations of an app: a Tizen version of the app can easily communicate with the one running on Android or iOS by the means of Backendless service APIs.
Our Data Service supports a very flexible security mechanism for restricting access to objects stored in Backendless. Security permissions apply to users and roles. A permission can either grant or reject an operation for a particular asset. In the context of Data Service, the asset is an object which your app can retrieve, update or delete. Permissions can be granted or rejected globally, where they apply to all tables and all objects in the data store. Additionally, every table may have its own permission matrix and owner policy – a special instruction whether object owners can or cannot retrieve/update/delete the objects they ‘own’. Finally, every object has its own Access Control List (ACL) which is a matrix of permissions for the operations applicable specifically to the object:
It is hard to believe January is already over. We will remember this month as one filled with a lot of hard work, implementing cool features and fixing some interesting bugs. All of this came to fruition today since we pushed a new release out of the door. To sum the release up with just one word, it would be called “awesome”. Here’s a brief summary of what you will find now in Backendless:
Any time you save an object in Backendless using the Data Service, we automatically assign the ‘owner’ to the object (assuming there is a currently logged in user). Having an association between a user and the objects he created is helpful since it makes it so much easier for a user to retrieve only the objects he owns. Along with the support for Object ACL, we have greatly enhanced the system of permissions for objects and tables. In fact, the system is so flexible that you can configure any kind of scenario for secure data access (load only objects one created, load only objects which were created anonymously, load only objects which belong to users in specific roles, etc). There will be a detailed blog post with the detailed information about Object ACL.
Being able to control access to files and folders stored in the Backendless File Service has been one of the most requested features. The wait is finally over. With today’s release you can control access to any file and folder using the same intuitive interface we have for other services. The File Browser interface now includes the “Edit Permissions” link for every single item. Clicking the link you can easily adjust the permission matrix for any user or role in the system.
The File Service received quite a makeover in today’s release. In addition to File Permissions, we also added Git integration. Once Git is enabled (you can do it from the Manage > App Settings screen), you can work with your file storage as a git repository. This may be particularly helpful for deploying multiple files or syncing between your local development environment and Backendless file system.
We are very excited about this release. There is a lot more that went into it than just these features – most importantly our passion and love for beautifully made software. We have a feature packed roadmap and can’t wait to get some amazing functionality into your hands. We hope you enjoy using it as much as we did designing and coding Backendless.
One of the coolest features included into our November release is support for mobile audio/video conferencing, screen and gesture sharing. This functionality is made possible through our partnership with ShowKit – a mobile SDK for iOS and other environments. Integration with Backendless makes it trivially easy to enable the users of your mobile app to conference with each other and share app screens. Complete documentation describing the integration is available in the Backendless Media Service API doc as well as ShowKit’s website.
How much does it cost? Is it free to use? What can I get for free? What are the limitations? How much will it cost as the application grows? These are all very reasonable questions. When you decide to use a backend-as-a-service system, you should definitely estimate your usage and see what you may end up spending over time. The good thing is with Backendless the API usage is unlimited – your application can make unlimited number of API calls and we will not charge you for that. There is only one plan with Backendless and it is free. The plan has some limits for the number of resources included into it. Once you go over the limits, you would pay only for what you use. The video below provides an overview of our plan. For additional information about the pricing, see the Backendless Pricing page.
[allvideogallery profile=2 category=1 video=2]