Supported browsers and devices — Help

1pm is a web app, which means it runs in whatever browser you already have. There is no separate app to download for the venue and no separate app for crew.

This article covers what counts as a supported browser, what runs well on which devices, and the corners where you might hit a limit.

Supported browsers, in plain language

The four current evergreen browsers all work: Chrome, Safari, Firefox, Edge. By "current" we mean any version released within roughly the last two years, which on the major desktop platforms means anything that has auto-updated itself recently. If you haven't deliberately frozen your browser version, you are almost certainly on a supported one.

That covers Chrome on Windows, macOS, Linux, ChromeOS, Android. Safari on macOS and iOS. Firefox on Windows, macOS, Linux. Edge on Windows and macOS. Plus the dozens of niche browsers built on Chromium under different names (Brave, Vivaldi, Arc, Opera) which are all close enough to Chrome to work without us doing anything special.

We do not officially support Internet Explorer in any version. It has been retired by Microsoft and 1pm does not test against it. If you are on an enterprise machine that still ships IE as a default, switch to Edge and 1pm will work.

Devices

The full planner UI is designed for a laptop or desktop. The dense timeline editor, the inline rename of timeline items, the drag-to-reorder, and the side-by-side BEO panel all assume you have a keyboard, a precise pointer, and at least a 1024-pixel-wide window. You can technically do all of these on a tablet or a phone, but the experience is built for the bigger surface.

The crew view is the opposite. The live shareable run-sheet link is built mobile-first. Crew open it on a phone on the venue floor and the page is designed for one-handed reading: large tap targets, big times, items grouped into clean blocks. It works on tablets and laptops too, but the bias is towards a phone.

Managing an event on a tablet (an iPad in landscape, for example) gets you something in between. The dashboard, the events list, the briefing fields, and the share panel all work fine. The drag-to-reorder on the timeline is fiddlier with a finger than with a mouse, so most people on a tablet flip into one of the other timeline edit modes (typing in the start time directly) rather than dragging.

iPad / tablet specifics

The iPad in particular is a popular working device for venue teams on the move, and a few things are worth knowing:

In landscape orientation, the planner page lays out close to the desktop view. This is the recommended posture.

In portrait orientation, the planner page shifts towards the mobile-friendly stacked layout. Inline editing still works; some of the side panels move below the timeline.

Apple Pencil works as a pointer for tap-and-drag. It is not specially supported (no annotations on the run sheet, no handwriting recognition) but it does make dragging timeline items more comfortable than a finger.

iPadOS Safari is the same code base as macOS Safari. Anything that runs on a Mac runs on an iPad.

External keyboards (Magic Keyboard, Folio) are recommended for any session where you'll be typing more than a few timeline items. The on-screen keyboard takes up half the screen.

Mobile phones (planner side)

You can use the planner on a phone. Everything works, including inline editing, the briefing fields, and the share panel. The experience is just compressed: the timeline is a vertical scroll, the side panels become full-screen pages.

The supported scenario is "I left my laptop at home and need to add a quick item from my phone in the taxi". The not-supported scenario is "I'm going to plan a 200-item three-day conference from my phone over the next two weeks". You can technically do it, but you'll burn through your patience faster than necessary.

Mobile Safari (iOS), Chrome (Android), and Firefox (Android) all work. We see most planner-from-phone traffic on iOS Safari and Chrome Android in roughly equal share.

Mobile phones (crew side)

Crew almost always read the run sheet from a phone, which is the case the page was designed for. Specifically:

The page loads on any iPhone running iOS 15 or newer, which is approximately every iPhone made in the last seven years.

It loads on any Android phone running Chrome with a current update, which is approximately every Android phone still receiving updates.

The page works offline once it has loaded. If a crew member opens the link while they have signal and then walks into a basement venue with no connection, the timeline stays visible. Live updates pause and catch up when signal returns.

Crew can save the link to their home screen. On iOS, tap Share, then Add to Home Screen. On Android, the browser will typically prompt with an "Add 1pm to home screen" banner the second time the link is opened. The home-screen version is a slightly enhanced version with no browser chrome. See Saving the link to your phone.

In-app browsers (the awkward one)

A handful of messaging apps open links in their own embedded browser rather than handing the URL off to Safari or Chrome. Facebook Messenger, Instagram, LinkedIn, some email clients, some Slack mobile versions. These embedded browsers vary in quality.

Most of them are fine. Some have limitations with live updates or with saving the page to home screen. If a crew member taps a 1pm link from inside an app's chat and the page misbehaves, the universal fix is to copy the URL and paste it into Safari or Chrome directly.

Telegram's in-app browser is good. WhatsApp's in-app browser is decent. Messenger's is workable but does not let you save to home screen. Instagram's is the least friendly of the bunch.

If you know your crew tends to open links from a specific in-app browser, advise them to copy the link out into a proper browser the first time they open it. After that, the link is cached and they're set.

Specific feature notes

A few features have stricter browser requirements than the rest:

Drag-to-reorder timeline items needs touch or precise pointer support. This is universal on current browsers and rarely a problem.
The PDF print views (run of show, BEO, RSVP roll) use the browser's print stack, which is consistent across Chrome, Safari, Firefox, and Edge. Some older Android browsers do not have a print stack and will hand the page to the device's share menu instead (saving as a PDF from there works).
The Stripe customer portal opens via a redirect from 1pm. Some privacy-extension-heavy browsers (e.g. heavily-configured Firefox with strict tracking protection) sometimes block the redirect. The fix is a different browser or a temporary disable of the offending extension. See Managing your subscription.
File uploads from the planner page need a current browser. Drag-and-drop of files is supported on every desktop browser; tap-to-pick is supported on every mobile browser.
The live-updates mechanism uses Server-Sent Events. Every browser listed above supports SSE natively. If you happen to be behind a corporate proxy that strips long-running HTTP connections, the live updates may fall back to polling. Functionally the same; you might see a slight delay.

Recommended setup for the venue

If you're picking the equipment to use day-to-day:

A laptop with Chrome, Edge, or Safari and a reliable internet connection. Anything modern. A 13-inch screen is the practical minimum for the split layout; bigger is more comfortable.
A backup phone with the same browser. Useful when your laptop dies during a setup and you need to push a timeline change from the venue floor.
iPad-only: an iPad in landscape with a Magic Keyboard works well. iPad portrait alone is workable for short sessions.
Android tablet: current Chrome on a 10-inch+ tablet works. The same caveats as iPad apply.

Recommended setup for crew

Whatever phone they already have, charged. That's the entire requirement.

If the venue has weak signal, ask crew to open the link before going on-site. The page caches and stays available without a connection. See Working offline at the venue.

When something doesn't work

If a feature renders incorrectly or stops working, the first thing to try is a hard refresh (Ctrl+F5 on Windows, Cmd+Shift+R on macOS). This re-downloads the page and almost always fixes a misbehaving cache.

If it persists, try a different browser. If the page works in Chrome but not in Firefox, that's information; tell us in an email to [email protected] and we can have a look.

If the page works for you but a crew member can't open it from their phone, the issue is almost always one of: corporate Wi-Fi blocking, an in-app browser limitation, or a typo in the URL. See Resending a crew share link and Troubleshooting for the full walkthrough.