Sair

//WHAT EVEN IS THIS

Sair is a travel app that has the audacity to not panic you into booking something. Instead of throwing 47 filters and a sponsored listing in your face, it asks a different question how do you want to feel when you get there? It's built around a concept called Atmospheric Travel. Which is a fancy way of saying: stop selling coordinates, start selling a vibe.

//THE PROBLEM OR
(WHY EXISTING APPS ARE KIND OF UNHINGED)

Here's what mainstream travel apps are actually designed to do and I say this with full respect, make you feel like you're losing.

• You're losing the deal.

• You're losing the seat.

• You're losing time even being on the app.
  
  

~ That's not UX. That's a hostage negotiation.


The real problems were:

• Visual noise so thick you need a machete to find the destination name.

• "Search" that assumes you know exactly where you want to go (who does?).

• Zero room for "I don't know, somewhere that feels like this".

• Urgency triggers designed to short-circuit your decision-making.

~ So basically, these apps were designed for conversion. Not for humans.

//WHAT I ACTUALLY DID

I was the sole designer on this. Which means I wore every hat. The fun hat. The confusing hat.
The "why isn't this working" hat. All of them.

• UX flows and navigation architecture

• Visual storytelling & full-bleed imagery decisions

• Experimental gesture-based interactions

• Micro-interactions (the little moments that make the app feel alive)

• Developer handoff (so it could actually exist outside Figma)
  
  

//THE DESIGN MOVES

• Gesture-first navigation:
  We removed most of the buttons. I know. Wild. Swipe to explore. Pinch to pull back. It sounds scary until you use it, then going back to a grid of buttons feels like driving with a map from 2003.
  
  

• Haptics that mean something:
  Every significant interaction has a subtle physical response. Not the annoying buzz your phone does when you get a spam call. The intentional kind, a soft confirmation that says "yeah, you're in the right place."
  
  

• Slow transitions. On purpose:
  The animations are unhurried. Almost uncomfortably slow, at first. That's the point. It recalibrates your brain from "I'm in a rush" to "I'm exploring." It's basically a UX palate cleanser.
  
  

//DID IT WORK?

Yes. And here's the thing that surprised me most ….

When users spent time in the app, they weren't rushing to the booking screen. They were just... in it. Exploring places they hadn't thought about. Reading about the feeling of a destination rather than its star rating.

In a world where every app is screaming for your attention, Sair got it by staying quiet.

The prototype proved that you can have a high-engagement product without a single dark pattern.
Zero countdown timers. Zero artificial scarcity. Just good design doing its job.

// THE HARD DECISIONS NOBODY ASKS ABOUT

Discoverability vs. Minimalism , the fight that never ended.

The core tension in Sair was this: the more you hide, the calmer it feels. But hide too much and people don't know what the app does. There were screens mid-project where I'd stripped the UI down so far that
first-time users had genuinely no idea they could even search for a destination. It looked beautiful. It was completely unusable. The fix wasn't adding back buttons, it was adding intention. A single line of ambient text. A barely-there indicator. Enough to orient without enough to clutter. Getting that balance right took more iterations than I'd like to admit.


Haptics are a device problem disguised as a design problem.

I designed haptic responses for every key interaction. Felt amazing on an iPhone 14. On older Androids with weaker actuators, the same feedback felt like a broken notification. Haptic design is basically writing music and then finding out half your audience is listening through laptop speakers. The solution: at prototype stage, was to treat haptics as enhancement, never as information. If the haptic disappears, the interaction still makes sense. If it doesn't, you've built a dependency.


The gesture problem.

Gesture-based navigation sounds elegant in a presentation. In practice, gestures are invisible and invisible interactions break the moment a new user picks up the phone. We had flows where users would swipe in completely the wrong direction and end up somewhere with no obvious way back. No nav bar to rescue them. No breadcrumb. Just vibes and mild confusion.
The answer was onboarding that didn't feel like onboarding quick, ambient cues that teach the gestures while you're already using the app. Not a tutorial screen. Not a tooltip parade. Just the app

// WHERE THIS GOES

Not everything that was imagined made it into the prototype. That's just how it works — time, scope, the laws of physics. But the list of what's next? It's a good one. Social layers — travel routes shared between friends, not as itineraries but as moods. AI-curated atmospheric matching based on your listening history, your past trips, the weather where you are right now. Deeper offline capabilities for exactly the places Sair is built to send you to. Accessibility modes for sensory sensitivities. A version of this for slow travel by train. The foundation is solid. The philosophy holds.

Everything else is still ongoing. To be continued….