Console & team
The console is where you create apps, see how each patch is doing on real phones, act on patches, and manage who on your team can do what.
Signing in
Sign in with Google, or with your email and a one-time code. Your account is created the first time you sign in. There's no password to remember.
Organizations
Apps belong to an organization. Everyone gets a personal one; create a team organization from the organization menu in the sidebar when several people work on the same apps.
Members of an organization see every app in it. Add a teammate once and they have all of the team's apps, with one role across them.
Roles
| Role | Can |
|---|---|
| Viewer | See every app, release, patch, device and the activity log. Changes nothing. |
| Developer | Everything a viewer can, plus make releases and patches, change rollouts, roll patches back and forward, and connect projects with overpush init. |
| Admin | Everything a developer can, plus create apps, add and remove members, and remove anyone's project key. |
| Owner | Everything, including adding and removing other owners. |
Every organization keeps at least one owner. The last owner can't leave or be demoted until someone else is made an owner.
Adding a teammate
- Open Members in the sidebar.
- Enter their email and pick a role.
- If they already have an account, they're added at once. If not, they join automatically the first time they sign in with that email. Send them the console link.
Removing someone takes away their access to every app in the organization, and the projects they connected stop working at once.
An app's overview
Open an app to see how it's doing. What it shows depends on the plan (see Plans and billing); on Business:
| Devices | Phones that have run a release of the app. |
| Running a patch | How many of them are running a patch right now. |
| Patch installs | Patch downloads, on the day each happened. |
| Failed installs | Phones where a patch failed to install or was rolled back after crashing. |
| Patch adoption | For each release, the share of its phones on its newest patch. |
Click Failed installs for the list behind the number: when, which release and patch, which phone, and the reason. Hover a chart for each day's number, or open Show as table under it.
Releases and patches
The Releases tab lists every release of the app, Android and iOS. Open one to see its patches:
- Active: the patch phones on this release get.
- Superseded: an older patch, replaced by a newer one.
- Rolled back: stopped. Hidden unless Show rolled back is on.
Each patch shows its rollout, installs and failures. If any phone failed, What went wrong lists the phones and the error each one reported. The ⋮ menu on a patch changes its rollout, rolls it back, or rolls it forward again. See Rollouts & rolling back.
Devices
On Business, each release lists every phone that has run it, 15 at a time: the phone model and OS version, the patch it runs, and any failure. Filter by Running a patch, No patch or Failed. A phone that has updated to a newer release from the store stays listed with Now on and that version. Click a phone for its history. Device ids are made up by the app itself; nothing in them identifies a phone or its owner.
Activity
Activity in the sidebar (Business and up) is the organization's log: who published which patch, changed a rollout, rolled something back, added a member or connected a project, and whether they did it from the console or the CLI. Filter it by app.
Plans and billing
Each organization has a plan. The plan decides how many patch installs a month are included, how big the team can be, and what the console keeps about devices:
| Plan | What the console shows | Device data stored |
|---|---|---|
| Hobby | Patch installs and failures, per patch and per day | None |
| Pro | That, plus how many devices run each release | None: totals only |
| Business, Enterprise | Everything: every device, its patch, history and errors | Every device |
A plan keeps data at its level from the day it starts. After an upgrade, earlier days stay as they were. After a move down, device details stop being kept when the paid period ends, and the ones already kept are deleted.
The Billing page in the sidebar shows the plan, this month's patch installs against the plan's limit, and every invoice with its status, payment date and transaction id. A patch install is one device installing one patch; the count starts again on the 1st of each month.
When shipping pauses
New releases and patches pause, in the console and in the CLI, in two cases:
- An invoice is overdue. Each invoice has 7 days. Paying it lets you ship again at once. Still unpaid 30 days after the due date, the organization moves to the free Hobby plan and the invoice is cancelled.
- Hobby's installs are used up for the month. Shipping resumes on the 1st, or right away after an upgrade. On paid plans, extra installs are billed instead.
Apps already installed are never affected: devices keep downloading the patches already published, and keep the ones they have. Rolling a patch back always works. A banner on every app page says when shipping is paused and why.
Changing plans
An upgrade starts at once. The part of the period you already paid for is credited, and the invoice charges the new plan for the rest of the period. A move to a smaller plan happens when the current period ends.
Connected projects
An app's Settings tab shows its app id and every project connected to it with overpush init, such as each laptop and CI. Remove one and that project stops working until it's connected again.
Your account
Account lists every browser and laptop signed in to your account. Sign one out there if a laptop is lost. The console has a light and a dark theme; switch in the sidebar.
Getting help
Email support@overpush.in with the command you ran and its whole output, or use the contact form.