Skip to main content
Simulation Flow Guide Template

Use this to organize your Simulation (Required for customer simulation requests)

Joël avatar
Written by Joël
Updated over 3 years ago

So you're looking to have LemonadeLXP build a custom simulation for you? You came to the right place!

Welcome to the Simulation Flow Guide Template. This guide is designed to help organize your content to ensure that LemonadeLXP staff can create a simulation of your app or website that looks and feels like the real thing!

How To Use the Template

Toward the end of the the document you will find empty templates for you to outline all the potential user paths.

When completing the template, each page should describe what users are able to do on that given screen, and where they will be taken by that action. Examples are provided in the document.

To ensure that the simulation mimics the real app or webpage, please provide direction for every possible hotspot on each screen.

Filling Out the Template

Images

  • Images are to be included in a separate folder. Images that are embedded in this document cannot be used in the creation of the simulation

  • Be sure that the image file names provided in this document match the file names in the external folder

  • Each image should have it’s own unique name or identifier

Having images that are the right size and format make a big difference! For help as to how to best create images to be used in your simulation, please see these articles:

Hotspots

  • It’s best to include small screenshots of the areas of your screen which you wish to make hotspots

  • Be sure to include all hotspots on each screen. If a hotspot is not outlined with a destination, it will not be included

  • Images of hotspots can be embedded here, as the image is just for reference

Leads to

  • This is the hotspot’s destination

  • Please provide the image file’s name, as seen in the external folder you provide

In the document, you will have to copy and paste the blank template for screen 2 to add additional pages.

Did this answer your question?