The App or the Browser? Two Ways to Run a Meeting Room Panel
There are two ways to put a room panel on a wall, and the difference between them is smaller than people expect.
One is the app, installed on a tablet. The other is the browser, opened on any screen that already has one: a spare PC driving a display, a thin client, an old tablet in kiosk mode, a lobby screen somebody bought for a purpose nobody remembers.
Both show the same panel. Both take the same actions. Both obey the same plan rules and the same settings. What separates them is a short list of things a browser cannot do, and one habit that will un-pair a browser panel if nobody thinks about it.
Below, we discuss what is identical, what is not, and which to use where.
What Is the Same
Almost everything.
The browser panel is the same front end, not a cut-down version of it. Live status, the room name and capacity, the current meeting, what is booked next, and the whole of today's agenda. Booking at the door, check-in, extend and end, exactly as the app offers them.
The rules are identical too. Whether a panel shows buttons depends on your plan and on whether that device is set to interactive, and those apply the same way in a browser as in the app. Pairing works the same way, with a code generated in the administration site.
So a browser panel is not a compromise on function. If somebody is standing in front of it, they cannot tell.
What Is Different
Four things, and only the first two are about capability.
No status light. There is no hardware to drive, so a browser panel cannot show a corridor-visible colour. On a screen that people read from two metres away this does not matter. On a long corridor where the whole point is reading eleven doors from the lift lobby, it does.
No battery reporting. A browser panel shows a dash rather than a percentage, permanently, and it never raises a low battery alert. That is deliberate rather than an oversight: the browser interface for it is not reliable across browsers, and a partial answer would be worse than none. The consequence is practical. If you run a browser panel on an old tablet on its own battery, nothing will warn you before it dies. Give browser panels permanent power.
The identity lives in the browser. This is the one that catches people. A browser panel's pairing is stored in that browser on that machine. Anything that clears site data sends the panel back to the pairing screen and needs a fresh code: a cleanup policy, an overnight kiosk reset script, somebody being helpful with a browser's clear-history button. Never run one in a private or incognito window, which loses the identity the moment it closes.
Nothing restarts it. The app comes back after a reboot. A browser does not, unless your operating system or kiosk software reopens it at the right address in full screen. Screen savers and sleep settings apply too, and both have to be turned off on the host machine.
One setup detail follows from all of this: the device record has to be created as a browser device. A record made for a tablet will not pair from a browser, and the app will not pair into a record made for a browser. It is not a setting you can change your mind about halfway through.
Comparison
The app on a tablet | The browser panel | |
|---|---|---|
Status, agenda, booking, check-in, extend, end | Yes | Yes |
Plan rules and interactive mode | Same | Same |
Corridor-visible status light | On supported hardware | No |
Battery reporting and low battery alerts | Yes | No |
Launch on reboot | Yes | Only if something reopens it |
Survives site data being cleared | Not applicable | No, needs re-pairing |
Which to Use Where
Use the app at meeting room doors. That is where the status light earns its place, where battery reporting matters because the device is often on a wall away from a socket, and where you least want a panel that needs somebody to restart it.
Use the browser for screens you already own. A lobby or reception display showing one room's day. An overflow screen in a corridor. A spare PC in a shared area. In all of those the screen exists already, it is on permanent power, and nobody needs a light bar to read it from the far end of the building.
Use the browser to try the idea. This is the underrated one. You can put a real panel on a real door, reading your real calendar, on hardware you already have, before you order anything at all. Not a demo and not a video. Two weeks of your own corridor telling you whether this changes anything.
That matters because the expensive decisions in a room display project come early. Which hardware, how many doors, what cabling. Being able to validate the whole idea for nothing first is the cheapest insurance available, and most organisations do not realise it is on the table.
Wrapping Up
The browser panel is not the lesser option. It is the same product on hardware you have not had to buy, with three limits you can design around and one you have to remember.
Take a recruitment firm with six meeting rooms who were not convinced any of this would change behaviour. Rather than approve a hardware order, they put the browser panel on a spare PC driving a monitor outside their busiest room and left it for a fortnight. The panel did everything the tablets would have done. What it proved was not that the software worked, but that people used it: bookings at the door, check-ins, and a noticeable drop in the complaint that there was never anywhere to meet. The hardware order went through the following week, for the app on tablets at every door, because by then nobody needed convincing.
Start in the browser if you want to find out. Move to the app when you want the light bar and the battery warning.
Frequently Asked Questions
Is the browser panel a cut-down version of the app?
No. It shows the same panel and offers the same actions, under the same plan rules and the same interactive mode setting.
What can the app do that the browser cannot?
Drive a corridor-visible status light, report battery charge and raise low battery alerts, and come back on its own after a reboot.
Can I switch a device from the app to the browser later?
Yes. But you will need to pair it again.
What should we use for a lobby screen?
The browser, almost always. The screen usually exists already, it is on permanent power, and nobody reads a lobby display from the end of a corridor.
Can we trial the product without buying hardware?
Yes, and it is the best reason to use the browser panel. Put it on a spare screen outside your busiest room, connected to your real calendar, and watch what happens for a fortnight.
