# Userpilot: mobile onboarding and the plan it requires Assess Userpilot’s mobile add-on, screen targeting and message frequency before choosing an onboarding plan. Canonical page: https://quillwell.com/guides/software/userpilot/ Updated 2026-10-31 Publisher: Quillwell Guides (https://quillwell.com/guides/about/). Editorial standards: https://quillwell.com/guides/editorial/ ## The short answer - Userpilot may fit teams evaluating native mobile engagement when its add-on and plan requirements work for them. - [Userpilot mobile guidance](https://docs.userpilot.com/in-app-engagement/mobile-content/get-started-with-mobile-content) requires an installed SDK and an annual add-on on Growth or Enterprise. - Userpilot’s pages do not provide a comparable MAU definition or overage delivery rule; request both in the quote. - Compare UserGuiding for its documented quota boundary and Appcues for immediate segment edits. ## Price the mobile setup Start with the app runtime and the people who need access. The mobile purchase involves more than selecting a visual experience. [Userpilot’s mobile guidance](https://docs.userpilot.com/in-app-engagement/mobile-content/get-started-with-mobile-content) requires an installed SDK and an annually purchased add-on on Growth or Enterprise. Starter users must upgrade. Custom mobile-content roles require Enterprise. [Userpilot pricing](https://userpilot.com/pricing/) lists native iOS and Android support and mobile engagement as add-ons. It labels mobile session replay as coming soon. Include the add-on and the required staff access in the quote, then test the integration in your own app. For example, a team on Starter planning a native onboarding flow must account for an upgrade as well as mobile access. The intended author and the developer installing the SDK should both participate in the trial. ## Protect targeting when screens change A screen name can become part of a targeting rule. Treat a change to tracking as a release that needs review, especially when a guide depends on an existing name. [Userpilot’s screen tracking guide](https://docs.userpilot.com/data-events/mobile-screen-tracking/mobile-screen-auto-capture) says automatic capture ignores manual screen calls. Switching modes can change names used for targeting, preventing engagements from triggering or splitting analytics. Map the old names to the new ones before switching. Then test a representative journey and compare its targeting rules with the screen names recorded in analytics. Assign an owner to repair the affected experiences. Keep a record of the intended product action as well as the trigger. If an interface changes, the owner can judge whether the guide still helps users complete the task rather than merely whether it appears. ## Test in-app and push frequency Plan message frequency around the actual channels a user can receive. A single assumption about all messages can conceal a competing experience. [Userpilot’s ordering guidance](https://docs.userpilot.com/in-app-engagement/mobile-content/mobile-content-ordering) separates push controls from the shared in-app throttle for carousels and slideouts. Ordering and throttling can suppress otherwise eligible content. Queue an in-app experience and a push message for the same synthetic user. Record which appears and when, then repeat with another eligible experience. Use the results to set expectations for a launch and assign someone to maintain those settings. ## Get usage terms and trial the journey The quote needs to reflect the audience and the team that will operate the guides. A mobile add-on alone does not answer how the plan handles an unexpected traffic spike. Userpilot’s pages do not provide a comparable MAU definition or overage delivery rule. Request the counting method and the delivery consequence for the proposed plan, together with included seats and their price. Run a representative journey on your actual mobile stack. Record the installation work, the screen name and the product action after the guide. Use the [software trial guide](https://quillwell.com/guides/software-trial/) to compare the same task across candidates. Before switching from another product, inventory its experiences and targeting rules. The vendors do not document portable guide definitions. Inspect a sample export and plan a representative rebuild before removing the original flow. ## How to compare the alternatives Compare alternatives against the constraint that matters most to the team maintaining onboarding. UserGuiding may fit a team that can plan around a stated delivery boundary. [UserGuiding pricing](https://userguiding.com/pricing) says guides stop above quota until it increases or usage falls. Appcues may fit when live segment changes are central to the workflow. [Appcues segment guidance](https://docs.appcues.com/en_US/user-experiences-targeting/segments-overview) says edits immediately affect connected experiences without republishing. The [Appcues alternatives comparison](https://quillwell.com/guides/compare/appcues-alternatives/) compares the delivery decisions. The [product onboarding guide](https://quillwell.com/guides/product-onboarding-software/) provides an identity and exit worksheet. ## Common questions ### Does Userpilot support native mobile engagement? [Userpilot mobile guidance](https://docs.userpilot.com/in-app-engagement/mobile-content/get-started-with-mobile-content) requires an SDK and an annual add-on on Growth or Enterprise. ### Is mobile session replay available? [Userpilot pricing](https://userpilot.com/pricing/) labels mobile session replay as coming soon. ### What happens if we switch mobile screen capture modes? [Userpilot’s screen tracking guide](https://docs.userpilot.com/data-events/mobile-screen-tracking/mobile-screen-auto-capture) says automatic capture ignores manual calls; changed names can affect targeting and analytics. ### What happens above the MAU limit? Userpilot’s pages do not provide an overage delivery rule. Request the terms for your proposed plan. ## Sources and scope We read the linked vendor documentation on October 29, 2026. We have not run these products or tested their support. Plan entitlements and implementation behavior need confirmation for your account. ## Sources 6 vendor pages, checked October 29, 2026 [Userpilot: Get started with mobile content](https://docs.userpilot.com/in-app-engagement/mobile-content/get-started-with-mobile-content) Checked 2026-10-29. Current mobile documentation confirms native support but adds annual add-on and role-management requirements. [Userpilot: Userpilot pricing](https://userpilot.com/pricing/) Checked 2026-10-29. The current table lists native iOS/Android support and mobile engagement as add-ons, while mobile session replay is labelled coming soon. [Userpilot: Mobile Screen Auto Capture](https://docs.userpilot.com/data-events/mobile-screen-tracking/mobile-screen-auto-capture) Checked 2026-10-29. Switching to automatic screen capture changes naming and can break targeting unless old and new screen rules are reconciled. [Userpilot: Mobile content ordering and throttling](https://docs.userpilot.com/in-app-engagement/mobile-content/mobile-content-ordering) Checked 2026-10-29. In-app and push frequency controls are separate; ordering and throttling can suppress otherwise eligible messages. [UserGuiding: UserGuiding pricing](https://userguiding.com/pricing) Checked 2026-10-29. MAUs count unique users active in the previous thirty days. [Appcues: Set up Segments](https://docs.appcues.com/en_US/user-experiences-targeting/segments-overview) Checked 2026-10-29. Segmentation affects live targeting immediately and historical analysis has a cohort-window limitation. [Suggest a correction or send a vendor fact update](https://quillwell.com/guides/request/?type=correction&page=/software/userpilot/)