We just published a new tutorial that shows you how to build an HTML5 mobile app connected to OpenShift REST API. It’s based on this example.
The app has two pages, and two services. One service gets the current list of users. The second services creates a new user. Give it a try and let us know if you have any questions!
Last week we had our March release. Here is what’s new and cool.
We just added a bunch of new and awesome jQuery Mobile themes and swatches. Here is how the new Appery.io dark-gray theme looks:
Check out the rest here
Plugins make it possible to package services, screens, images as a “plugin” and then add the plugin to any other project. You can even create custom project templates from plugins. A plugin is created by selecting Export > Appery plugin:
To learn more, read plugins documentation.
The Appery.io visual editor is pretty cool but we know very well that being able to insert any custom code is a must have feature. In this release we added a new Panel component which can be.
Staying on the topic of customazing your app, in addition to being able to add any JavaScript you can now also create a custom CSS file:
A number of improvements were were do the visual data mapper. Once a connection is mapped, a grey dotted line appears to indicate to which variable the connection is made. 
We spent the last couple of days updating Appery.io documentation with all the new features. We’d love to hear your feedback. One thing we are definitely going to add is more tutorials!
In addition to standard jQuery Mobile themes, we just added a bunch of new and awesome themes and swatches to Appery.io Mobile App Builder.
You can set the swatch name from screen properties:
or click More themes link to change the theme:
ReadWriteMobile has posted an interesting Infographic created by Kinvey mapping the current mobile ecosystem (click on image to view larger version):
(Image source: http://kinvey.com/images/kinvey_backend-as-a-service_mobileecosystem_2100px.png)
First of all thanks to Kinvey for creating this wonderful map and including Appery.io in it (blue Mobile SDK line). Appery.io could actually span 3 different lines: BaaS, Mobile SDK and Mobile API. Appery.io is a cloud-based HTML5 mobile app builder, so it’s not exactly a mobile SDK. In fact, the technology under the hood is HTML, JavaScript and jQuery Mobile. For hybrid apps, the app can be wrapped in PhoneGap, which also provides access to native device features. So, there is no really “custom” SDK.
Second, from the builder it’s incredibly easy to consume any REST API (yellow Mobile API line). Appery.io comes with a pretty nice REST services console where any service can be tested. From the same console, the REST service response (structure) can be automatically created. Once the service is defined, it is mapped to jQuery Mobile UI using a visual mapper (UI to service input, service output to UI).
Thirdly, as most BaaS services (orange line) are exposed as REST, HTML5 mobile app built in Appery.io, can easily connect and use those services.
Lastly, and maybe the most important point is how incredibly fast you can build apps. It sort of all makes sense.. you got cloud-based mobile backend (exposed as REST) and cloud-based app builder to build the apps. It sounds simple.. but a really elegant picture.
This perfectly describes Appery.io. Appery.io is cloud-based builder for creating HTML5, jQuery Mobile, PhoneGap, and RESTful mobile apps.
Originally posted here.
In mid January we have released an update to Appery.io mobile app builder and now every app (new or old) is based on jQuery Mobile version 1.0.
Now that there is a Free plan, nothing should stop you from building your mobile app.
Lastly, if you need to write any custom JavaScript in your app, here is how.
Recording of our Learn How to Build Mobile Apps in the Cloud with HTML5, jQuery Mobile, REST, and PhoneGap webinar.
Recording of our webinar from November 16th: From an Idea to Android Market in 40 Minutes.
When: November 16, Wednesday, 11am US Pacific Time
Register: https://www1.gotomeeting.com/register/466425672
One of the great things about Appery.io Mobile Apps Builder is its support for end-to-end development, going all the way from an idea in one person’s mind to an app running in thousands of phones. In this webinar, we’ll show you exactly how it’s done (and how easy it is) by walking you through a hands-on example. The focus will be on exporting options for apps. In this case, we’ll export an Android binary (.apk) and publish to the Android Market. Of course, we’ll quickly build an app first, so you can learn or refresh your memory about how to build the UI with jQuery Mobile, connect to REST services, and test the app.
We just returned from app world conference in New York which was a great success. Next week we are heading to 2 more great events: AnDevCon conference and Mountain View JavaScript Meetup.
Appery.io Mobile Apps Builder is going to be at AnDevCon II (The Android Developer Conference) in San Francisco Bay Area, November 6-9. Stop by our booth and learn how to build Android apps ready for the Android Market using cloud services, all in about 5 minutes. It’s really awesome, I promise.
In this cool session you will learn how to build HTML5 and native apps using Appery.io. Appery.io is a cloud-based mobile apps builder that uses HTML5, jQuery Mobile, REST, and PhoneGap to build apps. A real mobile app will be built during the session, which attendees will be able to run and test on their own devices.
Sign up to attend this Meetup.
Navigating between pages in Appery.io is very simple. You first add an HTML event to a component, such as click for a button, and then add Navigate To Page action where you select the page to navigate:
This works very well, but it will replace the entire page. An alternative way to navigate or transition between pages is to use jQuery swipe transition which in my opinion looks better. Here is how to do it. You use the same event, such as click for a button. Then, we add Run Custom JavaScript action with the following code:
navigateTo('end', 's');
The first argument is the page name. The second argument indicates that a swipe transition should be done. That’s it. You are probably wondering why not do this via Navigate To Page action? It will be possible soon. We are going to add a check box so you will be able to select what type of transition you would like, a page replace or swipe. For now, this is a very simple work around.
Want to try it?
Just scan this QR code: