Learn How to Build an Ionic App with an RSS Feed [Video]
Looking to add an RSS feed into your Ionic app? This video shows you to display an RSS feed inside an Ionic app.
Learn from other short YouTube videos on the Appery.io channel.
Looking to add an RSS feed into your Ionic app? This video shows you to display an RSS feed inside an Ionic app.
Learn from other short YouTube videos on the Appery.io channel.
This short video shows how to build a complete app with an external REST API. This video covers:
Looking for more videos? Visit our YouTube channel for many more short videos.
Hi there – this is John, Appery.io CEO.
There has been a fair amount of discussion on the recent change in pricing for the Appery.io platform. I do want to assure you all that we are reading, listening, and we do understand the concern. We are grandfathering existing customers to their plans, but even without that, the change would actually affect a very small number of our customers as our platform is very efficient in the use of API calls, etc..
These changes should only impact a few of our customers that have the higher levels of consumption and need high levels of support and SLAs. For those customers you can contact us and we can work with you on an appropriate business model.
For the vast majority of customers, the only effect is that you will end each month having consumed 50% or 75% of the allowance versus an extremely small percentage.
By doing this, we are moving our high consumption customers to appropriate plans so that performance and quality of service is maintained for all. Please post any comments or questions and I will be happy to answer them.
This short video shows how to import backend services APIs into your app. Appery.io services consist of a cloud database, Server Code for custom app logic, and API Express for enterprise integration and service orchestration.
Our YouTube channel has many more short videos where you can learn how to build apps fast with Appery.io.
Update August 25: Please see a message on pricing from our CEO.
On August 30th, 2016 we will be revamping the online pricing for the Appery.io platform. Although pricing will be generally higher reflecting the significant enhancements we’ve introduced, we will grandfather in existing paid subscriptions.
If you are considering subscribing or upgrading your plan, you may want to do so before August 30th to be grandfathered in at today’s prices. Your price will be locked unless you make changes later. This is a great time to lock in the annual plan (or monthly) which has a big discount included. Please see the note about grandfathered plans at the end of this post.
To simplify the pricing there are now three plans: Pro, Team, and Enterprise.
The Pro plan is good for individual developers or small teams. The plan comes with 1 developer seat, and you can add 2 more developer seats to join your team.
The Team plan is for larger mobile development teams coming with 6 developer seats.
The Enterprise plan is for small, medium and large enterprises. The Enterprise plan may have any number of developer seats, apps, or API calls. It has private cloud or on-premise installation option, SLAs, and premium support.
We have also simplified and consolidated the platform API calls. There is now a single count for all platform API calls which includes: Database, Server Code, Push Notifications and API Express.
New pricing:
Pro | Team | Enterprise | |
---|---|---|---|
About grandfathering current subscriptions (Basic, Standard, Pro, and Premium): Current paid subscriptions will continue with existing prices until a change is made to the subscription. Any change in the subscription will require the customer to change to one of the existing/current plans at the time of the change. For example, adding or subtracting developer seats, upgrading or downgrading a subscription, or letting a subscription expire without payment will require the selection of one of the new plans, at the new pricing. If you subscription expires or cancels due to no payment, you will need to select from one of the existing/current plans as well.
Appery.io App Builder – Ionic app.
One of the biggest pet peeves developers have is when they lose configurations, settings or default views they set in their development tools and need to reconfigure everything again. We are happy to share with you that we solved one of these pet peeves. When working in Appery.io App Builder, the platform now remembers the size and state (open/close) of the following panels:
This means if you resized the Properties panel or the Events panel and come back to this app, the App Builder will remember the settings you set for these panels. If you opened four tabs to edit pages and come back to edit this app in two days, we will remember what pages you have opened and will also remember which sub-tab you had opened (Design/Scope/Binding for AngularJS and Design/Data for jQuery Mobile).
A quick note on where this information is saved. The settings are stored in browser’s local storage. This means if you open the app in another browser/computer, your previously saved settings on another browser/computer will not be applied.
We think this is a great improvement and greatly improves the developer experience. Try it today and let us know what you think.
We want to let you know that after September 15, 2016 we will be moving the Appery.io platform to HTTPS protocol. This blog post explains everything that you need to know about this update.
Why the switch to HTTPS? Going to an HTTPS page (instead, of HTTP page) protects you against malicious activities, such as site forgery, content alteration, and others.
All Appery.io Backend Services already use HTTPS protocol so there is nothing you need to do here. This means that when you invoke an Appery.io backend service from an app such API Express, database, or Server Code script, the REST API URL uses HTTPS. This has been supported from the very beginning of our platform.
Secured API Express service.
We have streamlined our approach for creating your app backend and connecting to external REST APIs. Your app backend consists of the following components:
Once you create your app backend using one or more of these services, it’s now very simple to import the services into your app (client)
All the services are now under Backend Services menu but more importantly, the services will be automatically imported into your app. These services are preconfigured and ready to be used in your app.
Connecting to external 3rd party APIs is now easily done from API Express or Server Code. There are a number of benefits invoking a 3rd party API from the server:
Note: Invoking API directly from the client is still possible if your Appery.io account was created before July 16, 2016. This option is also available for a custom or enterprise plans.
The source code editor inside the App Builder has been upgraded to Ace editor. The new editor provides the following new benefits:
We are excited about the new editor, its modern architecture and speed will allow us to introduce new benefits and features in the future.
We are also excited about our new docs portal. The new site has a modern look and feel, better topic organization, improved search functionality, and a simple way to submit edits to the docs. There is a separate and modern API section with a large number of code examples, and new and updated quickstart tutorials. The new site will allow us to continue developing our docs, examples and tutorials in a much simpler way.
No release can be without fixing bugs. We did that, and also made a number of infrastructure improvements to ensure platform stability and performance. If you run into any hiccups with this release (hey, we are not perfect), please reach to us via on the forum or email.
Read our first post on moving app logic to the server.
The Appery.io Database provides storage for your mobile app data. You can store data such as users, orders, purchases, products or anything else. The Appery.io Database is a cloud NoSQL database and provides a very simple and elegant REST API to work with the database.
One of the most common cases for an enterprise mobile app is to create/save a new item/record and then redisplay the list in the app with the newly created item.
Accessing the database directly from the client is fine but requires two requests to the database.
A better approach is to do both the create and list in a single request from the app. This is very simple to do from Appery.io Server Code script. The following script shows how to create a new record and then get the updated list:
var dbId = "cdaec951....d8"; var collectionName = "People" var newName = request.get("name"); var newTitle = request.get("title"); // Save new object into the collection Collection.createObject(dbId, collectionName, { "name": newName, "title": newTitle }); // Retrieve updated data from the collection var result = Collection.query(dbId, collectionName); // Return the updated list (including the new object) Apperyio.response.success(result, "application/json");
In this simple script you first create a new Person object (line 8) and then do another query to get the updated list of people (line 14). The script response returns the updated list of people. This script automatically has a REST API which is the invoked from the app.
What’s most important, there is only a single request from the app to the Server Code script. A single request is usually better than two requests. Also, you can add additional logic to the script without impacting the app. For example, you can send an email when a new person is added. Or, you can send Push Notification when a new person is added. All this can be done without impacting the app. That’s nice.
If you want to learn more about Server Code, check out our YouTube channel Server Code playlist.
An Appery.io developer posted a question on the Appery.io Facebook page on how to write a Server Code script to query two different collections in the database. This post will show you how to do that.
In general, querying two database collections is better to do on the server-side than from the client. Doing it on the server is a lot faster and provides you with the option to update the search without impacting the client. Plus, you can add any logic when needed. Doing it from the client would require two REST API calls to the database.
Let’s jump into the example.
First, there are two collections in the Appery.io Database. They look like this:
ProductName collection:
ProductName collection.
This collection is simple. It has a name and a code.
This is the ProductData collection:
ProductData collection.
The code in this collection links the product name to the actual product (Android or iOS device).