# Results

## *Qualitative Results*

Ingress is widely perceived as difficult to understand (68.8%) and learn (87.5%), with all participants (100%) agreeing that it is highly complex. Over half found it demotivating (56.4%) and inefficient (53.3%). These findings indicate that Ingress has a steep learning curve and is overly complicated.

<figure><img src="/files/WjhTWwW3nKrQVbzZVcyX" alt=""><figcaption><p>Comparison of objectives completed according to user and in reality</p></figcaption></figure>

## *Quantitative Results*

<figure><img src="/files/o7fbCMkqBHcuI7Bpo0oh" alt=""><figcaption><p>Correlation of Navigation &#x26; Task Summary Metrics with Tutorial Time</p></figcaption></figure>

Longer tutorial times may lead to increased task difficulty and completion time while reducing task completion rates, suggesting that tutorial complexity may hinder user learning and task performance.

<figure><img src="/files/WQblkHWYpklFe5O3ApnV" alt=""><figcaption><p>User Navigation Flow</p></figcaption></figure>

Our analysis of screen flow revealed navigation patterns, showing that users frequently switch between the portal and home screens. Many users return to the home screen instead of the menu, requiring an extra click to navigate back, leading to inefficiencies.

## Overall Results

* **Ineffective tutorial**: All the aspects of gameplay are not explained, and there is an overwhelming amount of information
* **Game Mechanics**: Overly complicated systems with too little time to master them
* **Bad UI Design**: Navigation through the menus is tedious and some parts of the game are unnecessarily hidden


---

# Agent Instructions: 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:

```
GET https://zhengtian-ding.gitbook.io/quantitative-ux/results.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.