---
title: "Your App in the Console"
description: "What the Shorebird console shows for an app and its releases, Mission Control, Insights, release size analysis and release notes"
---

The [Shorebird console](https://console.shorebird.dev) shows how your app’s releases and patches are doing on devices. Open an organization, then an app. Each app has these tabs: **Mission Control**, **Releases**, **Insights**, and, for Admins and the Owner, **Collaborators**, **Tracks** and **Settings**. On Enterprise there’s also an **Audit log**.

Mission Control, Insights and size analysis are currently free on every plan.

## The app’s summary

The app opens on **Mission Control**, a summary of what’s running on your users’ devices:

* The latest rollout: the most recent patch or release, and how many active devices have it so far. From here you can roll back a patch that’s going wrong; see [Rollback](/code-push/rollback/).
* **Deployment**: monthly active users, new devices, patch coverage (the share of devices on your active releases that already run their release’s latest stable patch), and how your users are spread across release versions and platforms.
* **Releases**: your releases in use, with each one’s share of active devices. **Releases** in the tab bar lists all of them.

Active user numbers come from the Shorebird updater in your app, and only releases built with Flutter 3.35.7 or newer report them. If none of your releases do, Mission Control says **Deployment metrics need a newer Flutter**, and Insights says **Active user metrics need a newer Flutter**. Create a release with a newer Flutter version to start seeing them.

Patch coverage and the latest rollout’s device count need a release built with Flutter 3.47.4 or newer, since older releases don’t report which patch a device is running. Until you have one, Mission Control leaves out **Patch coverage**, and a rollout on an older release says **Rollout adoption needs Flutter 3.47.4+**.

From the command line, [`shorebird metrics`](/account/cli/#metrics-commands) reads the same install, adoption and usage numbers.

## Insights

**Insights** shows the history behind Mission Control: daily, weekly and monthly active users over time, the same split by platform, when in the day and week your users are active, and patch installs and downloads. Each release has an **Insights** tab of its own, with that release’s active users and its patch installs and downloads.

## A release’s tabs

Open a release from **Releases** to see its **Overview** (its patches and their tracks), **Insights**, **Size** and **Notes** tabs. Members who can create releases also see **Artifacts**, and Admins and the Owner see **Settings**.

### Size

**Size** shows what a release is made of, split into native code, Dart code, assets and other files, by category or file by file. Use it to find what’s making your app bigger before you ship.

It covers Android and iOS releases, measured differently on each, and neither is the size users download from the store. For iOS it’s the unzipped `Runner.app`. For Android it’s the App Bundle’s base module, arm64 only, uncompressed. Releases for other platforms show **Size analysis supports Android and iOS only**. A release is analyzed shortly after you create it, so a new one shows **This release has not been analyzed yet** for a few minutes. **This release will not be analyzed** means analysis failed for good for that release; later releases are analyzed as usual. **Size analysis is not available for this build** means Shorebird can’t yet analyze builds from that Flutter revision; later releases built the same way are analyzed once it can.

### Notes

**Notes** holds free-form text about the release, such as what it contains or where it was submitted. Type in the box and click **Save**. Only people with access to the app can see notes, and anyone who can create releases can edit them. `shorebird releases info` prints them too; see [View release details](/code-push/release/#view-release-details).