> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/mobile-app/mobile-app-troubleshooting/the-app-looks-completely-different-than-before-or-than-my-colleagues.md).

# The app looks completely different than before or than my colleague's

Why the app can look different across devices and app versions, and how to tell which app you are using.

## The app looks completely different than before or than my colleague's

{% hint style="info" %}
Before you start, check [Troubleshooting checklist: start here](/issues-and-troubleshooting/troubleshooting-checklist-start-here.md). An outdated app version can cause unexpected differences.
{% endhint %}

### Introduction

Sometimes the app looks different from how it looked before, or different from a colleague's phone.

In almost all cases this is expected. OutSmart has more than one mobile app, and the two platforms are designed to look different.

### Detailed explanation

There are two normal reasons the app can look different:

* **iOS and Android are laid out differently on purpose.** The iPhone/iPad app and the Android app follow the design conventions of each platform, so menus and buttons are not in identical places. This is by design, not a bug.
* **OutSmart NEXT looks different from the older (legacy) app.** OutSmart NEXT is the newer app and has a different look and navigation than the previous app. If a colleague recently switched, their screens will not match an older app.

Because of this, the same task can look different on two devices while doing exactly the same thing.

### Step-by-step guide

{% stepper %}
{% step %}

#### Confirm which app you are using

Check whether the device is running the newer OutSmart NEXT app or the older app. The name and icon, and the app's own about/settings screen, indicate which one it is.
{% endstep %}

{% step %}

#### Check the platform

Note whether the device is iOS (iPhone/iPad) or Android. Layout differences between the two are expected.
{% endstep %}

{% step %}

#### Check the version in the BackOffice

An administrator can open **Settings → Paired devices** to see the operating system and app version for each employee, and compare it with the App Store or Play Store. See [Paired devices](/mobile-app/general-mobile-app/paired-devices.md).
{% endstep %}

{% step %}

#### Update if you are behind

If the device is on an older version, update it so everyone works with the same, current app. See [Troubleshooting checklist: start here](/issues-and-troubleshooting/troubleshooting-checklist-start-here.md).
{% endstep %}
{% endstepper %}

### FAQ

<details>

<summary>"It looks totally different since my colleague switched from iOS to Android"</summary>

That is expected. The iOS and Android apps are laid out differently on purpose. The features are the same; the screens are arranged to match each platform.

</details>

<details>

<summary>"The app changed after an update — is something broken?"</summary>

No. Updates can change the look and layout. If a specific feature is missing, check your permissions and app settings, or contact support.

</details>

<details>

<summary>"How do I know if I'm on OutSmart NEXT or the old app?"</summary>

Check the app icon and name, and the about/settings screen inside the app. An administrator can also confirm the app version under Paired devices in the BackOffice.

</details>

### References

* [What is the OutSmart mobile app?](/mobile-app/general-mobile-app/what-is-the-outsmart-mobile-app.md)
* [Paired devices](/mobile-app/general-mobile-app/paired-devices.md)
* [Android - OutSmart NEXT](/mobile-app/android-outsmart-next.md)
* [iOS - OutSmart App](/mobile-app/ios-outsmart-app.md)
* [Troubleshooting checklist: start here](/issues-and-troubleshooting/troubleshooting-checklist-start-here.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.out-smart.com/mobile-app/mobile-app-troubleshooting/the-app-looks-completely-different-than-before-or-than-my-colleagues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.