Welcome to the
WalkMe Help Center
Please log in to continue
Please log in to continue
WalkMe for Mobile Web lets you deliver guidance to users on mobile devices — in Safari, Chrome, or any mobile browser. If a large portion of your users work remotely or in the field, Mobile Web is an important part of your WalkMe implementation.
To access a system in the console:
To access a system in the Admin Center:
All apps available on web are available on mobile web and can be built the same way. Each item created in your mobile web system is separate from items in your web or desktop systems to ensure the best experience for your users.
You can switch between systems in the editor using the systems button. When building content for mobile web, make sure you're on the Mobile Web platform.

Set your web browser to mobile display in dev tools before you start building. This lets you record and preview mobile content and see exactly what your mobile users will see.

Before showing any content, WalkMe checks the device type and screen resolution to decide whether to load the mobile or desktop experience. WalkMe first checks if you're on a mobile device, then checks the screen resolution. When a mobile device is detected, only items built with the mobile emulator are shown. When a desktop browser is detected, WalkMe filters out items built for screen sizes smaller than 600x800 (this resolution can be customized).
WalkMe for Mobile Web uses the same snippet as the desktop version. Since the UI of a mobile environment can differ significantly from desktop, it's recommended to build your WalkMe items specifically for that environment. The mobile emulator lets you select specific devices and preview your environment at the right screen resolution, so you can build with confidence.
To use WalkMe for Mobile Web, you need the standard snippet on your site or a self-hosted setup. If you're currently using an extension, reach out to your Customer Success Manager or WalkMe contact for more information.
Smart Walk-Thrus, launchers, resources, onboarding tasks, and shuttles are all built the same way as on desktop, including segmentation and goals. However, some item designs adjust automatically to suit smaller screen sizes.
For example, the WalkMe Menu appears smaller, balloons scale based on screen resolution, and ShoutOuts have special mobile templates.
There are also a few differences in Smart Walk-Thru triggers. Since mobile users can't use "Click" or "Hover," those triggers are replaced with "Tap" and "Swipe" in the mobile emulator.

You can add a mobile web system to an existing web system.



All rule types are available for Mobile Web, including segmentation by variable, jQuery, and cookie.
"Screen Size" and "Browser Size" rules are especially useful for mobile environments. Use Screen Size to set the minimum desktop size or maximum mobile size, and Browser Size to handle responsive sites.
For example, a Smart Walk-Thru that works for an iPhone 5 in portrait mode may not work for an iPad in landscape mode. In that case, duplicate the Smart Walk-Thru, update only the steps that differ, and segment each version so it's shown only on the appropriate devices.
Start testing Smart Walk-Thrus and other items in preview mode through the editor. Check all items carefully, paying close attention to layout. Testing directly on a mobile device is also strongly recommended — test on the devices most commonly used by your users. To test on a device, publish your items to a test environment first.
Once published to production, Mobile Web data is merged with Desktop Web data and can be reviewed together in Insights.
Re-create an existing Smart Walk-Thru using the mobile emulator to understand how your website differs between desktop and mobile. Test on as many devices as possible to catch potential problem spots.
Then brainstorm with your team to identify which processes your users complete most on mobile — this is often different from desktop. Talk to your users directly to find out which actions they take most from a mobile device.
