Luzit — A Social Event App for Israel's Gay Community
A social event app for Israel's gay community, designed 0→1 — where a mascot carries emotional belonging, brand identity, and the trust a new app has to earn.
Recap
- Role
- Product Designer & Founder — solo
- Owned
- end-to-end product design, 0→1 — market research · brand & visual language · mascot design & illustration direction · UX flows · UI · prototyping · marketing creative. Built solo with AI-assisted development.
- Team
- Solo. (Development is AI-assisted; earlier iterations were built with a developer.)
- Duration
- 2022–present, ongoing
- Platform
- iOS · Android · Web — Hebrew-only, RTL-first
- Tools
- Figma · Google Flow AI · Gemini image AI · Photoshop · After Effects · Claude Code
The community runs on ~100 events a month, scattered across WhatsApp groups, Instagram posts, and Facebook feeds, with no home of their own. I designed that home: a visual language built from research and led by a mascot, a feed-style calendar with a social layer supporting three types of users — participants, hosts and admins, each with his own tool set, and a guest-to-member path designed around the moments intent spikes. Live on iOS, Android, and web.
Problem
Israel's gay community runs on events — around 100 a month: drag shows, hiking groups, support circles, dinners, parties, fitness meetups, medical checkups. The supply exists and the demand exists. What's missing is the layer between them.
Events live scattered across Instagram posters, Facebook groups, WhatsApp broadcasts, host Linktrees, and one party-only ticketing site. None are built for discovery — events vanish into general feeds next to unrelated content, with no chronology, no filtering, no dedicated space. If you don't already follow the right accounts, you don't know what's happening this weekend.
The core design problem: build the home this community doesn't have — one it would actually choose over the free tools it already trusts. That's harder than it sounds, because the constraints all pull on the design at once:
- A wary audience. A brand-new, unrecognized app has to earn trust fast, against entrenched habits.
- Two users, opposite jobs. Participants discovering events; hosts running them — each with sub-segments and its own needs, inside one app.
- Guest vs. member display. Guests browse freely; signed-in users get the full, social layer, tools etc. The design has to serve both and pull the guest across the line — turning curiosity into a sign-up at the moment it peaks, without ever feeling like a wall.
- Belonging is the differentiator. The one thing generic platforms can't offer is a space that feels made for this community. If the design doesn't deliver that, there's no reason to switch.
- Order is the other differentiator — and it has to land on first launch. The whole reason to leave the feeds is that events here are organized, not chaos: a real calendar, grouped by date, easy to scan. The main screen has to make that obvious the instant the app opens — this is what you don't get anywhere else.
Research
Fieldwork
Mapped how the community shares and finds events today — dedicated Facebook and WhatsApp groups, Instagram, the ticketing site, individual host sites, Linktree. For each I asked the same set: what is the user trying to solve by using it, what are the pain points, what is the tool actually built for, and is it exclusive to this community? Alongside that I characterized the events themselves and the content that goes into them.
Segmented the audience — hosts and participants. Hosts break into sub-groups I carried through the market research and interviews to define who they are and what they need. Participants split by what they even knew existed — many knew only about parties, not the hikes, dinners, and support groups also happening. Run across ~25 host and ~30 participant interviews.
Studied the wider app category — dedicated discovery apps like Meetup, for how they solve the problem even though no one here uses them for this audience; plus visual research on gay-community apps (non-event) to learn the design language the audience already knows, so I could differentiate on purpose.
Main insights
Hosts fight for visibility. They advertise the same event across many groups and platforms, repeatedly, with no single source of truth. The three host types feel it differently:
| Host type | Volume | Additional needs | Cost | Device |
|---|---|---|---|---|
| Organizations | ~25 events/mo | Own shareable landing page + schedule + info | Mostly free | Desktop |
| Businesses | ~6 events/mo | — | Paid / ticketed | Desktop |
| Personal initiatives | ~1 event/mo | — | Usually free | Desktop / mobile |
Across all three, some events are audience-subgroup-specific (gays, lesbians, trans, etc.).
Participants work to keep up. Discovery is spread across platforms that were never built for it, so events get missed — with no one place to look. Device: mobile.
Community-specific needs the incumbents ignore:
- Privacy — welcome both closeted and out users, and handle visibility with care. The open social platforms don't.
- Inclusion — every kind of event belongs, from a board-game night to a party rave.
- Exclusivity — make the product feel like a home for this community, where people feel safe.
Discovery is visual and social now — not calendar-shaped in people's heads. People scroll the creative, forward it, react to it.
Design process
Designing a brand the gay community would trust
The research pointed at a gap no competitor filled: none of them felt like a home for the gay community. So I built the identity to do exactly that — a warm, unmistakably queer visual language that looks nothing like the generic, cluttered platforms it competes with.
A mascot: an identity that does the emotional work
At the center is a mascot: a llama named Luzit ("schedule" in Hebrew) — the app's lead identity and its messenger. The idea comes straight from my gaming background: a character does emotional work a UI can't. It lowers the barrier to an unknown brand, and triggers a reaction — warmth, a smile — before the user has evaluated a single feature.
The character flexes by audience and message while keeping the brand instantly recognizable — a playful plot-driven hook for participants; a business message carrier for hosts — carrying one voice across the app and marketing. Under it sit the quieter research-driven calls: what to foreground versus keep in the background, microcopy in the community's own voice, a layout tuned to how this audience scrolls while adhering to its pain points.
TODO(caption): The mascot in the app UI
New feed-style UX — a refresh that became a growth loop
The original calendar event list dated back to the product's launch, and it was doing a deliberate job: looking unlike the social tools where events got lost in a feed of a tool not meant for event discovery. Instead the app had an orderly, dated calendar that showed the app's organizational strength at a glance. But the app was looking stale, and with a new version being introduced, a fresh look was a reason for people to come back and see what changed. I used that as the opening to rethink discovery itself.
- Scrolling should feel like the platforms they already use. Discovery today is visual and social. I moved the calendar from full-width horizontal cards to a two-column vertical grid where the event posters take the main stage — colorful, varied, and interesting to the eye on the way down, closer to Instagram than to a list.
- The host's poster is their way to shine. It's the artwork they worked hardest on, and it's the same image they already posted on social — so the event is instantly recognizable to someone who's seen it before. Giving it a prominent stage makes the event pop, carries its atmosphere, and makes hosts happy to be on the platform.
- The grid created a new problem: the stranded card. With two columns, a day with an odd number of events leaves one card alone in a row. My solution was breather images — atmospheric illustrated tiles that fill the gap and do several jobs at once:
- Strengthen the identity — the mascot appears in scenes drawn from gay life, so the product's community identity is reinforced between the events, not just around them.
- Keep you scrolling — they're humorous, so you keep going to find the next one.
- Invite sharing — the humor creates emotional engagement people want to pass on.
- The breathers became a distribution channel. Each one doubles as a WhatsApp sticker users can install on their own device — so the character travels outside the app, into the exact channel where this community already talks, building brand awareness on its own.
TODO(caption): Before: full-width horizontal cards — orderly, but flat to scan
TODO(caption): After: a two-column grid where the host's poster takes the stage
Designing the guest-to-member conversion
Guests can browse freely — but the app is built, end to end, to turn a guest into a member at the moment their curiosity peaks. A member gains access to social features.
- Finding the conversion points. I started by mapping where intent actually spikes — working from user behaviour and the goals people come to the app with — and picked the moments worth gating.
- Two views of every screen. For each one I designed a guest view and a member view, weighing community sensibilities and privacy in the split. On web, the guest view for internal app pages carries a second job: telling the guest what the app is inviting him to experience the main calendar feature page.
- Gates that invite instead of block. Every gated action is a humorous message in the mascot's voice, tied to the intent the user just showed, with a short path to sign-up.
- Tested, not assumed. I A/B-tested the gates, running one version of a gate's art and messaging against another and keeping the one that converted better.
TODO(caption): The gate that won the test
TODO(caption): The version it was measured against
Final design
TODO(caption): Where the app opens — order, visible on first launch
Outcome
Luzit is live on iOS, Android, and web — designed 0→1 and shipped solo, from research and brand through UX, UI, and marketing creative. The three decisions above are part of a much larger product:
- a full event platform with 3 user types: host, participant & admin — each with his own tooling
- Guest + Member states
- Mobile first + web app
It's in the hands of the community it was built for.
The three design decisions increased engagement with the product and lowered the barrier with the guest versus member approach, which helped tremendously with app marketing and reception.
Reflection
- A character is a design tool, not decoration. For a wary audience meeting an unknown brand, the llama does emotional work no UI copy could — it earns a smile before the app earns trust.
- A craft fix can become a growth mechanic. The breather images started as a way to fill an odd gap in a two-column grid. Designed with intent, the same images became the app's cheapest distribution loop.
- Designing for a community means designing for belonging. Every call — the visual language, the social-feed discovery, the privacy-aware gates — traces back to one thing generic platforms can't offer: a space that feels like it's theirs.
- Test the conversion moment. Gates are easy to have opinions about and easy to A/B. I chose to measure.