> 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/general-mobile-app.md).

# General mobile app

Use this section for mobile guidance that applies across devices.

Use the general pages for shared behavior, setup, and concepts.

Start with [Troubleshooting checklist: start here](/issues-and-troubleshooting/troubleshooting-checklist-start-here.md) when something stops working.

Use [Mobile App Troubleshooting](/mobile-app/mobile-app-troubleshooting.md) for common problems across iOS and Android.

Use the platform guides for exact screens and button names.

### Best for cross-platform guidance

These pages are mainly platform-agnostic:

* [What is the OutSmart mobile app?](/mobile-app/general-mobile-app/what-is-the-outsmart-mobile-app.md)
* [Connect a smartphone or tablet](/mobile-app/general-mobile-app/connect-a-smartphone-or-tablet.md)
* [Synchronise the mobile app](/mobile-app/general-mobile-app/synchronise-the-mobile-app.md)
* [Device policies and settings](/mobile-app/general-mobile-app/device-policies-and-settings.md)
* [Paired devices](/mobile-app/general-mobile-app/paired-devices.md)
* [Replace or reconnect a mobile device](/mobile-app/general-mobile-app/replace-or-reconnect-a-mobile-device.md)
* [Use the mobile app offline](/mobile-app/general-mobile-app/use-the-mobile-app-offline.md)
* [Use track and trace in the mobile app](/mobile-app/general-mobile-app/use-track-and-trace-in-the-mobile-app.md)

### Also covered in iOS and Android

These pages overlap with the platform manuals.

#### Best kept as shared guides

Keep these pages general.

They describe the same workflow on both platforms:

* [Complete a work order](/mobile-app/general-mobile-app/complete-a-work-order.md)
* [Register hours](/mobile-app/general-mobile-app/register-hours.md)
* [Add photos, files, and notes](/mobile-app/general-mobile-app/add-photos-files-and-notes.md)
* [Use forms](/mobile-app/general-mobile-app/use-forms.md)
* [Collect signatures](/mobile-app/general-mobile-app/collect-signatures.md)

#### Better as platform-specific guides over time

Move these topics toward iOS and Android first.

They depend more on screens, navigation, and device behavior:

* [Create a work order](/mobile-app/general-mobile-app/create-a-work-order.md)
* [Use the map](/mobile-app/general-mobile-app/use-the-map.md)

For screen-specific steps, use [iOS - OutSmart App](/mobile-app/ios-outsmart-app.md) or [Android - OutSmart NEXT](/mobile-app/android-outsmart-next.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.out-smart.com/mobile-app/general-mobile-app.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.