Ricardo Freire
All work

RedUP

Mobile BI for people who run restaurants. Prototyped in Flutter, tested with KFC and Acrelec teams, and now in production.

Company
Acrelec, for KFC
Role
Senior Product Designer
Platform
iOS and Android, Flutter
Status
In production
Three RedUP screens: one store’s indicators, the list of restaurants for a national director, and a voided check
Problem

Operations don’t happen at a desk

A restaurant chain is run from the floor, the car and the next store visit. The numbers needed to be there too.

RedUP is Acrelec’s reporting product for multi-store restaurant operators. The mobile app had one job, written into the product itself: real-time operational reporting that observes and compares, and doesn’t decide for the operator.

I designed it mobile-first for KFC’s operation in France, in English and French.

My role

Design, prototype and handoff

  • Designed the app end to end: navigation, screens, states and components
  • Built the functional prototype in Flutter, with realistic simulated data, using AI-assisted development
  • Reviewed it with people from KFC and Acrelec, then adjusted the design from what they did with it
  • Wrote the specification for the order detail screen, mapping every field to Acrelec’s order data
  • Handed off directly to the development team
Decisions

One app for four kinds of operator

Decision 1

The role sets the scope, not the user

Problem
A store manager, a franchisee, a regional director and a national director ask the same questions about very different amounts of data.
Change
One app with four scopes: a single store, a group, a region or the country. The header always says whose view it is, and navigation adapts. A manager with one store doesn’t get a ranking.
Why
People shouldn’t configure a dashboard before they can read it.
RedUP header showing the role and scope, and the net sales card
The header names the role and scope. One number leads the screen: net sales, live, compared with last year.
Decision 2

Every number comes with a comparison

Problem
8,420 € in sales means nothing by itself.
Change
Each value is paired with a comparison the operator picks: last year, last week or yesterday. Color has three levels: green when up, amber for a small drop, red past three points down.
Why
Amber separates “keep an eye on it” from “act now”, which a two-color scale can’t do.
List of restaurants with sales and change against last year in green, amber and red
Restaurant list: the amber row is a small drop, the red one needs attention.
RedUP Performance tab next to the Filters sheet with period and comparison options
Left: every indicator on one screen. Right: the operator picks the period and what to compare against, last year, last week or yesterday.
Decision 3

From the country to one receipt

Problem
When a number looks wrong, the operator needs to find the cause, not just see the total.
Change
Every level opens the next: network, store, indicator, list of checks, a single check. The audit view lists voids, deleted lines and refunds, with the cashier and who authorized each one.
Why
Trust in a BI tool comes from being able to check where a number came from.
Four RedUP screens in sequence: the store list, one store, its closed checks and a voided check
Four taps from the country to the receipt: the network, one store, its closed checks, and the voided check with who authorized it.
RedUP Audit tab, net sales by store and discounts by reason code
Audit lists every void, deleted line and refund. Any indicator breaks down by store, and discounts break down by reason code.
Prototype

Testing behavior, not screens

I built the prototype as a working Flutter app. Numbers drift while the app is open, lists load as you scroll, filters and role switching work. People from KFC and Acrelec used it on their own phones.

Using it surfaced things static screens wouldn’t have. Metric cards didn’t look tappable, so people missed the detail behind them. I reworked their affordance before handoff.

RedUP Stores screen
The Stores tab. All 17 screens of the app are in Figma, rebuilt from the Flutter prototype with simulated data.
Outcome

In production

After the review rounds, the prototype and the spec went straight to the development team. RedUP is in production today.

What I’d bring from it: when the prototype behaves like the product, the handoff is a conversation about details, not about intent.