Home > Articles > Programming > General Programming/Other Languages

Training Users for Cheap: Offering Simple Guided Tours in Your Mobile Interfaces

Avoid training and support overhead by adding simple tours to your apps. This write-up explores a simple boilerplate solution that’s easy to implement.
Like this article? We recommend

Not every app’s functionality is as obvious to users as developers would like. As a consequence, your UI may both incur support costs and garner unwelcome reviews when confused users cannot figure it out.

Creating training materials for your app can prove as big a development challenge as the app itself. For many developers, perfect is the enemy of good. They’re so focused on creating the best possible training system that they overlook solutions that are merely good enough. A simple but reusable training harness enables you to minimize costs and get started with training.

Custom Tour System

I started building my suite of tutorial classes a few years ago. You see a skeletal example in Figure 1. On the iPad, my tours consist of a series of popovers, which optionally point to items they describe. On the iPhone, a stack of view controllers replaces the popovers. The same classes and set-up power tours on both systems.

Figure 1 This boilerplate guided tour contains text, image, and navigation elements. When presented on the iPhone, the view controller shown in this popover is pushed onto the navigation stack

Over time, my tour classes have grown to accommodate built-in elements like UIKit’s new support for HTML-based attributed strings as well as custom elements like animated gifs. But when I first started, I had a list of non-negotiable requirements.

  • My tours needed to keep track of a user’s training through the defaults system. Each app could check defaults to determine if training had finished. I vary how each app uses this knowledge. Some apps present the tour at launch until complete. Others allow users to skip out, not presenting again unless specifically requested by the user. This default item enables each app to implement its own system.
  • The tours had to run platform agnostically. Because popovers are essentially view controller containers, this was quite easy to accomplish. On phone devices, I push controllers. On tablets, I embed them. Otherwise the programmatically generated controllers are identical.
  • My scripting had to be simple, centralized, and flexible. I wanted to ensure that at any time I could add new tour stages or re-order the ones I already had, whether during development or after deployment for app updates.
  • Each stage had to support a localizable headline, body text, next button, and an image. Although I generally deploy only to English, I wanted the system to be international-ready, so these elements had to be settable from the scripting method. My latest system adds iOS 7 HTML support to provide further lightweight customizations such as bolding and italics. My image can now be an animated GIF, which is a great resource for show-don’t-tell tutorials.
  • Users had to track where they were with respect to the tour so that they wouldn’t feel trapped. That’s why both the iPhone and iPad versions offer the page indicator control. At any time, users can tell how far they’ve progressed. Because I keep my tours short, I do not allow many “opt out” points. You should think about where in your training a user should be allowed to leave and adjust your tutorials accordingly.
  • The tour had to take charge of the interface, and users would not be allowed to perform normal tasks until they’d left the tour. Establishing a delegate protocol for a controller that could disable and enable its own interface was essential. My delegates implement one method, setInterfaceEnabled:, which allows the calling view controller to prepare itself for the training and recover after.

Even satisfying these bullet points, the system I eventually settled on has limitations. It assumes it describes a single main interface. The iPhone presentation is a stack of view controller presentations that cover the interface it describes. (This was the original motivation for why images had to be a part of the tour.) The tour contains no deliberate interactivity beyond page-to-page navigation.

These limitations, however, enabled me to create an exceedingly simple harness. What follows is an example of how little scripting it takes to build a tour.

- (void) setupTour
    // Create a tour
    tour = [[GuidedTour alloc] init];
    tour.delegate = self;

    // Build stages
    GuidedTourStage *stage;
    // This stage (see Figure 1) has an image
    stage = [[GuidedTourStage alloc] init];
    stage.header = @"Welcome";
    stage.body = @"Intro Text";
    stage.image = [UIImage imageNamed:@"flowers"];
    [tour addStage:stage];
    // This one uses HTML
    stage = [[GuidedTourStage alloc] init];
    stage.header = @"Stage 1";
    stage.body = @"Text that talks about <i>Stage 1</i> \
        in an interesting fashion";
    stage.desiredView = button; // Location hint for iPad
    [tour addStage:stage];
    // This one uses an animated GIF
    stage = [[GuidedTourStage alloc] init];
    stage.header = @"Thank you!";
    stage.gifPath = [[NSBundle mainBundle] 
        pathForResource:@"sample" ofType:@"gif"];
    stage.nextButtonText = @"Done";
    [tour addStage:stage];

The classes that power this tour are at my Github repository. They consist of a stage class (a data structure describing the stage properties), a tour view controller (it uses these properties to populate a view), and the tour itself, which is little more than a smart array. Although minimal, they provide a jumping-off point for anyone who wants to build a customizable tour system.

Designing Tours

A successful tour should be highly focused. Always respect your user’s time and attention. Determine what features are the most pertinent to getting started and limit your initial tour to those items. You can always provide additional tours for more experienced users, and your training should not overwhelm your product. A user is less likely to quit from an app with 4 or 5 intro frames than one requiring 17 or 20 steps. Never forget that your interface always contains one more button than you design for. When your users feel trapped or bored, they'll press the Home button instead of tapping Next.

Keep your language light and tight. Use style hints to punch your meaning. In Figure 2, this tour stage uses HTML to pop its example text (monospaced) and related trivia (italics). Admittedly, this example is wordy due to the nature of the app.

Figure 2 Always assume your users have a limited attention span. Get to the point as quickly as possible

Don’t ignore your headers. They offer the best way to get a single idea across before you expand that idea in your text and supporting media. In fact, design your headers to match the key points you need your users to understand. Think of them as the elevator pitches of your training materials.

If you can, substitute pictures for words, especially pictures that move, when teaching an interaction. There are some terrific finger-shaped cursors available. I use PhoneFinger, which is available as an open source repo. You'll find others with a quick Internet search.

You may also want to highlight touches using a kit like TouchKit, which I wrote about on InformIT a few years ago. Use the simulator or an AirPlay destination like Reflector to move your app to a desktop computer and QuickTime to capture the screen recording.

There’s a great discussion on converting movies to GIFs at this gist by Alex Dergachev. If you decide to go the gifsicle route he recommends, you may need to install Homebrew and brew cast. Be sure to read the comments on that gist as there are lots of great tips and links there as well.

Figure 3 Custom finger cursors highlight interaction on screen shots and in videos. Where possible, use a wide range of finger styles for audience inclusiveness

If your app is complicated, end your tour with a callout to your help system. Tell your user how to search for and find answers – through built-in or online manuals, video resources, and so on. Incidentally, this is probably not where you want to include links to your ticketing system as your user has now spent a grand total of a minute or so invested in your app.

Wrap Up

Guided tours go a long way toward getting your users up to speed with your app. Even limited systems like the one discussed in this write-up help users better understand and invest in your product. Yes, you’ll have to schedule in time to design, script, and implement a tour, but you’ll be setting your priorities in the right place for the long term.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020