Get Moving with Mobile Apps Using Cordova, Part 3

Development Tools / Utilities
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

Finally, add a database backend to your mobile app.


In parts 1 and 2 of this series, we built a simple to-do list application. Now we come to the final step in the process: adding the backend database. Previously, in part 2, we could add and delete the to-do list items in the Document Object Model (DOM), but they weren't saved anywhere and therefore would not persist between instances of the application.


The first thing I should explain is that in this article we're going to cover only the code for the AJAX interface in the mobile application. The actual backend server/service you create can be any number of types of application (PHP, Ruby on Rails, Node.js, etc.), and there are many examples and tutorials available for learning to build them. That said, here's a link to the Ruby on Rails github repository for the service that I built for this article. And here's a link to the Cordova app.  


So without further adieu…


HTML Changes

One of the nice things about the UI we've built is that it's easily modified to work with a persisted data source. Only one line of code needs to be changed in the HTML. We're just going to remove our placeholder. If we want or need a placeholder, then we can deal with that from the server side. So the code will look as shown below:


       <div data-role="content">

           <ul id="item-list" data-role="listview" data-icon="delete">




JQuery and JavaScript Changes

As you may have expected, most of our changes are going to be in the JavaScript. The first thing we're going to do is remove the code that was used to remove the placeholder item. So the addListItem function will be as shown below:


   addListItem: function() {

     if ($("#item").val() != "") {

         new_item = $("<li><a href='#' class='ui-btn ui-btn-icon-right ui-icon-delete'>"+$("#item").val()+"</a></li>");

         $(new_item).click( function(e) {





       window.location.href = "#mainpage"




We 're going to need several AJAX operations to make our application function correctly. We'll need 1) a function to retrieve all the existing rows, 2) a function to add a new row, and 3) a function to delete an existing row. We'll start with the function to retrieve all existing rows. Add the following code below the addListItem function:


   fetchItemsList: function() {

     items = [];


       type: "GET",

       url: "http://localhost:3000/items.json",

       success: function(data) {

         for( var i=0; i < data.length; i++) {

           app.insertNewItem(data[i].description, data[i].id);




     return items;



The code above is using the JQuery .ajax method to simplify the AJAX call to the server. JQuery documentation can be found at The gist of what is happening in this code is that we're making a GET request to the server at http://localhost:3000 for items.json. The localhost server is just my laptop, and 3000 is the port I have my Ruby on Rails server listening on. If the request completes successfully, then whatever is returned from the server will be placed in the "data" parameter passed to the function we define for "success:".


So what happens on the server side, one may ask? Well, in the case of the backend I'm using, the server retrieves the rows from my "todo" database and returns them as JSON objects. If you want to see this, you can load the backend server and get it running on your laptop. Then put the URL from the .ajax method into your browser. You should get something that looks like this:


[{"id":28,"description":"Grocery shopping","created_at":"2015-09-17T20:08:56.944Z","updated_at":"2015-09-17T20:08:56.944Z"},{"id":29,"description":"Feed cat","created_at":"2015-09-17T20:08:56.955Z","updated_at":"2015-09-17T20:08:56.955Z"},{"id":30,"description":"Clean house","created_at":"2015-09-17T20:08:56.968Z","updated_at":"2015-09-17T20:08:56.968Z"},{"id":31,"description":"Wash the car","created_at":"2015-09-17T20:08:56.975Z","updated_at":"2015-09-17T20:08:56.975Z"},{"id":32,"description":"Write Cordova article","created_at":"2015-09-17T20:08:56.977Z","updated_at":"2015-09-17T20:08:56.977Z"},{"id":33,"description":"Do dishes","created_at":"2015-09-17T20:08:56.978Z","updated_at":"2015-09-17T20:08:56.978Z"}]


This is just the JSON for the rows I loaded for testing purposes. So that's what the "data" parameter will contain. You may have noticed that the function that gets called when the AJAX request completes successfully is calling another function that we haven't written yet: app.insertNewItem.


The reason I did this is that we're going to need to be able to add a new item to our display both when we load the complete list and also when we add a new item to it from the add display. So it's best to separate that processing. Here's the code for the insertNewItem function. It should be added above the fetchItemsList function.


     insertNewItem: function(description, id) {

       if (id == undefined) {


           type: "POST",

           url: "http://localhost:3000/items.json",

           data: { description: description },

           success: function(data) {

             id = data;



           fail: function() {

             alert("add failed!")




       new_item = $("<li id='"+id+"'><a href='#mainpage' class='ui-btn ui-btn-icon-right ui-icon-delete'>"+description+"</a></li>"); function(e) {

        if ( != 0 && != "undefined") {






This function also makes an AJAX request, but in this case it will do that only if the "id" passed to the function is equal to "undefined." That code will make more sense in a moment. In this case, we're making a POST request to the same URL as we used before in the fetchItemsList. This is a Ruby on Rails convention for routing and will trigger the "create" method on the backend server. A new row will be created in the database using the data from the object specified on the "data:" parameter of our $.ajax method. Again the data being passed to and from the server is JSON, so here we're creating a JSON object on the fly that just contains the description of our to-do item. Upon successful return from the server, we will receive the "id" of the added row.


Here's where things get a bit confusing if you're unfamiliar with the asynchronous nature of AJAX. When the server request is made, we know the "id" passed to the function is "undefined" because we're checking that on the way in. So the AJAX request is made to the server, but the JavaScript doesn't wait for a response. It simply keeps going. Therefore, a new item with an "id" equal to "undefined" is added to the DOM in the code following the AJAX request. This is our newly added to-do item. When the server request completes, then we'll have the actual "id" of the added database row. At that point, we want to change the "id" of the item in the DOM to match the actual row id. We'll need that later when we add the delete function. This line from the "success:" function takes care of that for us.




There are some potential for issues with this handling in a production environment, but for demo purposes it's enough.

The only other thing worth mentioning in this code is the event listener we add to the new line item. We're using JQuery to set a listener that will trigger the function we specify (app.deleteItem, which we still need to write) when the user clicks on the line item. The rest of the JavaScript in the insertNewItem function should be clear enough if you worked through the first two articles.


The last part of the add process will be to change the current addListItem function to use our new insertNewItem function. So the new addListItem function is as shown below:


   addListItem: function() {

     if ($("#item").val() != "") {



       window.location.href = "#mainpage"




Notice that in the case of a newly added item we're only passing the description we entered, not passing a parameter for the "id" at all. Thus the "id" will be "undefined" inside the insertNewItem function and it will make the AJAX request as it should.


So now we can fetch the list and add to it. Let's wrap up with the delete function. This is simple enough. We already added the event listener that will trigger the delete function called app.deleteItem. Add the following code after the fetchItemList function.


   deleteItem: function(id) {

     url = "http://localhost:3000/items/"+id+".json"


       type: "POST",

       url: url,

       fail: function() {

         alert("delete failed!")





After you've coded the other two AJAX requests, this one should appear pretty simple. We set the URL using the "id" passed to the function. Make the POST request and check and report if it fails.


One last thing: we need to add the initial (only) call to the fetchItemList function when the app first loads. So change the code in the bindEvents function as shown below.


   bindEvents: function() {

       document.addEventListener('deviceready', this.onDeviceReady, false);




That's it. You now have a fully functioning mobile app. Well, unless you have syntax errors in your code. Since debugging a mobile app can be challenging, let me offer a few tips. If you remove the JQuery mobile UI library and the "viewport" meta-name tag, you can load the index.html in your browser and test it there. If you're using Google Chrome, check out the Developer Tools displays as they are enormously helpful in debugging your JavaScript. Also, liberal use of the JavaScript alert command can be helpful from within the app itself. Just remember to remove them all once you're done debugging.

Jeff Olen

Jeff Olen is a super-spy now but keeps his cover identity intact by working for video game studios on the East Coast. So when he’s not out killing members of ISIS or rescuing refugees, you can find him playing Wolfenstein II or testing the new Fallout 76 releases at his beach house in Costa Rica. In any case, he can’t be reached. You can email his cat at She will pass on your message…if she feels like it.

MC Press books written by Jeff Olen available now on the MC Press Bookstore.

The IBM i Programmer’s Guide to PHP The IBM i Programmer’s Guide to PHP
Get the scoop on how PHP can—and should—be deployed on IBM systems.
List Price $79.95

Now On Sale



Support MC Press Online





  • White Paper: Node.js for Enterprise IBM i Modernization

    SB Profound WP 5539

    If your business is thinking about modernizing your legacy IBM i (also known as AS/400 or iSeries) applications, you will want to read this white paper first!

    Download this paper and learn how Node.js can ensure that you:
    - Modernize on-time and budget - no more lengthy, costly, disruptive app rewrites!
    - Retain your IBM i systems of record
    - Find and hire new development talent
    - Integrate new Node.js applications with your existing RPG, Java, .Net, and PHP apps
    - Extend your IBM i capabilties to include Watson API, Cloud, and Internet of Things

    Read Node.js for Enterprise IBM i Modernization Now!


  • Profound Logic Solution Guide

    SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation.
    Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects.
    The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the companyare not aligned with the current IT environment.

    Get your copy of this important guide today!


  • 2022 IBM i Marketplace Survey Results

    Fortra2022 marks the eighth edition of the IBM i Marketplace Survey Results. Each year, Fortra captures data on how businesses use the IBM i platform and the IT and cybersecurity initiatives it supports.

    Over the years, this survey has become a true industry benchmark, revealing to readers the trends that are shaping and driving the market and providing insight into what the future may bring for this technology.

  • Brunswick bowls a perfect 300 with LANSA!

    FortraBrunswick is the leader in bowling products, services, and industry expertise for the development and renovation of new and existing bowling centers and mixed-use recreation facilities across the entertainment industry. However, the lifeblood of Brunswick’s capital equipment business was running on a 15-year-old software application written in Visual Basic 6 (VB6) with a SQL Server back-end. The application was at the end of its life and needed to be replaced.
    With the help of Visual LANSA, they found an easy-to-use, long-term platform that enabled their team to collaborate, innovate, and integrate with existing systems and databases within a single platform.
    Read the case study to learn how they achieved success and increased the speed of development by 30% with Visual LANSA.


  • Progressive Web Apps: Create a Universal Experience Across All Devices

    LANSAProgressive Web Apps allow you to reach anyone, anywhere, and on any device with a single unified codebase. This means that your applications—regardless of browser, device, or platform—instantly become more reliable and consistent. They are the present and future of application development, and more and more businesses are catching on.
    Download this whitepaper and learn:

    • How PWAs support fast application development and streamline DevOps
    • How to give your business a competitive edge using PWAs
    • What makes progressive web apps so versatile, both online and offline



  • The Power of Coding in a Low-Code Solution

    LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks



  • Why Migrate When You Can Modernize?

    LANSABusiness users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
    In this white paper, you’ll learn how to think of these issues as opportunities rather than problems. We’ll explore motivations to migrate or modernize, their risks and considerations you should be aware of before embarking on a (migration or modernization) project.
    Lastly, we’ll discuss how modernizing IBM i applications with optimized business workflows, integration with other technologies and new mobile and web user interfaces will enable IT – and the business – to experience time-added value and much more.


  • UPDATED: Developer Kit: Making a Business Case for Modernization and Beyond

    Profound Logic Software, Inc.Having trouble getting management approval for modernization projects? The problem may be you're not speaking enough "business" to them.

    This Developer Kit provides you study-backed data and a ready-to-use business case template to help get your very next development project approved!

  • What to Do When Your AS/400 Talent Retires

    FortraIT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators is small.

    This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:

    • Why IBM i skills depletion is a top concern
    • How leading organizations are coping
    • Where automation will make the biggest impact


  • Node.js on IBM i Webinar Series Pt. 2: Setting Up Your Development Tools

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. In Part 2, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Attend this webinar to learn:

    • Different tools to develop Node.js applications on IBM i
    • Debugging Node.js
    • The basics of Git and tools to help those new to it
    • Using as a pre-built development environment



  • Expert Tips for IBM i Security: Beyond the Basics

    SB PowerTech WC GenericIn this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

    Don't miss this chance to take your knowledge of IBM i security beyond the basics.



  • 5 IBM i Security Quick Wins

    SB PowerTech WC GenericIn today’s threat landscape, upper management is laser-focused on cybersecurity. You need to make progress in securing your systems—and make it fast.
    There’s no shortage of actions you could take, but what tactics will actually deliver the results you need? And how can you find a security strategy that fits your budget and time constraints?
    Join top IBM i security expert Robin Tatam as he outlines the five fastest and most impactful changes you can make to strengthen IBM i security this year.
    Your system didn’t become unsecure overnight and you won’t be able to turn it around overnight either. But quick wins are possible with IBM i security, and Robin Tatam will show you how to achieve them.

  • Security Bulletin: Malware Infection Discovered on IBM i Server!

    SB PowerTech WC GenericMalicious programs can bring entire businesses to their knees—and IBM i shops are not immune. It’s critical to grasp the true impact malware can have on IBM i and the network that connects to it. Attend this webinar to gain a thorough understanding of the relationships between:

    • Viruses, native objects, and the integrated file system (IFS)
    • Power Systems and Windows-based viruses and malware
    • PC-based anti-virus scanning versus native IBM i scanning

    There are a number of ways you can minimize your exposure to viruses. IBM i security expert Sandi Moore explains the facts, including how to ensure you're fully protected and compliant with regulations such as PCI.



  • Encryption on IBM i Simplified

    SB PowerTech WC GenericDB2 Field Procedures (FieldProcs) were introduced in IBM i 7.1 and have greatly simplified encryption, often without requiring any application changes. Now you can quickly encrypt sensitive data on the IBM i including PII, PCI, PHI data in your physical files and tables.
    Watch this webinar to learn how you can quickly implement encryption on the IBM i. During the webinar, security expert Robin Tatam will show you how to:

    • Use Field Procedures to automate encryption and decryption
    • Restrict and mask field level access by user or group
    • Meet compliance requirements with effective key management and audit trails


  • Lessons Learned from IBM i Cyber Attacks

    SB PowerTech WC GenericDespite the many options IBM has provided to protect your systems and data, many organizations still struggle to apply appropriate security controls.
    In this webinar, you'll get insight into how the criminals accessed these systems, the fallout from these attacks, and how the incidents could have been avoided by following security best practices.

    • Learn which security gaps cyber criminals love most
    • Find out how other IBM i organizations have fallen victim
    • Get the details on policies and processes you can implement to protect your organization, even when staff works from home

    You will learn the steps you can take to avoid the mistakes made in these examples, as well as other inadequate and misconfigured settings that put businesses at risk.



  • The Power of Coding in a Low-Code Solution

    SB PowerTech WC GenericWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks



  • Node Webinar Series Pt. 1: The World of Node.js on IBM i

    SB Profound WC GenericHave you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.
    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.
    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).
    Watch Now.

  • The Biggest Mistakes in IBM i Security

    SB Profound WC Generic The Biggest Mistakes in IBM i Security
    Here’s the harsh reality: cybersecurity pros have to get their jobs right every single day, while an attacker only has to succeed once to do incredible damage.
    Whether that’s thousands of exposed records, millions of dollars in fines and legal fees, or diminished share value, it’s easy to judge organizations that fall victim. IBM i enjoys an enviable reputation for security, but no system is impervious to mistakes.
    Join this webinar to learn about the biggest errors made when securing a Power Systems server.
    This knowledge is critical for ensuring integrity of your application data and preventing you from becoming the next Equifax. It’s also essential for complying with all formal regulations, including SOX, PCI, GDPR, and HIPAA
    Watch Now.

  • Comply in 5! Well, actually UNDER 5 minutes!!

    SB CYBRA PPL 5382

    TRY the one package that solves all your document design and printing challenges on all your platforms.

    Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product.

    Request your trial now!

  • Backup and Recovery on IBM i: Your Strategy for the Unexpected

    FortraRobot automates the routine tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
    - Simplified backup procedures
    - Easy data encryption
    - Save media management
    - Guided restoration
    - Seamless product integration
    Make sure your data survives when catastrophe hits. Try the Robot Backup and Recovery Solution FREE for 30 days.

  • Manage IBM i Messages by Exception with Robot

    SB HelpSystems SC 5413Managing messages on your IBM i can be more than a full-time job if you have to do it manually. How can you be sure you won’t miss important system events?
    Automate your message center with the Robot Message Management Solution. Key features include:
    - Automated message management
    - Tailored notifications and automatic escalation
    - System-wide control of your IBM i partitions
    - Two-way system notifications from your mobile device
    - Seamless product integration
    Try the Robot Message Management Solution FREE for 30 days.

  • Easiest Way to Save Money? Stop Printing IBM i Reports

    FortraRobot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing.
    Manage your reports with the Robot Report Management Solution. Key features include:

    - Automated report distribution
    - View online without delay
    - Browser interface to make notes
    - Custom retention capabilities
    - Seamless product integration
    Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.

  • Hassle-Free IBM i Operations around the Clock

    SB HelpSystems SC 5413For over 30 years, Robot has been a leader in systems management for IBM i.
    Manage your job schedule with the Robot Job Scheduling Solution. Key features include:
    - Automated batch, interactive, and cross-platform scheduling
    - Event-driven dependency processing
    - Centralized monitoring and reporting
    - Audit log and ready-to-use reports
    - Seamless product integration
    Scale your software, not your staff. Try the Robot Job Scheduling Solution FREE for 30 days.