Second, from the builder it’s incredibly easy to consume any REST API (yellow Mobile API line). Tiggzi 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 Tiggzi, 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 Tiggzi. Tiggzi is cloud-based builder for creating HTML5, jQuery Mobile, PhoneGap, and RESTful mobile apps.
In this fascinating hands-on webinar, a real mobile app will be built, connected to a REST service, and tested. Attendees will be be able to test the app as it’s being built. Beyond that, we will also cover some of the exciting features of the new version of Tiggr that will have been released by then (under a new name…).
Learn How to Build Mobile Apps in the Cloud with HTML5, jQuery Mobile, REST, and PhoneGap
January 19, Thursday
11am US Pacific Time
Here is how the app look in design time in Tiggr:
There are three REST services on the right which connect to Parse mobile back end. The services are for loading the current list items, creating new list item and deleting a list item. For example, this is how the service URL to get all List items looks:
List – is a class I created in Parse.
This is how the service URL looks for deleting an item:
objectId – is the class Id to delete.
Parse mobile back end is very easy to use and is very elegant.
Here is how the actual app look when running:
I’ll publishing the actual tutorial on how to build this app.
Happy New Year!
Tiggr – the easiest platform for building mobile apps in the cloud
Building mobile UI with jQuery Mobile
To build the mobile UI, there is a visual editor and jQuery Mobile components, as shown below. You simply drag and drop components into the phone area.
Testing the mobile app
Testing is one of the most innovative features in Tiggr. There is a big Test button at the top. Clicking that button opens up a browser window with the mobile app in it. Need to test the app on the actual device? Scan the QR code, and e-mail the URL to your device. Don’t forget to make the app public. (More about testing native apps a little bit later.)
Consuming any cloud service
Once the UI is ready, the next step is connecting to cloud services. In Tiggr, you can connect to any cloud REST service. Below is an example of using the service editor to define a connection to Twitter’s search REST service:
Once the service is defined, it is mapped to the UI. A service usually has inputs and outputs. Mapping specifies how different UI components are related to different service parameters for input and output. There is even a visual data mapping editor available (service output is shown on the left, screen components are shown on the right:
One last step is adding an event to invoke the service. For example, on a specific button click (HTML click event) the service could be invoked. You can of course use any other HTML events. With Tiggr this is easy.
Native apps with PhoneGap
Exporting native app
Every app (native) in Tiggr comes with PhoneGap installed. To export the app as native is as simple as clicking the big Export button:
If you are targeting for Android, then you can download Android Release binary (.apk). This file is ready for the Android Market. Tiggr has a Android .apk file editor for you to enter all the necessary information.
If you are targeting iOS, then export iOS xCode project (Eclipse). You can then build the app on your machine or use cloud-based PhoneGap Build service to build for iOS.
As an alternative, for both Android, iOS or any other platform you can download the mobile Web version (Web resources, HTML/CSS/JS) and use PhoneGap Build service to build for the platform.
For example, if you need to build for BlackBerry, then simply download the mobile Web version and upload to PhoneGap Build. It’s that simple.
Using PhoneGap API
As an example, we will implement a Vibrate button.
First, we add the click HTML event to the button:
Testing native apps
Once you use a native API, testing in Web browser is no longer as useful. To test native apps, you can use Tiggr Mobile Tester. It’s a native app (Android, iOS) that lists all your mobile app in Tiggr. You simply tap any app in the list to launch the native app for testing. It’s the easiest and fasted way to test a native app without having to install it. The tester app looks like this:
This is even simpler than using the API. More components are planned to be added such as Camera and others.
Tiggr and PhoneGap – The ULTIMATE mobile app development combo?
We think so.
When you combine the two, Tiggr and PhoneGap, you get powerful cloud-based HTML5 mobile apps builder with an easy way to incorporate native device features and build for multiple mobile platforms.
Sign up for Tiggr and build your mobile app today.
Originally posted on PhoneGap blog: http://phonegap.com/2011/12/15/building-mobile-apps-in-the-cloud-with-tiggr-and-phonegap/
Mapping mobile UI to service is one of the most basic tasks in any mobile app (or a standard Web application). Input data entered by the user is sent to the service (input), the service is invoked, returns data (result) is sent back to the app for displaying results. Tiggr Mobile Apps Builder makes it super easy to map UI to service. Let’s look at an example.
REST service settings:
REST service input parameters:
REST service output parameters:
To open the standard mapping editor, there are two buttons in properties for a service:
Mapping UI to service look like this:
The service input parameters are on the left and are mapped to input components and properties on the right.
Mapping service back to UI for displaying the result looks like this:
The service output parameters are on the left and are mapped to output components and properties on the right.
Now there is even a more visual way to do the same. There is a new Data Mapping tab in the main editor, clicking the tab will open a visual data mapping editor:
That’s a pretty cool way to do mobile UI to REST service mapping.
Slides from my talk at AppsWorld conference in London (Nov 29-30) on building mobile apps in the cloud with Tiggr.