Ongoing mission at SaaS Office: the design system shared by the mobile app and the web interface, key journeys, prototypes and part of the front-end integration.

SaaS Office
  • +10kRegular users
  • −40%Lower drop-off
  • +60Documented components

The platform

An app for office buildings.

SaaS Office publishes a platform that brings together an office building’s services: meeting rooms, catering, concierge, incidents.

Occupants use the mobile app, and each property manager gets a web interface in its own colors.

Web tenant portal in Praemia REIM colors

Trade-off

One app for everyone, or one interface per use?

The product serves four audiences with different needs and different devices: occupants, property managers, service providers and visitors.

Ruled out

A single app with role-based access

One product to maintain. But occupants would have inherited management screens, and visitors would have needed an account to get through reception.

Chosen

One interface per use

The mobile app for occupants, a web console for property managers and service providers, and an account-free QR code for visitors.

In return, three interfaces had to evolve in parallel without drifting apart. That’s what made the shared design system essential: the same tokens and components everywhere, with one theme per client.

Mobile app

Badge and rooms first.

Badging in and booking a room are what occupants do every day, so they’re at the top of the home screen. The directory and the concierge are one step further.

A reported incident can be followed in the app, without going back through the building’s front desk.

Home, assisted booking and request tracking in the mobile app

Design system

One design system for web and mobile.

Web and mobile had grown up separately, each with its own components and little habits. I brought them together in a single design system, starting with tokens, then components, documented in Figma with all their states.

Along the way, I reworked the contrast: several grays and the blue used for prices didn’t meet AA. I darkened them to the threshold, no further.

The web and mobile teams now work from the same mockups. A new feature is designed once, for both.

Design system foundations: colors, type, spacing, radii and contrast audit

With the team

With PMs and developers.

Decisions are made in workshops with PMs and developers, then we ship sprint by sprint, with a demo each time.

I also get my hands into the code (HTML, CSS, JS) when it helps. If a mockup doesn’t hold up for real, I see it before the developers do.

Room booking and restaurant list in the mobile app

On the SaaS Office apps, a memorable encounter, both personally and professionally. An expert, one of those who make complicated things look simple. The Design System he created for our apps changed everything: look and feel, navigation, but above all the ability to maintain and evolve our web and mobile apps quickly. Pragmatic, respectful of time and resource constraints, he fits right into dev teams. In short, a game changer.

Renaud DecondeChief Engineer · SaaS Office