Introduction to Universal Micro Apps (aka Zapp Templates)


Building a ZappTM requires you to create a workflow and mobile user experience that is both simple and intuitive for your users. Starting from a blank page may be challenging if you are not familiar with design best practices for mobile app development.

In addition, you may also want to configure push notifications, enable Cards, add event tracking, and generally optimize your Zapp for performance and adoption, which requires additional steps.

That’s where our Zapp templates or Universal Micro Apps come in. Based on our extensive knowledge of mobile app design and the multitude of use cases we’ve encountered over the years, we are able to offer you a place to start.


What are Universal Micro Apps (Zapp Templates)?


Universal Micro Apps are fully designed and configured Zapps that are not connected to any backend system. Each micro app contains a collection of mobile pages that define a specific workflow. In addition, some micro apps are pre-configured with push notification for any new incoming requests, event tracking on certain buttons in the Zapp app, page caching that allows direct access to and immediate interaction with the first page and additional performance optimizations behind the scenes.


Each page in the Zapp contains a set of virtual mobile controls that are not yet attached to any web controls. Each Zapp template offers a fully developed user experience, layout and style inspiration for a specific workflow.


When a specific template is selected, the entire mobile experience is available while the colors of the Zapp are inherited from the Org brand colors.


Which Micro Apps are available?


The 26 templates that are currently available are divided into Approvals, HR, Lookup, Field Services, and Sales use cases:



  • Expense Approvals 
  • Invoice Approvals
  • Requisition Approvals
  • PO Approvals
  • Time Off Approvals
  • Basic Approvals (for additional approvals-related use cases)




  • Manage Time Off (to enable employees to manage previously submitted PTO requests)
  • Request Time Off (for submitting new PTO requests)
  • My Pay (for viewing pay statement)
  • Corporate Directory
  • My Profile





  • Corporate Directory
  • Product Search
  • Customer Search
  • Basic Search (for all other lookup-related use cases)



Field Services

  • Product Search
  • Customer Search
  • Create Field Report (e.g. incident, meeting, maintenance task, etc.)
  • Update Field Report
  • Submit a Request (e.g. appointment, delivery, support, etc.)
  • Submit a Multi-Step Request (divides the request process into several steps)




  • Log an Activity
  • Create a Contact
  • My Contacts
  • Create an Account
  • My Accounts
  • Create an Opportunity
  • My Opportunities
  • Sales Performance




If your use-case is not related to any of the above, you can still create a new Zapp from scratch. Simply select the Blank option. Please see the Available Zapp Templates article for a more detailed overview of each template.


What does each Micro App include?


Universal Micro Apps are fully developed mobile Zapps that merely require attachment to a web application. Each micro app includes a set of pages with a set of mobile controls that describe the selected use case. In addition, where applicable, enhanced functionality is also built into each micro app including push notifications, Cards, and event tracking.


Let’s analyze one of the existing micro apps. For example, Invoice Approvals.


This micro app includes 7 pages.


Page one is the login page that includes the title of the Zapp, two text fields for username and password and a Sign In button.



The next page, includes a table of all the pending invoice approvals. Each table row contains 4 cells for the invoice name, amount, owner and date. This is simply the recommended information that should be in the table but can be easily changed based on actual content in the web application.


The table is set up with a full row tap action to allow the user to easily drill into the details of each row by tapping anywhere on the row.




The third page is the invoice approval request details page. It contains details about the invoice report submitted for approval as well as two buttons to approve or reject the request. Note that the page includes three tabs for the details, line items and history of approvers.

As in the table page, the information on the page is a simply a recommendation and can be easily edited, removed or added to.


On this page, event tracking is enabled for the Approve and Reject buttons.



An attachments page is also included and is accessed via the paperclip icon on the invoice approval request details page. It consists of a table with two values: attachment name and attachment description. The user can open the attachment by tapping anywhere on the row.



Next are two pages related to the Accept and Reject buttons. The Accept page provides the user with confirmation that the invoice was successfully approved.



For the page relating to the Reject button, the user can enter the reason for rejection before completing the task.



Lastly, an error page is provided to capture edge cases where an acceptance or rejection may not go through.




Note: The data in each page of the universal micro apps is simply a suggestion to provide inspiration to the Zapp builder and can be easily replaced with actual content from the web application.

For more information on templates for creating Zapp micro apps, please see the following articles:



Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.