Brief Overview

The new WalkMe Mobile is a complete rebuild of our mobile product designed for enterprise scale, stability, and growth. It represents a significant renewed investment in mobile as a core strategic product within the WalkMe platform.

The new WalkMe Mobile brings mobile in line with the broader WalkMe ecosystem, delivering a unified experience across web, desktop, and mobile. It introduces enterprise-grade management capabilities, scalable content creation, and deeper analytics — all built on a modern architecture designed to support how our customers actually work today.

Key Highlights

• Admin Center support for centralized user access and permissions management
• Mobile system creation with support for multiple environments (Production, Test, etc)

• Robust builder experience within the Content Manager app 
• Drag-and-drop Smart Walk-Thru steps, copy-paste functionality, and reusable templates
• Upgraded rule engine with AND/OR operators

• Mobile data now surfaces in WalkMe Insights in System Overview dashboards 

How It Works

Compatibility

Before planning your migration, please review the current compatibility requirements for the new WalkMe Mobile SDK.

Supported app types

At launch, the new WalkMe Mobile SDK supports native iOS and Android apps only. Support for hybrid and plugin frameworks will be rolled out on an ongoing basis throughout the remainder of 2026, including:

• Flutter
• React Native
• Cordova
• Capacitor
• .NET MAUI

If your app is built on one of these frameworks, we recommend staying on the legacy WalkMe Mobile product for now and monitoring our release communications for framework support announcements as they become available.

What this means for your existing implementation

Because the new WalkMe Mobile is built on a completely different SDK, architecture, and database, legacy mobile content, settings, and analytics are not compatible with the new product. Specifically:

• Content created in the legacy product cannot be migrated to the new product
• Settings, segmentation, autoplay rules, folders, and other configurations do not carry over
• Historical analytics data remains in the legacy product and will not transfer

Recommended next steps

To prepare for the transition, we recommend the following approach:

1. Confirm compatibility. Verify that your app meets the platform requirements above. If you're using a hybrid framework, plan your timeline around the upcoming framework support rollout.
2. Install the new WalkMe Mobile SDK in a new app instance within a test environment. This allows your team to explore the new product without impacting your production legacy implementation.
3. Familiarize your team with the new builder experience, including the Content Manager, visual designer, and updated rule engine.
4. Begin recreating your existing legacy content in the new product as a practice exercise. This will help you identify which flows are highest priority and surface any questions early.
5. Plan your full migration timeline with the Spring '27 EOL in mind. We recommend completing migration well before May 2027 to allow time for testing and rollout.

Learn more

For detailed guidance on getting started with the new WalkMe Mobile, please visit the following resources:

Mobile in Console

Mobile in Console: Content Manager

Mobile in Console: Admin Center

Mobile in Console: Power Mode