---
title: "M300XL UI Design Best Practices"
slug: "m300xl-ui-design-best-practices"
updated: 2024-05-29T17:38:58Z
published: 2024-05-29T17:38:58Z
canonical: "support.vuzix.com/m300xl-ui-design-best-practices"
---

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

# M300XL UI Design Best Practices

## **Screen Orientation**

The device may be worn on the left or right eye, and will always be in landscape or reverseLandscape orientation.

- The proper orientation to specify for your Activity in the manifest is:

```java
android:screenOrientation="sensorLandscape"
```

## **Navigation**

The user will navigate your UI with the three physical buttons or touch swipes that can be automatically translated to KeyEvent key codes as described in the [Interaction Methods](/v1/docs/m300xl-interaction-methods) article.

- Allow UI elements to be navigated with simple left/right/up/down navigation, and give users clear visual indicators which UI element currently has focus.
- Consider adding customized verbal navigation using the [Vuzix Speech SDK](https://support.vuzix.com/v1/docs/overview-8).
- Explicitly control the focus order. More details can be found in the separate [Navigation and Focus](/v1/docs/navigation-and-focus-1) article.

## **Usability Best Practices**

The most important aspect to a well-designed user interface for an application intended to be used on the M300XL and M300 is simplicity. This is largely driven by the limited amount of space on the display.

- Avoid complex menu systems, instead use a linear progression through interface components to minimize the amount of time a user needs to dedicate to navigating the application UI.
- Limit the amount of information being displayed to the user at any given moment to be very contextually relevant. I.E. a single, specific instruction to guide the user to performing an individual step in a procedure.
- Avoid displaying complex diagrams or schematics to the user, instead opt for displaying only the components immediately relevant to the task at hand.
- Try to minimize the frequency of scenarios requiring the user to physically interact with the device by leveraging alternative methods of advancing a user through the application interface. The best way to do so is by leveraging voice commands, but this can also be done by automatically advancing a user to the next screen based on any number of interactions, such as scanning a barcode, taking a picture, or some other form of verification that the step has been completed.