All work

Offri’s Event App

A personal frustration with friends over messy event coordination, turned into a small team’s app concept - with me leading product design end-to-end.

IndependentB2CMobileCross-team CollaborationDesign to DevelopmentEnd-to-end
Role
Product Designer (research through UI)
Timeline
2023
Team
Product manager, 2 full-stack engineers
Tools
Figma, prototyping
Two phones on a pale blue surface, one showing the friends list and the other the month calendar with the next two events listed beneath it.
TL;DR

Offri’s started as a real problem: my friends and I kept losing track of event details, guest lists, and communication across group chats and spreadsheets. I partnered with a product manager and two engineers to design an event-planning app end-to-end - owning the user flow mapping, and visual design, down to UI refined through several rounds of feedback.

01Context & Role

Where this lived, and what I owned

Offri came out of a problem my friends and I kept running into ourselves: planning even a simple event meant juggling scheduling, guest lists, and updates across chats, spreadsheets, and notes, which made the process disorganized and stressful more often than it should have been. I partnered with a product manager, Ofri Yehuda, and two full-stack engineers, Aviv Shitrit and Tom Mouwes, to turn that frustration into a real app concept - the name is a nod to Ofri. I owned product design end-to-end: research and personas, the user flow map, visual and interaction design, and the prototype.

A code editor with the login screen’s Flutter source open - a LogInPage widget wiring the Google and Apple sign-in buttons to an auth service - and a phone emulator beside it running that same screen.
The handoff in practice: the login screen’s Flutter source open beside the emulator running it, with the sign-in buttons wired up.
02The Problem

Concrete pain points

  1. 01

    Coordination happened across too many tools

    Scheduling, guest lists, and updates for a single event were split across chats, spreadsheets, and notes.

  2. 02

    Guest lists and RSVPs were tracked by hand

    Invites and responses lived in group chats and spreadsheets - easy to lose track of and slow to update.

  3. 03

    Existing apps solved only half the problem

    Event platforms like Eventbrite and Meetup, and calendar tools like Google Calendar, Cozi, and TeamUp, each covered part of event planning or shared scheduling, but not both together.

03Opportunity

From problem to design opportunity

  • Coordination spread across toolsA single app that carries an event from creation through the day itself.
  • Manual guest trackingGuest lists and RSVPs built into the event, not bolted on.
  • Existing apps only cover half the jobCombine what event-planning apps and shared-calendar apps each do well into one place.
  • No quick read on what’s coming upOpen the app on a home screen that leads with your next events and where each one stands, so keeping track of the next one takes a glance instead of scrolling back through old messages.
04Personas

Who we were designing for

Persona card for Alex Chen, 28, single, a college student in San Francisco. A social butterfly who organises events on and off campus and wants to streamline his planning. Goals: communicate with friends and family with less effort, and keep up with social opportunities in his city. Challenges: juggling academic work with social commitments, and staying inside a student budget, which makes him want clarity on the cost of future events. Quoted: “Between classes, clubs, and hanging out with friends, my schedule can get pretty hectic. I’m looking for an app that makes it easy to plan events and keep track of everything going around.”
Persona card for Meggie Stevans, 31, married, an architect in Stockholm. She values collaboration and efficiency, attends design exhibitions and networks with peers. Goals: communicate with friends and family with less effort, and stay inspired and up to date with opportunities in her city. Challenges: balancing a demanding career with family commitments, and having very little time to plan and coordinate family gatherings. Quoted: “As an architect and a family person, finding the right balance between work and personal life is my constant endeavor.”
05Solution

The design, and the decisions behind it

01

Agree on the smallest useful version first

Everything felt essential at the start, and with two engineers building this alongside their own jobs, a long feature list would have meant nothing shipped at all.

Decision - Sort every idea into an MVP and a nice-to-have list with the team before any screens were designed. Creating and editing an event, RSVPs, invites, the friends list, and a feed of upcoming events made the cut; notifications, analytics, calendar sync, external ticketing and payments, and per-guest food preferences were parked.

A prioritisation board of sticky notes in two rows: an MVP row holding basic profile editing, event creation and editing, event search, RSVP functionality, inviting people, adding people to a friends list, and a feed of upcoming events; and a Nice-to-have row holding a notification system, language preferences, social sharing, comments, analytics, external ticketing and payment integrations, calendar view, and tracking attendee food preferences.
02

One flow map, start to finish

Creating an event, coordinating guests, and running the day itself had always lived in separate tools, so nothing carried context from one step to the next.

Decision - Map every screen, action, and decision a user makes across the full journey - from creating an event to the day-of schedule - as one connected flow, so the app always knows what happened before it.

The Offri flow map: onboarding and login branch through registration and password reset into the homepage, which fans out into search with price, location, host, and date filters, a nav bar leading to events, notifications, and adding an event, and a menu covering settings, profile, personal details, friends, and app info.
03

Guest coordination without the spreadsheet

Invites and RSVPs were being tracked by hand in group chats and spreadsheets, and easily got lost or went stale.

Decision - Build guest management directly into the event - invites, RSVP status, and updates all live in one place instead of a side spreadsheet.

The guest picker: a search field above 25 friends grouped alphabetically, each row an avatar, a name, and a selection circle, with a dark “(3) Done” button confirming three guests selected.
Guests are picked straight from the user’s own friends list, with a running count of who has been selected.
The attendees tab of an event, listing guests under Going (3), Not going (1), and Not responded (6), each row with the guest’s avatar and status icon.
The attendees tab answers the organizer’s real question - who is actually coming - by grouping guests into going, not going, and not responded.
04

UI interface

Event apps in this space tend to borrow visual patterns from ticketing, messaging, and calendar apps all at once, which made most of them feel busy.

Decision - Settle on a single, monochromatic, minimalist visual language, refined over several rounds of feedback with the team, so the interface stayed calm no matter how much event detail it held. Colour earns its place in exactly one job: soft pink and green to mark whether a guest is coming.

The Offri UI kit: button states, guest-row states from add through pending to removed, an event card, the going / not going / not decided status chips, and an avatar size scale.

Ink

#000000

Surface

#FEFEFE

Surface muted

#F1F1F1

Neutral

#D9D9D9

Going

#D5F1C3

Not going

#F1C3C3

06Reflection

What I took away

  • 01

    This was the first time I worked alongside a product manager and engineers, and it changed how I scoped the work - I was designing for what could actually get built, not just for what looked good in Figma.

  • 02

    Studying five existing apps side by side made the gap obvious: event tools and calendar tools solve adjacent problems, but almost none combine them.

  • 03

    Committing to one flow map before touching visual design kept the guest and scheduling features connected instead of bolted on separately.

  • 04

    A minimalist, monochromatic UI held up well under real event detail - simplicity did more work than any single feature.

07Prototype

The experience

  • The splash screen: the Offri’s wordmark reversed out of near-black.
  • The login screen, offering sign-in with Google or Apple.
  • The home screen: a greeting, a count of upcoming events, a search field, and event cards each carrying an RSVP chip.
  • The calendar view: a month grid with event days marked, and the next events listed beneath it.
  • The first step of creating an event, asking for a name for the gathering.
  • The event details step: title with an emoji picker, date, time, duration, place, and description.
  • The guest picker: friends listed alphabetically with selection circles and a running count on the Done button.
  • Three guests selected, with bulk add and remove actions, a payment option toggle, and a co-host chosen.
  • The same step with an empty guest list, prompting the user to select from their friends list.
  • Finding friends by name, each result showing whether they can be added, are already added, or are pending.
  • The find-friends screen before a name has been typed.
  • An event seen by a guest who has declined, showing “You are not going” and an option to change their mind.
  • The same event awaiting a response, with a prominent RSVP button.
  • The same event once accepted, confirming “You are going!”.
  • The attendees tab, grouping guests into going, not going, and not responded.
  • The preferences tab, where a guest sets dietary needs, a plus-one, whether they can help prepare, and update settings.
  • The notifications feed: RSVP changes, invitations, and approvals, split into new and earlier today.
  • The notifications screen with nothing waiting.
  • The friends list with a search field and an add-friend action.
  • The profile screen: avatar, full name, email address, and birthday.
  • Profile settings, including notification and friend-request approval toggles, logout, and account deletion.
  • The help centre menu, linking to events, the friends list, settings, FAQs, and contact.
  • A step-by-step guide to creating an event, written out inside the help centre.
  • The about screen, crediting the team behind the app and its version number.
  • The 404 screen, apologising and offering a support address.
Turn sound on

The prototype showcases the app’s minimalist design and user-friendly interface, giving a clear demonstration of how it works and how it feels to move through.

Open the Figma file

© Designed & built by Lior Shitrit with AI tools.