Blog

An app that has multi-language support is always better than the same app that supports just one language.  Appery.io app can be easily upgraded with multi-language support by using the i18next plug-in. This post will show you how to do it.

There are few steps to add the multi-language support:

1. Download i18next.js from the i18next web-site and upload it to WEB_RESOURCES folder in Appery.io app builder.
2. Create folder structure that corresponds to i18next structure and upload translation files in JSON format:
   
3. UI components that should be translated must be marked with special attributes: data-i18n, and data-i18n-target. Read more about it in our detailed tutorial.
4. Initialize the plug-in via JavaScript specifying needed options as initialize language (can be retrieved from the browser or device language) and fallback language. Fallback language is very handy feature and it’s define what language should be used in case of missing language or translation.

Downloading of translation files will take some time on initial app start up. There is no need to create any preloaders as all the files will be loaded automatically. It’s a good idea to use launch images to show that the app launching/loading. Once the translation files are loaded, properly marked components will be automatically translated accordingly to the initialized language.

To build an app with multi-language support, try the multi-language tutorial and read the i18next documentation.

Every modern app consists of two parts: front-end UI and backend. Backend services can greatly extend your app logic and help implement many useful features.  Appery.io provides a possibility to create your own server scripts without the need to maintain servers yourself.  Server code scripts (that’s how this feature is called in Appery.io) can be invoked from the app via a REST API and will  run on the Appery.io servers.

Using server code scripts provides the following advantages:

• Broader app logic
  Use server code services to extend your app logic. You can implement various backend features such as Restore password and others.  Some code logically belongs on the server.  For example, if you need to process data retrieved from multiple sources before presenting the results to the user, its more efficient to perform that logic in the server.
• Reusable code base
  Appery.io server scripts can be self-contained app modules which can be used from different apps. You can implement one handy feature and re-use it from all of your apps instantly and without any additional coding.
• Code accessibility 
  As Appery.io provides powerful a collaboration feature, server code can be shared with other users too. This makes team development much easier and faster.
• Extend with powerful 3rd party libraries 
  Server code supports several predefined libraries such as Underscore.js, moment.js, handlebar.js and others. You can also upload your own or other 3-rd party library and use it from the Appery.io. Libraries can be shared too!
• Keep your users on the latest version of the code.  Another important advantage of server code is the ability to modify your app without having to redistribute your app to your users.  If you make changes on the client side, that requires an update in the app store, and an update by all your users.  But if your logic is server based, you can be sure that all your users always have the latest version of your app.

The server code console can help test and debug your scripts from one place without the need to run REST API services. Want to add custom app logic to your app? Start with Server Code by trying this tutorial! And, to learn more about Appery.io Server Code, visit the documentation.

Many mobile apps use GPS sensors to track a user’s current location. For example, it could be a ride sharing app, fitness app, or a delivery app. This post shows how to build such an app in Appery.io. The app tracks your current location via  the device’s GPS sensor and stores the location into a database.

This is the app UI:

The GPS location is determined every 15 seconds (you can change the interval). The location is shown in the app and also saved into a cloud database. Because this is a native app (with PhoneGap), the app will continue tracking the location even if in the background or with the phone screen locked.

To try this app, download the app backup and create a new app from it. Keep in mind that you do need to build a binary file and install it on the device for testing.

Now you just need to configure the settings service with the correct database ID. This app uses a pretty simple database; it contains one collection with name Locations. This collection contains one column location with type of Geo point:

Open the GPSLocationTracking_settings file and change the database_id to your own.

Once the database ID is changed in the settings file, the application is ready to go.

Let’s take a quick look how the app works:

1. The GPS service starts initially after the Device ready event and runs every 15 seconds.

Here is the JavaScript code:

2. You can also change how often the GPS will run. To apply a new interval, first stop tracking, and then start it again:

3. In the case that the GPS fails to determine the location, an error message will be shown:

4. Every time a new GPS location is retrieved, the location is saved into a cloud database:

This is a starter app that uses the GPS sensor to track your current location. It’s very easy to add more features. For instance, you can add Google Reverse Geocoding service to get the address of a place. Or, you could also show all locations on a map.

If you want more practice, try the Building a mobile app with Google Maps and Geolocation tutorial.

Last November, we partnered with VisionMobile to help them reach out for their Developer Economics survey. Now the data for VisionMobile’s well-known reports on the state of the developer nation is out. The report features in-depth analysis and insights into the key issues in the app economy, including platform prioritization, going beyond tablets, trending revenue models, and making the right choices in developer tools.

Download the full report for free.

Push notifications. It is a great way to inform app users about cool offers, important events or any updates. It’s an important feature for enterprise mobile apps. For instance, a sales manager can be instantly notified when an existing customer upgrades his/her plan.  Push notifications are a powerful tool to ensure your message is received and read by the user, even when they are not using your app.

Appery.io provides fast and easy way to send the push notifications for both platforms – iOS and Android. Sending can be done in just a few steps:

1. Enable push notifications in the application settings.
2. Register the application with Apple or Google services.
3. Install the app on the device. When it’s done, device information will be automatically added to your predefined devices collection.
4. Send notifications from the console. That it!

You can send these alerts:

1. Instantly
2. Schedule
3. Deliver in device’s time zone

The first two options, all the users will receive the message simultaneously. For instance, for some users it could be 8 AM, and for other users it could be 1 PM.

In the third case of the device time zone sending, users will receive the notifications in a different time – someone later and someone sooner.

Having all three options — is what makes Appery.io push easy to use, yet very powerful, and customizable.

You are not limited to sending push notifications from the push console. With push REST API, you can enable sending messages from any app.

Want to learn more? Head to our push docs or try the quick start push tutorial.

Mashable recently compiled a list of the best mobile app builders, and Appery.io topped the list of 10 contenders. While we’re quite pleased to be considered #1 as just an app builder, we like to remind people that we are a full mobile app platform with a great suite of seamlessly integrable back-end services. So, with Appery.io, you get the best building tool—and much more.

Read the whole article.

Our partner, Salesforce.com, certainly knows how to get your attention. They certainly got mine! This is a really great opportunity for mobile app developers. (The runner-up prizes aren’t too shabby either.)

What is this? Salesforce.com hosts a big annual uber-conference called Dreamforce. This year’s runs November 13-17 in San Francisco. As part of the conference, there’s a Developer Zone that focuses more on the technical side. If you have a bunch of developers together, you’re going to have a hackathon. The difference this time is that the prize is so amazing. Read the rest of this entry »

Fima Katz, Francisco Kattan, and Max Katz were all at MobileCON this year to promote Appery.io. Appery.io was a finalist for the Application Development & Platforms MobITS award, Francisco Kattan presented on “Is Your IT Department a Bottleneck for Mobile Innovation?”, Max Katz demoed Appery.io, and we made two announcements. Read the rest of this entry »

We recently updated Appery.io in a number of ways, adding up to a big step forward for the platform. At the same time, RESTXpress, an important part of the overall mobile solution provided by Appery.io, has been enhanced. We’ve discussed most of the improvements in Appery.io in a previous blog post, so I’ll just provide a summary of these before moving on to a discussion of the changes in RESTXpress.
Read the rest of this entry »

We are looking forward to our next webinar with Max Katz, Head of Product Management and Developer Relations for Appery.io. This time, he will be explaining how you can get the most out of Appery.io using its newest features, like advanced collaboration, Heroku integration (for publishing apps), and new UI components. You can see all of these new features demonstrated in this hands-on webinar. And, if there’s time, we might be able to squeeze in a little bit of the latest on RESTXpress, our secure web integration product … maybe.

What’s New in Appery.io
Wednesday, October 2nd, 10am Pacific time

Register now for the webinar.