Getting started

Installing the app

Constellations runs in any browser at constellations.li, and the website can be added to your home screen or dock so it opens like an app. That is what this page covers. Added that way, it lives on the home screen or dock, opens in its own window, and on iPhone is what unlocks push notifications.

There is also a Constellations app for Android phones, which is entering testing on Google Play, and an iPhone app is in preparation. Neither is generally available yet. They use the same account as the website, and everything below about adding the website to your home screen keeps working either way.

Once you have a trip, Home offers it. On a phone it's a card at the top, Add Constellations to your home screen, with Install where your browser can do it in one tap, or the steps for Safari; Later brings it back on your next travel day, once; after that it stays away. On a wider screen it's an Install app button in Home's title bar, and closing the browser's own prompt counts as Later. You can add the app any time from Settings → Display & formats, under This device.

iPhone and iPad

Installation has to be done from Safari:

  1. Open constellations.li in Safari and sign in.
  2. Tap the Share button (the square with the up arrow).
  3. Scroll down, tap Add to Home Screen, then Add.

The app appears on the home screen like any other.

On iOS, push notifications only reach the installed app. Safari tabs can't receive them, so signal pushes won't arrive until the app is installed and push is enabled under Settings → Signals.

Android

To add the website: open constellations.li in Chrome (or Edge, Firefox, Brave). The browser offers an Install app prompt, either as a banner or an entry in the ⋮ menu. Accepting it puts Constellations in the app drawer.

In the Android app from Google Play, the admin screens open on the website. Deleting your account can be started in the app; the link in the confirmation email opens the website to finish.

Desktop

In Chrome or Edge, the install icon sits at the right end of the address bar (a monitor with a down arrow). Clicking it opens the app in its own window and adds it to the dock, taskbar, or launcher.

Turning on push notifications

Once installed, push is enabled under Settings → Signals with "Push on this device". The browser or OS then asks for notification permission; that is the prompt to accept.

Push is how time-sensitive signals reach a device: a delayed flight, a gate moved at the last minute, a document about to expire. Live status covers flights for now; other transit joins as status feeds for it arrive. The permission is per-device, so granting it on a phone doesn't grant it on a laptop.

Constellations never sends marketing or third-party push messages. Every signal category can be turned down or off inside the app, and the permission can be revoked from the browser or OS settings at any time.

Offline

The installed app keeps recently viewed pages readable without a connection, which is useful for checking an itinerary mid-flight. Home, the Trips, People and Signals lists, Settings and any trip that has been opened stay readable for two weeks after they were last viewed.

Some things are saved ahead of time, automatically, whenever the app is open with a connection:

  • The trip underway and the next trip, in full: the trip screen plus every document on it. Boarding passes and confirmations attached to a particular flight or stay, paperwork attached to the trip as a whole, and receipts on expenses are all included.
  • Travel documents: everything in the profile's document vault, passport scans included, along with the travel profile page itself.
  • Other members' trips over the next month: the trip screens, so "where is everyone" still has an answer from a plane. Their documents are not saved.
  • Home and the Trips, People and Signals lists: the screens everything else is reached from, so they are there on a new device before you have opened each one.

The saved copies refresh themselves while online, so nothing shown offline is older than the last time the app was open with signal. Everything saved on the device is cleared on sign-out.

Opening the app uses the saved copy too. If the page can't be loaded within a few seconds, because the signal is weak or missing, the app opens from what's saved on the device instead and brings it up to date once the connection is back.

Saving runs in the background, after the page has finished loading and while the browser is otherwise idle, at a lower priority than anything being waited on. It shouldn't be noticeable.

Knowing what's saved

A document that is on the device carries a Downloaded mark, shown wherever the document already appears — the trip's Files tab, the travel documents list, a constellation's shared files. There's no separate place to go and check.

The mark reflects the copy actually held on the device, so it is accurate rather than a promise: if a device clears its storage, or a very large number of documents pushes the oldest ones out, the mark goes with them. A document with no mark still opens normally with a connection.

Trips work the same way. While you're offline, a trip saved on the device shows a small tick after its name in the Trips list; with a connection every trip opens, so the tick isn't shown. A saved trip opens from wherever you tap it: Home, Signals and a person's page as well as the Trips list.

A saved page read without a connection says so: the header shows Offline, so an itinerary checked mid-flight is clearly the version from before take-off. Search, Add and Connie need a connection and are dimmed until it's back.

Changes made offline

Checklists can be worked through without a connection. Ticking items off, renaming them, adding, removing and re-ordering are all held on the device and sent as soon as there is a signal, so a packing list can be finished on a plane and is up to date on landing.

A row with a change still to send carries a small cloud mark, and this screen says how many are waiting in total. There is nothing to do but reconnect — it happens on its own.

More is held the same way:

  • To-dos and signals: ticking a to-do off under Still to book, or putting it back, and dismissing a signal or undoing that.
  • Expenses: adding one, editing it (amount, label, split, date) and deleting one. Settle up shows a note that it will update once your changes have been sent.
  • Comments and reactions: posting, editing and deleting a comment, and reacting, on a thread that was open before the signal went.
  • Booking details: a booking's name, note, reference, seat and times. Changing a flight number, airline or airports, picking a place, or changing a time zone needs a connection.

Each shows straight away, marked as waiting to send.

If a change genuinely can't be saved — the checklist was deleted while the device was away, for example — the app asks whether to try again or discard it, rather than retrying indefinitely or dropping it silently. A to-do that someone deleted in the meantime is simply left deleted.

Where two people change the same checklist row and one of them was offline, the change that arrives last is the one that sticks. Edits to an expense, a comment or a booking are different: if someone else changed the same detail while you were offline, yours isn't saved, and the app tells you so once, so nobody's change is overwritten without them knowing.

How long changes are kept

Browsers treat data saved by a website as disposable, and may clear it to reclaim space. So the first time there is actually a change waiting to send, the app asks the browser to keep it. On some browsers that is a one-off permission request — it is asked once and never again, whichever way it is answered.

Declining doesn't stop anything working; it only means the browser is free to clear saved data if it needs the space. Adding Constellations to the home screen is the most reliable protection, and on iPhone and iPad it's the difference that matters: Safari clears a website's saved data after seven days of not being used, while an app added to the home screen is exempt.

This applies to everything held on the device, saved documents and pending changes alike — a browser clearing storage clears all of it together.

Everything else needs a connection. Anything involving other people — combining trips, recording a settlement, sharing, reporting — is deliberately not held for later: those aren't decisions to apply days after they were made. Changes waiting to send are cleared on sign-out.

Beyond that, offline reading is a cache of what has already been opened; other pages need a connection. When a page can't be shown without signal, the app says You're offline, names what's missing (a trip, a person's page), and lists the trips and documents that are on the device, upcoming trips first, each with its dates and each a link straight to it. Past trips are folded away underneath. The list is checked against what is genuinely saved at the moment it's read, so it never offers a page it can't open. The app's navigation stays in place on phones, tablets and computers alike, and the missing page loads by itself once the connection is back.