ANODA Discuss your product

Venue discovery app, both sides of the table

Glimix is a hospitality app for diners and venue owners.We redesigned it, designed its AI assistant and receipt scanner, and gave it a brand.

Glimix feed: posts from Cozy Ember and Sky Garden Rooftop, each with its rating, photo, likes and caption; Glimix venue analytics: the peak time, the visitor trend, and counts of profile visits, repeat visits, promotions and reviews
200+
screens for two roles: the diner and the venue owner
300h+
of design from the first audit to the handoff
5
experts in one pod, design and brand together
Brand
from scratch the logo, a brand book and a landing page

We redesigned Glimix’s hospitality app to connect diners’ discovery and visits with the venue team’s posts, promotions and reporting. The mobile app for both roles includes designed AI-assistant and receipt-scanning journeys. We also designed the Creator Platform, Admin Portal and a new brand with its landing page and store assets, handing the connected product to the client’s developers.

What a night out asks of the app

Both sides meet at the same venue. The diner’s path through the app, then what the venue answers with:

  1. Discover

    • Feed and live photos
    • Filters
    • Map and search

  2. Decide

    • Venue page
    • Ratings
    • Who is there now

  3. Visit

    • Check-in
    • Camera
    • Receipt

  4. Share

    • Rating and review
    • Chat
    • Loyalty rewards

  5. Ask

    • AI assistant
    • Voice
    • Past chats

  6. Run the venue

    • Posts and promotions
    • Review replies
    • Analytics
Familiar Distinctive
An app people already know how to use, with a look they remember among the other discovery apps.
Diners Venues
One product language, and neither side treated as the guest of the other.
Social posting Business rules
Posting has to feel like a social app while the schedule and the limits stay exact.

The venue’s numbers, in a reading order

Found
Every figure sat in the same outlined box on a dark screen, and check-ins and reviews had no place of their own.
Decided
One order down the screen: the period, the peak time as a plain date and hour, the visitor trend, then the counts, with promotions and reviews a tap deeper. Visitors got their own tab.
For the user
A manager checks the app between services and sees when the place is busiest, whether visits are growing and what to open next.
The earlier Glimix analytics screen: a dark background, a peak-time line chart and four outlined boxes for profile visits, maximum visits per user, total promotions and reviews
Before: the analytics screen the client came with
In the way
Light on dark in a condensed face, every number in an identical box: the eye had nowhere to start.
Redesigned Glimix analytics: Profile and Visitors tabs, the period, the peak time, the visitor trend chart and tiles for profile visits, maximum visits per user, total promotions and reviews
After: the same figures, in a reading order

  1. When

    Profile or visitors, and the period every figure below follows.

  2. The peak

    The busiest hour as a date and a time, not a point on a line.

  3. The trend

    Visits over time, with the high point marked.

  4. The counts

    Visits, repeat visits, promotions and reviews; each explains itself, the last two open their lists.

How the work progressed

From the app the client came with to a brand, a system and a handoff, one question closed at a time.

  1. Discovery

    Where the existing app lost people, and what other discovery apps had already taught them to expect

    Artifact Competitor research and an audit of the app’s screens, role by role

    The earlier Glimix app laid out for review: its dark analytics, settings and profile screens with notes on what each was missing

  2. User Flow

    What each role does from start to finish, including the ways in the app was missing

    Artifact Information architecture and flows for diners and venues

    Part of the diner information architecture: the feed with its main and live tabs and filters, mapped over the earlier screens

  3. Wireframes

    What goes on each screen, before colour and photos could hide a problem

    Artifact Wireframes and clickable prototypes for both roles

    Grey wireframe of the landing page: the hero with the app, audience cards and a video block

  4. UI & Design System

    One interface for both roles, in light and dark on the phone

    Artifact The final UI with its states, and a UI kit

    UI kit colour page: primary, grey and additional colours with their values

  5. Landing & Adaptives

    How the product explains itself to diners and to venues before either downloads it

    Artifact The landing page at desktop, tablet and mobile sizes, and its 404

    Two landing page styles side by side, a centred layout and a left-aligned one, each with its palette and reasoning

  6. Delivery

    What the client’s developers needed to build it without guessing

    Artifact Prototypes for both roles, the UI kit and an organised file

    Screens organised by flow for handoff: the feed, its filters, the selected state and the live tab

Two roles, mapped before they were drawn

Found
Sign-up and recovery had gaps for both roles, and a venue’s analytics sat inside its settings.
Decided
Every flow was mapped end to end first. Each role got its own tab bar in the same shell, with its main action in the middle.

  1. Diner sign-up and login

    Onboarding, sign-up, login and a two-step password reset, every branch drawn, social logins included.

    Open the full map
    Glimix sign-up and login flow: onboarding screens, the check for an existing account, sign-up with its fields, login, and a password reset in two steps

  2. The venue’s profile and settings

    The venue side mapped on the app the client came with, marking what each screen had to gain, from opening hours to a menu upload.

    Open the full map
    Venue profile flow on the earlier app: edit-profile screens annotated with what to add, such as opening hours, a menu upload, a phone number, a website and an address, then the settings screens
Glimix tab bars in each state, the diner’s on the left (Home, Map, Check-in, Message, Profile) and the venue’s on the right (Profile, Analytics, Add Post, Message, Settings)

One shell, two tab bars

Diners move between the feed, the map, check-in, messages and their profile; venues between their profile, analytics, a new post, messages and settings.

  • Information architecture for both roles
  • Registration and login paths
  • Role-specific navigation
  • Clickable prototypes

Five jobs the app does for both sides

The assistant and the receipt first, then finding a place, the visit itself, and the venue’s side of it.

Our mobile engagement guide connects repeat visits to useful tasks. Bring our foodtech design team the diner or venue journey that stalls before another app refresh.

An assistant that reads the diner’s own history

Found
Diners already keep a record of where they eat: check-ins, photos, notes. None of it helped them choose the next place.
Decided
An assistant inside the app: attach photos or a document and ask; get visits, favourite experiences, habits and new places to try; talk instead of typing; come back to past chats, rename or delete them.
AI Assistant with three photos and a PDF of weekend check-ins attached, and a question asking which restaurants were visited most and for similar places nearby
AI Assistant answer listing the most visited restaurants, the highest-rated experiences, the dining pattern, common feedback themes and suggested new spots
AI Assistant recording a voice message, the waveform and send button under the answer
AI Assistant history with a list of past chats, one opened as a preview with Rename and Delete actions

Receipts that turn a visit into points

Found
Loyalty points depend on a receipt, but a diner who lost it, or checks out the next day, would hit a dead end.
Decided
The receipt is optional at check-out: snap or upload it to earn points, or skip it and still check out. A receipt already used, or not from today, is flagged in place with a way to try again.
Check-out dialog for The Golden Fork with an option to take or upload a photo of the receipt to earn loyalty points
Upload Your Receipt screen with a photo of a restaurant receipt and recent photos below
Check-out dialog with the receipt photo attached and the Check-Out button
Check-out dialog with an error saying the receipt was already uploaded or is not from today

Finding a place for tonight

Found
Deciding where to go weighs the type of place, the food, the mood, the rating and the deals, and people want to see the place as it is right now.
Decided
Filters grouped the way people decide, a map of the results with a venue card one tap away, and a live tab of photos people have just posted from inside.
Feed filters with bars, restaurants and vegan and healthy selected, grouped by venue type, cuisine and ambiance
Map of the filtered venues marked with yellow pins
Map with Sky Garden Rooftop selected: its rating, address, opening hours, cuisine, a photo and a description
The Live tab of the feed, a grid of photos posted from venues

Check in, rate, come back

Found
A review helps only if it comes from a real visit, and a check-in matters only if it leads somewhere.
Decided
A check-in that asks how you’re visiting: to mingle, solo, to connect or anonymously. Then who else is there, a rating and review at check-out, and rewards that show every step to the next perk.
Check-in dialog asking how the visitor will be visiting the venue: Mingle, Solo, Connect or Anonymous
Live Visitors, a grid of people currently checked in at the venue
Rate Your Experience for The Golden Fork: four stars and a short written review
Loyalty Rewards: a free drink, a free appetizer and 10% off the next bill, each with its progress

Promoting a venue without a marketing team

Found
Venue owners know Instagram, not scheduling tools, yet their posts run on rules: every week on a set day, or between two dates, within a limit.
Decided
Posting that feels like a social app: photos and a description, then one choice, a regular post on a weekday or an extra one between two dates. Review replies and the venue’s numbers are a tab away.
New Post with the Regular Post dialog and Friday selected as the weekday
New Post with the Additional Post dialog and a start and end date
Reply to Review dialog over The Golden Fork’s reviews, with the diner’s review and a written reply
Venue analytics, Visitors tab: peak time, total and peak check-ins, profile visits, users who left reviews and the review rating

A brand drawn for the app it lives in

Found
The product needed a face that works at icon size on a home screen, beside food photography in the feed and on a poster in the street.
Decided
Every logo concept was tried where it would live, as an app icon and in the app’s header, before one was refined. The brand book then set the colour, type, imagery and store assets the product uses.
Glimix logo concepts, each shown as a wordmark, as an app icon and in an app header on a phone
Brand book page, Primary Logo: the Glimix wordmark, the app icon on a phone and posters on a wall
Brand book page, Colors: Sunlit Orange beside a halved orange, with Onyx Grey, Fresh Herb and Spiced Cherry
Brand book page, Typeface and Styles: Quicksand with its light, regular, medium and semibold styles
Brand book page, App Icon and Favicon: the Glimix icon in an App Store listing and the favicon in a browser tab over the landing page

One system for both sides of the app

Found
A venue shows up in the feed, on the map, on its own page and in its owner’s tools; if it looked different in each, neither side would trust what it saw.
Decided
One kit for both roles: the same venue card, rating, buttons and sheets everywhere, each drawn for its empty and error states, in light and dark on the phone.

A venue reads the same everywhere

Its logo, name and rating sit in the same place on a feed post and on a map card.

  • Feed post card from Cozy Ember: logo, name and rating over the photo, then likes, shares, saves and the caption
    Feed: A venue’s post.
  • Map card for Sky Garden Rooftop: logo, name and rating, then address, hours, cuisine, a photo and a description
    Map: The same venue identity on a map card.

Drawn for the moments that go wrong

No results, no reviews yet, a check-in without a venue: each says what happened and what to do next.

  • Find a Place with no results for a search and a hint to refine it
    Nothing found
  • A venue’s Reviews tab with no reviews yet and a note on encouraging feedback
    No reviews yet
  • Check-in dialog asking to choose the venue, with an error to select one before continuing
    No venue chosen

Everything around the app, in the same voice

Found
The landing page had to speak to diners and to venue owners at once, and the store listing and the deck had to look like the same product.
Decided

One brand across the landing page at every size, its 404, the store assets and the pitch deck, and the landing shows the real app rather than illustrations.

Our marketing design guide shows how ANODA connects the brand code, message hierarchy and next action before the next campaign scales.

Glimix landing page hero: a headline about the city’s best restaurants and bars, the app on a phone, store badges, and three cards for venues
Two landing sections: Where to Tonight with the feed on a phone, and Be Their Next Spot with the venue analytics
Glimix 404 page on charcoal: a message about a hidden spot not ready for visitors and a button back
The Glimix landing page on a phone: the headline, a venue card, the app, store badges and cards for venues

Store listing

The App Store page and its screenshots, each a brand colour, a promise and the real screen behind it.

Glimix App Store listing: the G icon, the Food & Drink category and the store screenshots
Store screenshot on yellow: “Find where to go tonight” over the feed
Store screenshot on charcoal: “See the place before you go” over a venue card on the map
Store screenshot on yellow: “Ask what you’ll love next” over the AI Assistant answer
Store screenshot on charcoal: “Check in, earn rewards” over the loyalty rewards
Store screenshot on yellow: “Know your busiest hour” over the venue analytics

  • Pitch deck

    Built on the brand book’s slide template, so the deck and the brand read as one.

  • Creator Platform and Admin Portal

    Web products for creators and for the team running Glimix, designed in full.

  • Social media assets

    Post and story templates in the brand’s voice.

Where the product ended up

One design for the whole product: diners find, visit and rate venues; venues post, promote and read their numbers; an AI assistant and a receipt scanner work inside both paths.

Around it, a brand from the logo up, a landing page, store assets, a pitch deck, and the Creator Platform and Admin Portal, handed to the client’s developers with prototypes and a UI kit.

screens for diners and venue owners
200+
experts in one pod
5

In the client's words

ANODA brought the product screens, identity and landing-page direction together. We appreciated the consistency between how the service is introduced and how its two user roles move through the proposed experience.

James Parkinson Founder & CEO, Glimix

5.0

Worried one side of your app will feel second-best?

In Glimix, diners and venue owners share one product language and each side sees its own jobs first. Show us both sides of yours, and we’ll show you where they should meet.

Discuss your product Explore more case studies

What we brought to Glimix

The product

The interface and the work

Read more about the design decisions

All articles