---
title: "Mobile Device Configurations"
canonical: "https://kb.myframeworks.com.au/space/FRAM/28410724/Mobile%20Device%20Configurations"
format: markdown
---
Frameworks is an adaptive web-designed application meaning it is aware of the device on which it is running and can adjust to the settings and configuration of that device. As such Frameworks is able to run on a range of mobile devices such as smartphones, smartphones with scanners, tablets, and hybrid laptops so long as these devices are sufficiently configured and can run a standard browser such as Google Chrome or MS Edge. Furthermore, Frameworks will customise the available menu items, system navigation and screen definitions if the device, such as a handset, has screen size limitations that must be considered. 

These pages define the minimum level considerations for each device type and how best to configure Frameworks for use on the device types. Frameworks will understand the underlying device that is in operation and will preset parameters based on that device that will control the display and operation of Frameworks. These parameters can be overwritten to improve the user experience, these details are also defined below in the "Modifying the URL" section.

> ℹ️ When running **Frameworks Mobile** on a handset, like a smartphone, the activates available from the Frameworks menu is cut down to a handful of select tasks. Refer to [Frameworks Mobile Version](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28410756) for more information.

> ✅ Refer to [Mobile Inventory](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/616595604) documentation for more information related out Mobile Inventory Application.

> ⚠️ **Important**: To complete these steps, you will need to know your Frameworks URL. If you require assistance with this please contact [Support](https://kb.myframeworks.com.au/page/support).
> ⚠️ 
> ⚠️ ![image-20251119-234501.png](media://c9835eae-d936-497a-9961-24f60dd1340f)

# Device Requirements

> Macro (include)

# > Macro (anchor)

Modifying the URL

Frameworks understands the underlying device that is in operation and will pre-set parameters based on that device that will control the display and operation of Frameworks. These can be overwritten to improve the user experience by additional URL Parameters added to your Frameworks shortcut allowing Frameworks to be opened up using optimised settings for your particular device. 

The default settings for each device are:

- **desktop:** `?skin=Frameworks&device=desktop&useMobile=False`
- **tablet:** `?skin=Frameworks&device=tablet&useMobile=False`
- **handset: **`?skin=Tahoe&device=handset&useMobile=True&fontIncrease=1`

> ⚠️ The default setting is not required to be added to your Frameworks URL unless you are choosing to overwrite them.
> ⚠️ 
> ⚠️ For most handsets and smartphones an additional Frameworks URL parameter is not required. Frameworks will auto-detect the device type and display the handset version.

To add the parameters to your framework link you will need to add a **? **after Fluid.html and then add the parameters with a **& **between each parameter. 

**Example**: `https:\\[SiteID].[Environment].myframeworks.com.au?skin=Tahoe&device=tablet&useMobile=False&fontIncrease=2`

The parameters are:

| **Parameters ** | **Values and Definitions** |
| --- | --- |
| **skin=** | The available value is:<br>- **Tahoe**: This skin is a simplified look to give you maximum information on your screen.
- **Frameworks:** This is the default look for the desktop and tablet.<br>Additional **skins **will be delivered in future Frameworks releases. |
| **device=** | The values are:<br>- **desktop**: This defines the device being used to be a desktop computer. Activity layout will not have been changes.
- **tablet**: This defines the device being used to be a tablet device. Some activity layouts will have been modified to display better on smaller screens.
- **handset**: This defines the device being used to be a small handset or mobile phone. The Frameworks menu will be limited to only activities which have been modified to work well with small handset sized screens.
  `device=handset` is recommended to be used the additional parameter `useMobile=true`. Not all Frameworks activities are available when device=handset is defined. |
| **useMobile=** | The values are:<br>- **false**: When defined Framework will function as normal displaying the full Frameworks Logo, Dashboard Icons, the Company and user details, and multiple tabs.
- **true**: When defined the Frameworks menu will be accessed via just the Frameworks Logo and the tab functionality will be turned off for more screen space. |
| **fontIncrease=** | This value is a **Numeric **value. This will increase the size of the text displayed in Frameworks.<br>> ℹ️ Typically a number between 1 - 5 works well. |


# Creating a Desktop/Home screen Icon.

## Windows 10 hybrid devices.

When using a mobile device running Windows 10 the easiest way to access your Frameworks is to create a desktop icon. 

> Macro (include)

## <span style="color: #172b4d">Android Devices / Chrome Mobile</span>

By adding your Frameworks Mobile access to your mobile devices Home Screen will:

- Give you quick access to Frameworks on your mobile device
- On accessing the page it will automatically hide the URL Address Bar at the top of the page.

> Macro (include)

# > Macro (anchor)

<span style="color: #172b4d">Additional Mobile Device Configurations</span>

<span style="color: #333333">Select an option below for more information</span>

> Macro (ui-children)