# Orderific — A shared system for connected apps

> Components, RTL, themes, collaboration and handoff across a restaurant management platform with six connected apps.

- Reza A. Work About Contact Components
- Interfaces
- RTL
- Themes
- Handoff
# A shared system for connected apps

I strengthened components, language support, and handoff rules across a restaurant management platform with six connected apps.

- **My role:** Product Designer

- **Owned:** Components · RTL · Themes · Handoff

- **Team:** Designers · PMs · Engineers

## Outcome

A design system across six connected restaurant apps, with component detachment down from 50% to 20%.

- **50% → 20%:** component detachment after adding configurable properties

- **~25%:** fewer design–engineering review meetings over 8 weeks

- **4 → 2 weeks:** designer onboarding (3 designers)

## Key decision

Expose common variations as component properties, with shared token rules.

Rejected: Let designers keep detaching components for missing states.

## Challenge

Components had drifted across products. Missing states and inconsistent rules made reuse and handoff harder, and many apps had no RTL or tablet layouts.

## My contribution

I improved reusable components, added the missing responsive layouts, refined the BMS (brand management system) direction and theme support, and documented rules for the team.

## Reusing components

Different spacing, corners, shadows and missing states pushed designers to detach components. I added configurable properties and shared token rules, and detachment fell from 50% to 20%.

Caption: Type, state, content and helper settings are exposed in one panel. The cards below show shared controls across LTR, RTL and QR customisation.

### Add missing states

Make common variations available through component properties.

### Set shared visual rules

Use the same spacing, corners, shadows, and token structure.

### Make handoff explicit

Help engineers identify the content and states each component needs, along with references.

## Interfaces

The same component rules carry through the dashboard above, review tables, setup forms and pricing.

### Reviews

Filters, review status and actions use shared table rules.
1 / 4 Reviews Loyalty QR designer Pricing
## RTL

To meet the deadline, I built the BMS RTL screens first, using detached components. Navigation and reading order adapt, while maps and other fixed content keep their orientation.

## Themes

Figma variable modes let BMS use the same components in light and dark themes. Token values change while layout and interaction states stay consistent.

## Handoff

I documented naming and handoff rules, trained QA, and hired and mentored two junior designers to help the team apply the system consistently. I regularly worked with product managers and engineers to clarify what UI fields meant and how they connected to business rules.

### Design rules

- File and frame names
- Component changes
- Icon library
- Tokens
- Handoff stage
- Designing edge cases
- Responsive states
Caption: Shared rules for design and handoff.

The backend team maintained a data model with around 220 tables. I helped resolve mismatches and unclear links between interface fields and business data.

Caption: The guide connects shared values to semantic and component tokens, with examples the team can follow.

## System deliverables

- ~3–4 responsive layouts per app
- LTR and RTL for BMS (brand management system)
- Light and dark themes for BMS
## Team development

One of the two junior designers I mentored was promoted.

## What didn’t work

Because of time constraints, I built the RTL screens first with detached components. The dark-mode switch already existed, so turning it on switched every component to its dark variant. RTL had no matching variable property.

## What’s next

Build RTL as a component property first.
Next project · Zevian →

---

[View the visual case study](/orderific)
