> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/how-the-apps-work/screens/reports/analytics.md).

# Analytics

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). Platforms: iOS and Android. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/reports/analytics.md).
{% endhint %}

Charts and top-five lists for one group or asset register on the apps: how many tasks are new, in progress and completed, the top tags and users, and a map of task locations. It counts the tasks of the list it was opened from, reads only the device's copy of them, and makes no request to the server.

* **Where:** iOS: a group's task list, view menu (`TaskListingGroupViewVC`), "Analytics", which switches the group's view to this screen (`NewDashboardVC`); not offered for rooms, areas or asset registers. An asset list's menu (`TaskListingOverflowMenuVC`), "Analytics". Android: a group's task list, view sheet (`BottomSheetChangeView`), "Analytics" (`ReportsActivity`); not offered for rooms or areas. An asset list's "+" menu, "Analytics" (the same screen, for assets).
* **Who:** any user who can open the list. Neither app checks a role, permission or plan for the menu items or the screen.
* **Feature:** [Dashboard](https://docs.snapfix.com/product/features/reports/dashboard.md)

## Layout

**iOS**, top to bottom:

1. **Header:** the group's image and name, the title "Analytics" and an info button.
2. **Dates:** "Created between … and …" when the list has a created-date filter, and "Activity from … to …" for the activity range (from the earliest task to today when there is no filter).
3. **Count:** "N Tasks", or "N Assets" for an asset register.
4. **Three status cards**, for red, amber and green. Each shows a small pie chart, the count and the share with two decimals. The cards have no words.
5. **Table:** one section per tag folder with its top five tags ("View all" when there are more than five), then "Users" with the top five, a map with a pin per task that has a location (Apple Maps), and a card with "Log in to Snapfix on your desktop to access Dashboards, Reports, and Data Analytics." and a button.

**Android**, top to bottom:

1. **Toolbar:** "Analytics" and an info icon.
2. **Group name and image**, "Activity from … to …" and "Created between … and …" when the list has those filters, and the count "N Tasks" or "N Assets".
3. **Three status cards** with a pie chart, the count and the share with two decimals.
4. **"Top 5" tag folders**, each with its top five tags and "View all" when there are more than five. Then "Users", the people who created, wrote in, are assigned to or follow the tasks, with the top five and "View all", or "No Users" when there are none.
5. **Map** (Google Maps) with a pin per task that has a location, and the device's own location when the location permission is given.
6. **Web card:** "Log in to Snapfix on your desktop to access Dashboards, Reports and Data Analytics." and the button "Snapfix Web Login", which is hidden and never shown.
7. **Bottom navigation** (groups only): "List", "Grid", "Planner" and "Settings", with "Analytics" selected. Asset registers have no bottom navigation.

Both apps leave out the tag folder sections for an asset register, so an asset register shows its count, status cards, users, map and web card.

The info text: "“Analytics” displays a summary of the group activity, and can be filtered by date-range, users and tags." and "Please note that additional analytics are available on your Snapfix Web." For an asset register it says "asset register activity" and "date-range and users". The screen itself has no filter controls: "can be filtered" refers to the list's own filters.

## Inputs

None on the screen. It counts the tasks the list holds, with the list's search, filters and date range, passed in when the screen opens. When an Android list is paged, it first loads every matching task ID for each colour, with "Please wait...".

## Actions

| Action                                               | Who                   | What happens                                                                                                                               | API  |
| ---------------------------------------------------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ---- |
| Info button                                          | Anyone                | Shows the info text.                                                                                                                       | None |
| "View all" on a tag folder or on "Users"             | Anyone                | Shows the full list for that folder or for users: a panel on iOS, a bottom sheet on Android. Neither has search or sort.                   | None |
| Tap a pin                                            | Anyone                | Opens the task: iOS in [Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md), Android in the task's chat. | None |
| iOS web card button                                  | Anyone                | Opens `https://web.snapfix.com/dashboard-report`. No web page has that path, so the web app opens on `/fix`.                               | None |
| Android "Snapfix Web Login"                          | Nobody                | Hidden; it cannot be tapped.                                                                                                               | None |
| Android bottom navigation: "List", "Grid", "Planner" | Groups                | Returns to the list in that view, or opens planned tasks.                                                                                  | None |
| Android bottom navigation: "Settings"                | Users the list allows | Opens the group's settings.                                                                                                                | None |
| Back                                                 | Anyone                | Returns to the list.                                                                                                                       | None |

## States

* **Loading:** iOS shows an indicator in each tag folder's header until the tag data is ready. Android shows a progress bar in the users card until the users are ready, and "Please wait..." while it loads the IDs of a paged list.
* **Empty:** each empty section says "No" and the section's name, for example "No Users". The counts show zero.
* **Error:** the screen reads the device's database and shows no error text. If the users cannot be read, the users card shows "No Users".
* **No permission:** none on this screen.
* **Offline (mobile):** the screen works without a connection, because it reads the device's copy. Only the web link and the map's tiles need one.

## Dialogs and sheets

* **Info:** the info text, under [Layout](#layout).
* **View all:** iOS `ViewAllDashboardVC`, a panel with the full list for a tag folder or for users. Android `DashboardViewAllBottomSheet`, a bottom sheet with the same list.
* **Analytics on web:** a popup that points to the web analytics, with the same broken link. iOS shows it from the help hub (`AnalyticPopupVC`). Android shows it from the group list, the profile and the help hub (`AnalyticsInfoDialog`), and its button is hidden there too.

## Platform differences

* **Entry:** iOS shows the screen as one of the group container's views; Android opens a separate screen and hands it the task IDs for each status.
* **Navigation:** iOS shows no bottom navigation. Android adds it for groups, so users can switch view from it.
* **Map:** Apple Maps on iOS; Google Maps on Android, which asks for the location permission for the current-location marker.
* **Web link:** iOS shows a working button whose link leads to `/fix`. Android shows the text with no button.
* **Thread safety:** iOS builds the tag and user lists on a background queue while the table reads them on the main queue. Android builds the list of task IDs from several threads without a lock.
* **Legacy screen:** iOS also has an older group dashboard, reached only from the group list's hidden bottom bar: [Legacy dashboard](https://docs.snapfix.com/how-the-apps-work/screens/reports/legacy-dashboard.md). Android has none.
* **Web:** the web dashboard has more: the status by day, a comparison, a group table and filters ([Dashboard](https://docs.snapfix.com/how-the-apps-work/screens/reports/dashboard.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://docs.snapfix.com/how-the-apps-work/screens/reports/analytics.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.
