A little while back I made a post on what it was like to develop with AppMobi. In general the post was very favorable to AppMobi and the wonderful job they have done in making mobile development incredibly simply. With this post I want to deep dive into programming some of the more device specific functionalities.
When I started using AppMobi about 6 months ago interacting with device specific design elements was rather difficult. These were items such as the pull down drawer, the swiping actions, the formatted tables, etc… A few months ago however AppMobi helped to really change the game of this work by releasing the JQ Mobile package which can be downloaded at: http://jqmobi.com/. In the next few paragraphs I want to highlight some of the benefits of the great open source work.
The first functionality I wanted to interface with was basic swiping. Using the “jq.swipe” function you can interact with a swipe event by registering it to a string or element within your application. You are able to set the swipe direction as well as how many pixels need to be moved in order for the event to fire. The problems I ran into related to the test cycle. You could not really test this using the AppMobi virtualizer so you needed to perform a full test cycle out to your mobile device in order to truly test your code. It was slow to test – but it was not that big of deal in all honesty.
The second bit of functionality I wanted to interface with was the stylized block tables that are found on the mobile devices. To do this you can interact with the “jq.alphaTable” function. This function has very few customizations to it – simply pass in any custom styles as well as a prefix that you want to include. Testing the functionality was easy as you can use your mouse to interact on the behalf of a users finger.
The third piece of functionality was the pull down drawer style. This function is called “jq.drawer”. In essence you set up a container with the content you want inside the drawer – then this function simply adds the style elements and rules to interact properly with the device.
Above we have three different unique pieces of functionality that are specific to mobile devices. The JQ Mobile framework cuts the pain and difficult process out of interacting with specific functions for each os. Although the project is very young (a few months old as of this writing) it simplifies greatly the coding process for unique device destinations. Hopefully in a later post I can spend some time discussing other pieces of functionality.