Most design meetings are one person's screen and everybody else watching it.
- the weekly review of the site
- the client walkthrough a week before launch
- the handover call with whoever builds the change
- the twenty minutes that start with "can we just look at it together"
The shape is always the same. Someone shares a tab, walks the group through the site, and everybody else looks at a video of a page they can't touch. A stakeholder asks how the pricing section holds up on a phone, so the presenter drags the window narrower while ten people wait. Someone says the space under the heading is too big. Someone else writes that down.
Then the call ends and the work starts from nothing. The notes say "shorter hero, testimonials higher, the button is cramped on mobile", and whoever picks them up has to get the page back into that state, find the rule that makes the space, and work out what cramped meant.
An hour of everyone looking at the website, and the website is exactly as it was.
Everyone opens the page, not your screen
A meeting in Pixy is a link to your own site. Open Share a link, switch Live on, and anyone who opens that link lands on the page with you.
They aren't watching a stream of your screen. It's their browser, their window width, and your site's own server response, logged-in states included. When you scroll, their page follows you. When you click something on the site, the same menu opens on their side. Their chip reads Follow, so they can step out of your scroll to check something on their own and press it again to catch up.
A screen share sends everyone a picture of the page. A Live link sends them the page.
The difference shows up the moment someone asks a question you didn't plan for. On a screen share, "can you go back to the footer" is a request. Here they can just look.
A meeting still needs a time
The same card schedules it. Pick Schedule instead of Now, choose the date and time, how long it runs, and when people should be reminded. Invitees get a calendar entry with the link inside it and a mail before the hour.
The room opens before you do, so whoever arrives early can talk while they wait. Set the link to Invitees only when the page shouldn't travel past the guest list, and add an address later to send that one person their own invitation.
The camera is in the page
Microphone and Camera sit on the bar in the bottom left. Switch them on and your tile joins the strip in the bottom right, one tile per person with something on, a ring around whoever is speaking. Click a tile to make that person large. Guests get Raise hand, and Room and chat opens the drawer with everyone who is here and the chat beside the page.
The call and the work sit in one window. You install nothing, and nobody shares a screen, because everyone is already on the page.
Both switches stay off until you press them. The session runs on a link you made, and it stops for everyone from the same bar with End Live.
Decide it by changing it
This is where a screen share runs out. Somebody says the space under the heading is too big, and instead of writing it down you press ⌘⇧E, select the heading and drag its margin. Everyone watches the page change while they're still talking about it.
The gap somebody just complained about is smaller by the time they finish the sentence.
The next comment is about the page as it stands, in the real layout with the real text, not about a version everyone remembers slightly differently.
Ask what it does on a phone and pull the frame in to 390 pixels. The site's own CSS reflows through its own breakpoints, and a change made at that width belongs to that width rather than to the whole site. Try the version somebody else suggested and drop it again if nobody likes it. Only what you keep reaches your agent.
Your teammates don't need the link
The link is for the people outside the project. Everyone who works on it is together without one.
A teammate is in the room from the moment their page loads. The Here now strip shows who is on which page, and clicking a name takes you to the page they're on. Cursors, selections and edits arrive in each person's own colour, so two of you can work the same page in the same minute.
A review splits the way it actually happens. The client talks through the page, a designer moves the section, and a developer watches which rule it lands on.
Nobody has to write the notes
Every change made during the call is recorded as a change: the element, the property, the value before, the value after, and the width you were at. A decision that isn't visual becomes a comment on the element it belongs to instead of a line in a document about the page.
So the follow-up exists before the call is over. Your agent pulls the list and implements it in the code that produced the page everyone was looking at, and picking it up is one call.
After the call
The old version of this hour produced a document. Somebody had to read it, rebuild the state it described, guess at the parts that were said out loud and never written, then send a screenshot back to ask whether that was what everyone meant.
The new version produces the changes themselves. They were made in front of the people who asked for them, at the widths they asked about, on the site itself. What goes out afterwards is a link to the page rather than a picture of it.
Your next review already has a page. Open it from your projects, turn Live on, and send the link round.
Try the review on a real page.
Open this page in Pixy and try editing it live, or bring in the site your team actually reviews.