Feature
Built for the phone first
Most of the people in your chat are holding a phone. The widget is laid out for that case first and expands into the space a desktop gives it.
A phone is not a small desktop
On a narrow screen the chat takes the screen, the keyboard does not cover the composer, and the room list is a tap rather than a column.
Touch targets sized for thumbs
Everything you can press is big enough to press while walking.
It survives a lock screen
Coming back to a backgrounded tab reconnects and catches up, rather than sitting on a stale room.
How it works
One widget, three shapes
It measures the space, not the device
The layout responds to how much room it has rather than sniffing a user agent, so it is correct in a narrow column on a desktop and on a tablet held either way round.
Wide: a dock and windows side by side
The room in the panel, private conversations as windows along the bottom, up to three at once and the rest rolled up as tiles.
Narrow: one thing at a time
Windows stop being windows. The chat takes the screen and going back to the list is a step, because two 340px panels side by side on a phone is two unusable panels.
Embedded: whatever you set
An embedded room is sized by its container through your own CSS, so it fits a layout rather than imposing one.
Questions
- Is there a separate mobile version?
- No, and that is deliberate: a separate build is a second thing to keep in step, and it drifts. It is one widget that responds to the space it is given.
- What if my site is not responsive?
- The widget still is. It reads the viewport rather than your stylesheet, so it behaves correctly on a phone even on a site that does not.
- Does it work in a narrow sidebar?
- Yes. An embedded room in a 300px column uses the narrow layout, because the decision is made on available width rather than on screen size.
Put a chat on your site this afternoon
One script tag before the closing body tag. Fourteen days free, and no card until you decide.