WallpaperMachine
The wallpapers you love. A new home on your Mac.
Make a quiz about the star of your party – birthday, wedding, bar mitzvah and more. Guests guess the answers from their phones while it plays on the TV. חידון מסיבה שכולם משחקים מהטלפון.
Translation pending
LifestyleTypeScript · CSSGitHub @inbar-collabOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗"Who knows the star of the night best?" A party quiz that everyone plays from their phone, in Hebrew or English.
You make a quiz about the star of your event: the birthday person, the couple, the kid, the parents-to-be. At the party, the star secretly answers each question on their phone. Every guest answers the same question on their own phone and tries to guess what the star picked. The TV reveals the answer, everyone who matched gets a point, every few questions there's a funny race to the top, and at the end a podium shows who knows the star best.
| Who | Opens | What they see |
|---|---|---|
| 🎛️ Host | the website → sign in with Google → My quizzes | All quizzes, the links to send, and each quiz's control page |
| 📺 TV | /screen/CODE | Lobby with QR code + link + code, the questions, the reveals, the leaderboard shows and the podium |
| 📱 Guests | /join/CODE (scan the QR on the TV) | Name and selfie or emoji, big answer buttons, emoji reactions to the TV |
| 🌟 The star | /star/CODE?token=… (secret link) | The question and their answers. They never see what guests picked |
Templates set the look, the fonts, the decorations, the confetti and the starter questions: 🎂 Birthday · 🎈 Kid's birthday · 🦖 Kids · 💍 Wedding · ✡️ Bar / Bat Mitzvah · 🍼 Baby shower · 🥂 Anniversary · 🪩 Party / any event.
You need free accounts on Supabase (database, sign-in, live updates, photos) and Vercel (hosting), and this code on GitHub.
Database. Create a Supabase project, then open SQL Editor → New query and run each file in supabase/migrations/ in order of their names (open the file on GitHub → Raw → copy → paste → Run). Each should say "Success. No rows returned". Developers can instead run npx supabase link --project-ref … and npx supabase db push.
Keys. In Supabase, Project Settings → API Keys / Data API:
| Supabase calls it | Environment variable |
|---|---|
Project URL (https://abcd.supabase.co) | NEXT_PUBLIC_SUPABASE_URL |
anon / Publishable key | NEXT_PUBLIC_SUPABASE_ANON_KEY |
service_role / Secret key | SUPABASE_SERVICE_ROLE_KEY ⚠️ private |
Website. In Vercel, import the GitHub repository, add those three variables plus APP_BASE_URL (your site's address, no trailing /), and deploy. Whenever you change a variable in Vercel, redeploy for it to take effect. The server region is in vercel.json (sin1, next to this project's Supabase); pick the region closest to your Supabase project.
Hosts sign in with Google to create and keep their quizzes. Guests, the TV and the star never need an account. This takes about 10 minutes, once.
A. Google Cloud: create the sign-in client
https://eventquiz-party.vercel.app.https://YOUR-PROJECT.supabase.co/auth/v1/callback (your Supabase Project URL + /auth/v1/callback).B. Supabase: connect it
https://eventquiz-party.vercel.app.https://eventquiz-party.vercel.app/** (and http://localhost:3000/** if you develop locally).Done. Open the site and click Sign in with Google.
Quizzes made before accounts existed can be added to your list: open their admin link while signed in and press Add to my quizzes, or paste the admin link at the bottom of My quizzes.
The 🤖 builder chats with you (what's the event, who's the star, who's the crowd, what kind of questions, how many) and then writes up to 30 questions plus a practice question. You untick what you don't want and create the quiz, or add them to an existing quiz from its Questions tab. It uses Google's Gemini API on the free tier.
This is the beginning of the README. Read the rest at the original. Read the full README ↗