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

# Improve performance for InstantSearch Android

> Learn how to optimize your InstantSearch Android app.

Algolia is fast by default.
But network speed and bandwidth can vary.
This page lists a few best practices you can implement to adapt to your users' network conditions.

## Add a loading indicator

You can mitigate the impact of a slow network on your search experience by managing user expectations.
One way of letting them know that the network is suboptimal is by displaying a **loading indicator**, which prevents them from becoming frustrated by network delays and blaming your app for lack of responsiveness.

**Use the [`Loading`](/doc/api-reference/widgets/loading/android) widget to implement this behavior.**

## Optimize build size

See the [Android Studio guide on shrinking your code and resources](https://developer.android.com/build/shrink-code).

## Queries per second (QPS)

Search operations aren't limited by a fixed "search quota".
Instead, they're limited by your plan's [maximum QPS](https://support.algolia.com/hc/en-us/articles/4406975224721) and
[operations limit](https://support.algolia.com/hc/en-us/articles/18138875086865).

Every keystroke in InstantSearch using the `SearchBox` counts as one operation.
Then, depending on the widgets you add to your search interface,
you may have more operations being counted on each keystroke.
For example, if you have a search interface with a `SearchBox`, a `HierarchicalMenu`, and a `RefinementList`,
then every keystroke triggers one operation.
Upon each user change to a `HierarchicalMenu` or `RefinementList`, a new operation is executed.

For more information, see:

* [`SearchBox`](/doc/api-reference/widgets/search-box/android)
* [`HierarchicalMenu`](/doc/api-reference/widgets/hierarchical-menu/android)
* [`RefinementList`](/doc/api-reference/widgets/refinement-list/android)