This demo creates a very simple workflow form that allows mobile users on iPad or Android to “send” an InfoPath form back and forth to each other with changed content. The reason “send” is in quotes? Nothing really moves from one user to the other — it’s not like an email attachment. The form always resides on SharePoint, and what changes is who can see it to check it out, download it and fill it. If it’s not assigned to you, you don’t see it — and that’s the core functionality of mobile workflow forms.

Requirements

Step 1. Use InfoPath to create the form

If you are familiar with InfoPath, this may be the simplest form you ever used. It just has three text boxes bound to three simple fields. Nothing special here.

Start with the simplest InfoPath form ever

You can download the Hello World form here. This form needs to be set to full trust, published to a SharePoint form library with all three fields promoted, and then it needs to be set to submit to that same library. This is all standard Microsoft procedure, nothing Formotus-specific yet. In InfoPath 2010:

1. Click File | Form Options | Security and Trust | unmark Automatically determine… | Full Trust | Sign this form template | OK
   
2. Click File | Publish | SharePoint Server
3. Enter the URL of the SharePoint site where you want to publish the form template, and enter credentials
4. Choose to create a Form Library, then New form library, and name the library Hello World
5. Use the Add button in the Publishing Wizard to promote each of the three fields as SharePoint columns
   

   Promote all three fields when publishing to SharePoint

    

6. Complete the wizard and open the SharePoint form library for future use.
7. Click File | Info | Submit Form | To SharePoint Library
8. Paste in the URL of your Hello World SharePoint Library
9. To give each submission a unique filename, click Fx and enter now() in the formula area. Complete the wizard.
10. Select the Submit button control in the form.  In the Properties tab on the ribbon find the Action dropdown on the left and choose  Submit. You can use the Submit Actions button to verify and manage the submit settings now attached to the button.
11. Optional: Set the default value of the From textbox to the function userName() so it will autofill with a Formotus ID

Step 2: Use the Formotus console to deploy the form

Here we’ll use the Formotus console to turn our InfoPath form into a mobile workflow form and deploy it to two mobile users who can be on iOS or Android devices.

1. Log into your Formotus account here  (register for free trial first here if needed)
2. If you don’t already have at least two mobile users, add one. Under Common Tasks click Add Mobile User and fill in the required fields and an easy password.
3. Under Common Tasks click Upload Workflow Form | paste in the URL of your Hello World library | Enter your SharePoint credentials | Click Next
4. On the Workflow Forms Settings page, use two dropdowns to select the appropriate fields in the form:
   Create a second-line memo in the job list = Memo
   Show only jobs assigned to the user = AssignedTo
   (There may be extra characters inserted in the field names by SharePoint; not to worry)
   

   Only two settings are needed for this workflow form

5. Disregard the other filters on this page. We’ll explain how to use “Show only active jobs” and “Show only jobs assigned to a certain role or task”  in a future post.
6. Click Upload | Publish | Select both User 1 and User 2| Deploy | OK
7. Click Applications and see the form deployed as an application
   

   Hello World form deployed as a workflow application

    

Step 3: Use SharePoint to initiate a workflow

A workflow job on the mobile device is created when you add an InfoPath form instance to your SharePoint library. We’ll use InfoPath to add the first workflow job.

1. In your Hello World SharePoint form library, click Add Document
2. Accept security warnings until the form opens in InfoPath
   Note: If you get a security error related to UserName,  you may need to adjust your Internet Explorer security settings. For this and related issues, see Dealing with InfoPath trust and security issues.
3. Enter the Formotus ID (email)  of one of your mobile users in the To field.
4. In the Memo field enter “Let’s get this workflow going!”
5. Optional: Enter something in the From field
6. Submit the form
7. Verify the submitted instance now appears in your SharePoint library
   

   Add a form in SharePoint assigned to a mobile user ID (click to enlarge)

Step 4: Use the workflow form on a mobile device or two

Here comes the payoff. Let’s assume you have two different mobile users on different devices: User 1 is the user you assigned the job to in Step 3, and User 2 is your other mobile user. (If you only have one device, play along by logging out as one user and logging in as the other user, as required.)

1. Log in as user1 on a mobile device (this one is an Android phone)
   

   The app is pushed to User 1 on an Android

2. Tap on Hello World to download and install it
   

   The installed app shows 1 job waiting on SharePoint

3. Tap on Hello World again to open the job list
   

   The memo field shows right in the job list

4. Tap the job to open the form. Change the To field to your User 2 ID, and change the Memo field to “Over to you, user two!”
   

   User 1 changes the To and Memo fields, and submits the form

5. Submit the form. Because it is no longer assigned to User 1, you will no longer be able to see the job.
6. Log in to Forms Central with your User 2 ID. Tap to install the form, open the job list, and open the form. Notice you see the data entered by User 1 (but the From field auto-fills with User 2 ID)
7. Tap Forms to return to the job list. Notice you have now grabbed (downloaded) the form so you can fill it out any time, even if not connected.
   

   User 2 grabs the form on iPad with changes made by User 1 on Android

Your Formotus mobile users can pass this form around to each other as much as they want. There can be as many different users as your subscription supports, and for ease of use you’d probably want to put the users in a drop-down list for easy selection.

This form doesn’t do very much, but we hope it gives you plenty of ideas about the possibilities for using a workflow like this in your own mobility solutions.

Formotus released a new version of its mobile business application platform with enhanced SharePoint integration and new mobile workflow capabilities. The growing ubiquity of SharePoint makes it an ideal anchor-point for mobile workflow and dispatch software on iPad, iPhone, and Android tablets and smartphones.

Formotus makes it possible for organizations to create and deploy custom mobile business applications built around Microsoft Office InfoPath forms. The new feature set announced today enables companies to implement flexible collaboration frameworks with robust forms that can be routed and shared among mobile users in a wide variety of ways. Formotus mobile workflow forms require no SharePoint modifications and work with any version including on-premises, hosted, and Office 365 SharePoint Online.

All Kinds of Collaboration Supported

The new mobile workflow forms announced today will open up a whole new range of possibilities by supporting scenarios such as these:

• Process Workflow. Complex multi-step workflows can be defined around a company’s business processes. A request form, for example, might be routed to various people for approval, completion, verification, and archiving.
• Social Collaboration. Flexible workflows can be created that empower mobile users to drive the success of a project. Jobs can be assigned and reassigned to individuals or groups, or each mobile user can choose which job to grab next – and SharePoint check-out protocols prevent two users from grabbing the same job.
• Field Dispatch. The essence of dispatch is the need to let a mobile workforce know where to go, when to go, and what to do there. Workflow forms can be designed so that a dispatcher enters that information in a form first, then assigns it to someone else to do the job and complete the form with data collected at the job site.

Mobile Workers Shielded from SharePoint Complexity

The experience for the user of Formotus mobile workflows is unlike that of using SharePoint in a browser. The Formotus mobile user doesn’t have to deal with the sometimes confusing concepts of sites, sub-sites, lists, libraries or views. And there is no searching or site navigation required, because Formotus mobile users simply grab jobs assigned to them with no need to figure out where online that information resides.

A mobile workflow experience built on SharePoint

“SharePoint is becoming ubiquitous in all kinds of organizations,” according to Formotus CEO Adriana Neagu, “and we leverage SharePoint data connections in our mobile apps. But we’re not porting the SharePoint experience to mobile, we’re offering a whole new task-oriented mobile experience that is easier, smarter, more beautiful, more powerful.  The fact is, a person using our platform on an iPad or Android tablet,  won’t be able to tell that there is any SharePoint behind the workflow.”

Formotus Mobile Workflows Are Not SharePoint Workflows

Formotus workflows are not dependent upon SharePoint workflows but are entirely complementary. In fact, Formotus mobile workflows do not involve any SharePoint-side actions at all and are implemented  entirely on the device by filtering the list of items in the library, much like a SharePoint view.

Under the hood the Formotus mobile workflow app is filtering for assigned items in a SharePoint library, and checking InfoPath forms out and then back into that SharePoint library.  For the mobile user, the experience is simply: grab their jobs, complete each job form and submit it when completed—just as they have done with paper and clipboard in the past.

About Formotus

Founded in 2005, Formotus invented the leading technology platform for creating custom mobile business forms that connect tablets and smartphones to SharePoint. Without writing a single line of code, companies can deploy custom mobile solutions for field service, inspections, dispatch, delivery, health care, and more. Formotus offers rich native applications that work well offline for data collection – including signature, photo and GPS capture – and connect online to live business data. Users can design cross-platform mobile applications once in InfoPath, and deploy them anywhere from the cloud as XML-based Formotus form applications.

Formotus is building a worldwide ecosystem of partners who can help our customers with training, support, hosting and consulting services around InfoPath form design, SharePoint implementation, business process management, and more. Learn more about becoming a Formotus partner.

Configure SharePoint 2010 to receive incoming email

Note: SharePoint Online (Office 365) does not support email submit.

1. If you need to configure Central Admin to enable libraries to receive email, find instructions here.
2. Publish your InfoPath form to a SharePoint library.
3. Open the library where the form is published
4. Click Library Settingson the Library tab
5. Under Communications, click Incoming e-mail settings
   
6. Click Yes to allow the library to receive email, enter an email address to use, and click Accept e-mail messages from any sender
   
7.  Copy the complete email address somewhere for future use and click OK.

Configure InfoPath to submit to SharePoint’s email address

1.  Open the InfoPath form template in Design mode.
2. Click File | Info | Submit Form under Submit Options | To Email
3. In the To field, enter the complete SharePoint incoming email address
4. Recommended: Add a Submit button to the form.
5. Finish the wizard, save and publish the form.

Deploy as a Formotus mobile form

Now you can upload the InfoPath form to your Formotus account from SharePoint and deploy it to mobile users. When they submit the form from a mobile device, the form will attach to an email and end up in the SharePoint library.

Notes:

• The form must be uploaded to Formotus from the SharePoint library where it submits.
• The From address will not be retained by SharePoint.
• Only the InfoPath form will be saved in SharePoint, no other attachments.
• For added security you can have the form submit to a second email address that will forward it to the actual address

Forms on Fire, a Formotus authorized training and consulting partner, recently announced availability of their new introductory class “Formotus Essentials.” The online class runs two and a half hours and for the time being is offered at no charge.

This class is intended for new users of the Formotus mobile business platform who may have little or no familiarity with using Microsoft Office InfoPath. People using Formotus free trial accounts are encouraged to attend.

Learn how to:

• Create a Formotus Trial account
• Create an InfoPath form
• Deploy an InfoPath form to Formotus and your mobile users
• Manage your Formotus Cloud Console
• Learn mobile form best practices and use the latest tricks and shortcuts for creating mobile forms for Formotus
• Blow your boss away with KNOWLEDGE and SKILLS!

Register Now for the Next Class

[Updated March 31, 2012 with new screenshots]

Formotus forms are already a powerful platform that lets you create mobile applications without coding, deploy one design across platforms, work offline on mobile devices, connect directly to your data storage (Formotus never hosts your data), and include photos and signatures in your forms.

With our new advanced workflow and collaboration forms a whole new range of possibilities opens up. Whether you need to dispatch an inspector or technician to a job site,  assign a patient to a home health care provider, or get multiple approval signatures on a form,  you’ll be able to control all kinds of mobile business processes on iPads and Android tablets.

Tell me what a business can do with these new forms

Tell me how these new forms work with InfoPath and SharePoint

Show me screenshots

Tell me about the beta requirements

Put me on the list!

The following InfoPath template parts are provided free for your convenience to enable handy mobile-oriented functions within your forms.  They are tested and known to work on the Formotus platform, but they may also prove useful in browser-based forms or on laptops running InfoPath.

For installation instructions and additional templates that only work with Formotus Forms Central (camera, ink, annotation, location and device info), see this article in our knowledgebase.

Dial Control
FormotusDialControl.xtp
Include a phone number in a form that the mobile user can dial with one tap, assuming the device has telephone functionality.

Map Address Control
FormotusMapAddressControl.xtp
Use a hyperlink to open a Google map showing an address in the form. A similar link could point to Bing or Mapquest if you prefer.

Directions Control
FormotusDirectionsControl.xtp
Use a hyperlink to open a Google map showing directions between two addresses in the form.

Keypad Control
FormotusKeypadControl.xtp
Include an easy way for users to enter numbers in a form by using large buttons in the form as a keypad.

Note: The keypad contents may need to be cut and pasted outside the template part section before the keypad will work correctly. The empty section can then be deleted.

We’re getting ready to roll out a new feature on our mobile application platform, and it has me thinking about workflows. The scenario that originally inspired the feature was dispatching mobile workers to job sites.

Simple workflow

Dispatch as a simple workflow

A dispatch scenario is a good example of a simple workflow in which a sequence of tasks take place in a specified order. For example:

• Task 1: Dispatcher submits a form with the address and instructions for a job to be done
• Task 2: Mobile worker completes the work and submits a report
• Task 3: Office worker opens the form to print it, convert it to PDF, or do something else with it.

We know this kind of simple workflow is in great demand, especially in areas such as field services and inspections. It’s a straightforward translation of an existing paper process onto mobile devices. Compared to the paper it’s replacing, this workflow is faster, more efficient and less error prone.

Workflows always grow more complex

The thing about simple workflows is that they tend to grow more complex during implementation. In the real world there are always exceptions to the rules. What if the mobile worker doesn’t have the time or the right equipment to do the job, and it needs to be reassigned to someone else instead? What if while doing the job the worker discovers there is another job that needs to be done by someone else at the same site? What if the form the worker submits is missing some important data and it needs to be returned to him in the field?

In the course of designing the form it is common for a number of such exceptions to be anticipated, and for the workflow to grow more arrows. Pretty soon the simple workflow becomes a complex workflow with conditional branching and alternative routing of the work.Then there are the unanticipated exceptions that arise in the field after the forms have been deployed. This is why deployments need to be iterative, typically starting with simpler workflows and growing more complex to accommodate situations that arise.

Complex structured workflow

Complex workflows, iteratively improved, can be a good solution for mobile business processes. But there are also some alternatives for companies willing to release a little more control to the people working in the field.

Unstructured collaboration frameworks

Inherent in the idea of a ‘workflow’ is the notion that the whole process is automated and controlled by rules. The next step in the process is always determined by the workflow rule.

Contrast this with a purely collaborative framework, such as email, where anyone can send anything to anyone else. In this case the work does flow, but the path it takes is determined entirely by the participants. The designer does not need to account for all the exceptions, because there are no rules or set tasks, just roles and communications.

Unstructured collaboration framework

The underlying assumption of a collaborative process like this is that the person in the field is the one who knows best what needs to happen next. The job of the designer is, in a sense, to stay out of the way of the end user and enable as many opportunities and channels for collaboration as possible.

The problem with an unstructured collaborative framework like this is the risk of chaos. With no built-in rules at all, the work might flow endlessly in circles or stop flowing altogether.

A semi-structured collaboration framework

Collaboration need not be totally chaotic. It’s possible to devise a framework, for example, in which one person or role has a unique status that exerts control over the flow of the work.

Semi-structured collaboration framework

In this case Role A, the manager/dispatcher, has full flexibility to assign tasks to others as needed, while the other roles experience the more structured workflow of receiving and completing assignments.

Collaboration within a workflow

Another possibility is that some parts of a workflow are highly structured while other parts are very flexible. Here’s a workflow with highly structured beginning and end segments, but with an unstructured collaborative space in the middle.

Unstructured collaboration within a structured workflow

As a concrete example of this kind of collaboration-within-workflow scheme, consider the demo we’re working on to show off our new stuff. Our fictional field service company does plumbing, drywall and painting, and those different workers need to be able to pass jobs off to one another as needed. But all that must not begin until the job has been approved, and when the work is done the customer must be invoiced.

Field worker collaboration within back office workflow

Control and Empowerment

Workflow is about tight control and precise specification of tasks to be accomplished in certain orders and time frames according to rules and conditions. Collaboration is about enabling teams to work together flexibly in order to accomplish tasks, even in unforeseen circumstances.

Where’s the happy medium?

The sweet spot will not be the same for every company or situation. It will vary depending on factors such as the level of expertise of the end users and the tilt of of the organizational culture — whether the company leans more toward control and hierarchy or toward trust and empowerment.

The important thing to remember is that there are good alternatives to consider besides workflows strictly controlled by rules, and these alternatives can lead to a more empowering user experience and a more efficient workforce.

-Glen Furnas

The good news is that the Views pane still exists, you just can’t find it in the ribbon. Here’s how to add a Manage Views button to your Quick Launch Bar so you can toggle the Views pane on and off from anywhere:

1. InfoPath 2010 has View tools on the Page Design tab, but no way to show the Views Pane

2. Customize the Quick Access Toolbar and choose More Commands

3 – 6. Select Commands Not in the Ribbon, Views Pane, Add, OK

7. Now you can toggle the Views pane on and off from anywhere in InfoPath. We also like to toggle the Rules and Fields panes there, and to launch Preview.

Everyone knows using paper forms is an outdated, inefficient and costly way to do business. But it’s not easy to find hard data to support calculations of return on investment (ROI) for switching to paperless processes.

Unsubstantiated claims about the cost of paper forms

There are plenty of anecdotal claims, such as this one from 2009:

“Have you heard that it costs $25,000 to fill a filing cabinet and $2,100 per year to maintain it? Did you know that rejecting a document based on poor penmanship, missing information or missing pages costs an average of $75? Or that filling out just 5 pages of forms per day costs an average of $12,000 per year (at $25 per hour or $40,000 salary)?”

But when you try to track down the source of such numbers, they prove elusive. Here’s another one, from 2006:

“Estimations for the costs of paper transactions range from $8,000 to $9,000 from the inception to sunset of paper forms. The cost of paper transactions hover around $35 per transaction, not to mention the specter of human errors that are introduced as data is rekeyed into a database from paper forms.”

Generally these kinds of unsubstantiated claims are made by companies promoting their own paperless solutions. (Full disclosure: we promote our own paperless solution.)

Calculate the cost of paper forms yourself

One mobile forms company has made available an interesting calculator you can use to estimate the costs of paper forms in your own situation — not just in dollars but in trees and pounds of carbon as well. The calculator is attributed to a university institute, and the dollar calculations hinge on estimating how long it takes to key data from a paper form into a computer.

“The primary cost savings comes from not having to reenter paper forms data into a computer system. On average, you can save from $0.51 per page if using offshore contractors to reenter form data, to $1.88 or more if using your own employees.”

The nice thing is that you don’t need to accept this claim, because the factors are all transparent and you can enter your own assumptions into the calculator. But we do wonder how accurately most companies can estimate the key metric at the heart of the calculator: “Average time in minutes to enter the answers to an average form question into a computer system including wasted time”.

At last, a good recent study of the cost of paper forms

the average cost per form is $4.56, but for 20% of respondents the cost per form is $10 or moreAIIM published a whitepaper in 2012 that includes the results of a survey they conducted with 477  of its 64,000 community members. We like it because the survey was conducted by an objective non-profit organization, it includes all the demographics, and it excludes extreme answers and the responses of companies that are too small or have a conflict of interest.

“However, the costs mount dramatically once the forms have been completed by the user, and need to be transported safely, securely and quickly to the start of the appropriate process, wherever that may be, and whether or not it includes a scanning and capture element.

In the AIIM survey mentioned earlier, we asked respondents to estimate how much it costs them, per document or form, in printing, distribution, mailing, collection and sorting, prior to either scanning or paper-based processing. Eliminating 14 responses of over $75 per form (which may well be valid for certain very specialized applications or remote locations), the average cost per form is $4.56. The median (mid-point) is $2.00, but for 20% of respondents the cost per form is $10 or more.”

Sources © AIIM 2012 www.aiim.org and available at aiim.org/research:

• The Paper Free Office – dream or reality?
• Process-Critical Forms and the Mobile Workforce – making the digital savings

(Updated May 7, 2012)

General app development costs

Forrester Research took an early stab at estimating the cost of developing an iPhone app, and said most apps take at least six months of full-time work and cost between $20,000 and $150,000 to develop. That’s a pretty wide range, and it’s a pretty old estimate from 2009.

A 2010 article at padgadget.com provided a good discussion about creating your own apps, and broke the costs down like this:

For a nice but simple app, the design work will likely take a designer about a week, which will cost you about $6,000. The server side will likely require a developer about 2 weeks of work, or about $12,000. Similarly, the app could be written in about 2 weeks as well, another $12,000. Add $5,000 for project management, hosting fees for a year, debugging, unforeseen delays, and your total budget is around $35,000.

The author continued to point out that a high-end app like a game could easily run over $200,000.

The problem with these and other similar estimates (like these  and these) is that they are generally talking to an audience interested in developing consumer apps to sell in the app stores. It’s not clear how these discussions pertain to the very different kinds of apps that businesses are looking for to facilitate their own business processes using mobile devices.

Business app development costs

Canadian mobile application developer Seregon Solutions offers “The Mobilizer,” a $20,000 fixed-price service to create and deliver custom mobile business apps on three different mobile platforms. Seregon uses the DragonRad  application development environment for its cross-platform development, and it appears in some cases there may be additional annual subscription costs involved.

Another app development company, Propelics, specializes in iPad apps and posted a very informative blog post in December 2011 with a breakdown of iPad app development costs. This is recommended reading on the difference between consumer and enterprise apps. In a nutshell, Propelics describes three levels of complexity in enterprise apps corresponding to three price ranges:

• Simple Enterprise iPad App Development Cost: $50,000 (+/- 20%)
• Medium Enterprise iPad App Development Cost: $100,000 (+/- 20%)
• Complex Enterprise iPad App Development Cost: $150,000 (and up)

Features that bump an app into the $100,000 range include a branded and highly tuned user experience, and integration that leverages your existing enterprise capabilities. For real-time integration, mobile device management (MDM) and mobile application management (MAM) infrastructure, you enter the $150,000+ category.

Web applications in a browser are an alternative to native app development.  Comentum, a company that does Web application development, has published an analysis of different types of Web development companies. Projects using “Moderate Class” development companies are said to range in cost from $7,000 to $150,000, putting Web application development in a similar range to native app development.

Continuing costs after app development

It would be a mistake to think of app design and development as a one-time cost. As Art Wittmann wrote recently in Information Week:

The short-term investment in creating those first pristine apps is likely to be the tip of the iceberg in terms of people and capital costs. Whether you're using internal teams for development or contracting with coding houses (a practice that brings its own set of challenges), you'll need to make a sober assessment of the short- and long-term costs of supporting the practice.

An app developed today will need to be updated in the future for changing business processes and for operating system updates. It will need to be ported to any new platforms you want to support. According to MGI Research, most mobile apps will experience at least four major update cycles stemming from operating system and device updates in the 2012-2014 time frame.

Moreover, there are ongoing costs associated with distributing apps and updates to employees. Anyone planning to develop multiple business apps might want to engage a mobile application management vendor such as App47 or MAAS360.

Also, if your strategy for cross-platform app development is to use a framework such as DragonRad, be sure to include any ongoing subscription costs in your calculation.

What about mobile enterprise application platform (MEAP) costs?

A number of companies offer middleware server platforms to deliver mobile application solutions with more or less programming involved. Some of the prominent MEAP vendors include Antenna Software, IBM Worklight, Kony Solutions, Verivo (formerly Pyxis Mobile) and Sybase Unwired Platform.

Pricing is not transparent for most of these solutions, but one mobile analyst  Kevin Benedict recently wrote:

Upfront, getting-started costs are important to understand. I know some mobile platform vendors that want to charge you hundreds of thousands of dollars worth of platform before there are any mobile apps. To me this is difficult to swallow. There is no ROI on a mobile platform without apps. I would rather pay for the platform as part of an app. I want to pay when my ROI starts.

An alternative to app development: Subscription software services

App development and management costs can be avoided by companies whose needs can be met instead with software-as-a-service (SaaS) offerings. For example, companies needing mobile customer relationship management (CRM) solutions can subscribe to Salesforce.com or soon Microsoft Dynamics and pay a monthly fee per user rather than developing custom apps. Salesforce starts at $65 per user per month, and Dynamics is expected to start at $30 per user per month.

A Formotus form running on iPad

Formotus pricing is also by subscription, starting at $45 per user per month and sliding down with volume. This price is all inclusive for as many custom business apps as you want to create, deploy, update and use:

• No activation or sign up fees
• No additional charges to create, deploy and use as many forms as you want
• No extra cost for as many administrator seats in the Formotus cloud console as you need
• No additional Formotus software, server or maintenance charges of any kind

For customers who use our platform to create custom mobile solutions without coding, this is the only cost. When customers choose to have Formotus or one of our partners create the solution, that typically is just a small fraction of the cost of coded app development.

Formotus custom business forms work across platforms, are optimized for offline use, and are fully controlled from the cloud. The capabilities of these forms include leveraging existing backend systems, creating highly tuned user interfaces, and managing the complete life cycle of each Formotus form — eliminating the costs of  MAM and MDM. Employees can use Formotus on their own BYOD devices, and the employer stays in full control of updating or removing the apps remotely.

Learn more about the Formotus mobile business platform and get started on a free 30-day trial