---
title: "Launchers Best Practices"
slug: "launchers-best-practices"
updated: 2025-01-31T04:23:37Z
published: 2025-01-31T04:23:37Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.whatfix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Launchers Best Practices

<div class="accordion">
    <div class="accordion-toggle"> Add Launchers to a Launcher collection </div>
    <div class="accordion-content">
     <p>
     
A Launcher once created must always be a part of a Launcher collection for it to reflect on the page or application. A Launcher collection is a group of Launchers belonging to the same page.
For more information, see [Add a Launcher to an existing collection](/studio/docs/add-a-launcher-to-an-existing-collection){target=`_blank`}.
        
</p>
</div>
</div>

<div class="accordion">
    <div class="accordion-toggle"> Create one or two Launchers per page </div>
    <div class="accordion-content">
     <p>
  
It is recommended to limit the number of Launchers to one or two per page. For more information, see [Create a Launcher](/studio/docs/create-a-launcher){target=`_blank`}.         

:::(Warning) (Note)
Visibility rules are defined for the Launcher Collection. So even if you have only one Launcher on a page, it needs to be part of a collection.
:::
</p></div></div>

<div class="accordion">
    <div class="accordion-toggle"> Create one Launcher collection per page </div>
    <div class="accordion-content">
     <p>
         
Whatfix evaluates only one Launcher collection at any given time. If two or more Launcher collections exist on the same page of an application, then only one of them is evaluated. 
         
When editing or modifying a particular page to add a new Launcher, look for any existing Launcher collection for that page. Do not create a new Launcher collection for a page if the collection already exists.
         
For more information, see [Adding a Launcher to an existing collection.](/studio/docs/add-a-launcher-to-an-existing-collection){target="_blank"}
         
:::(Warning) (Note)
The criteria for evaluation depends on the visibility settings or the number of conditions (in case visibility settings are the same for two segments).
:::
</p></div></div>

<div class="accordion">
    <div class="accordion-toggle">  Provide URL paths for Launcher Segment across application environments </div>
    <div class="accordion-content">
     <p>

If you want the same Launcher segment to work across application environments, then provide URL paths instead of the complete URLs. If this is not done, the Launcher segment in one environment may not work in another​.
![DB_Beacon_VR_URL path](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/DB_Beacon_VR_URL%20path.png){height="" width="500"}

</p></div></div>

<div class="accordion">
    <div class="accordion-toggle"> Look for existing Launcher collections on a page </div>
    <div class="accordion-content">
     <p> 
When editing or modifying a particular page to add new Launchers, look for any existing Launcher collection for that page. Don't create a new Launcher collection for a page if the collection already exists.

</p>
</div>
</div>

<div class="accordion">
    <div class="accordion-toggle">Choose an appropriate button style for the Launcher</div>
    <div class="accordion-content">
     <p> 
         
Select different button styles for a Launcher to suit the underlying application. Choose between **{{glossary.Filled}}** (Primary) button, **Secondary** (Outlined) button, and **{{glossary.Text}}** button styles based on your use case. 
             
![lm_launchers_button style](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/lm_launchers_button%20style.png){height="" width="500"}

For more information, see [Customize a Launcher.](/studio/docs/customize-a-launcher){target="_blank"}
</p>
</div>
</div>

<div class="accordion">
    <div class="accordion-toggle">Provide clear and concise text for the Launcher </div>
    <div class="accordion-content">
     <p>

Keep the text in the Launcher short. The text of the Launcher should give the end user clarity on the information rather than being something generic.

</p>
</div>
    
<div class="accordion">
    <div class="accordion-toggle">Place Launchers contextually</div>
    <div class="accordion-content">
     <p>
        
Place the Launcher where the end user will most need it on the application, and not in a generic location. If there's a dashboard or homepage, place a Launcher that launches a Flow to guide users through key features or updates.
              
</p>
</div>

 <div class="accordion">
    <div class="accordion-toggle">Preview the Launcher before pushing it to Production</div>
    <div class="accordion-content">
     <p>

Once you are done creating a Launcher, test the Launcher in the Preview mode before publishing it. Ensure that it appears in the correct location.
         
For more information, see [Preview a Launcher](/studio/docs/preview-a-launcher){target="_blank"}.     
 </p>
</div>

## Related

- [Launcher not latching properly to the selected element](/launcher-not-latching-properly-to-the-selected-element.md)
- [Reselect Launcher elements to manage UI changes](/reselect-launcher-elements-to-manage-ui-changes.md)