Baqati


Plan, data, minutes, the bill and roaming, all before the first scroll.
Loading Mowgoud.
Getting everything ready before you enter.
The Omantel super app: customer home variants, planned utility payments, sign-in and top-up flows, and the design system underneath them.



Balance, bills, top-ups and roaming lead the home, with offers, rewards and shopping below. The first row changes with the customer’s account.
Omantel’s customers do not share one relationship with the company. Some pay a monthly plan, some top up a prepaid line, some only know it as the router at home. The super app had to welcome all of them on the same home screen, and not make any of them dig for the thing they came to do.
The work shown comes from the design files: home variants, sign-in and top-up flows, colour tokens and component documentation. The selected screens use different sample accounts and navigation labels.
Baqati, Hayyak and home broadband (HBB) adapt the shared home to different Omantel accounts. The planned Nama (نماء) integration would also let users pay their water bills through the app.


Plan, data, minutes, the bill and roaming, all before the first scroll.


Prepaid first: the available balance and its Top up button sit in the first row.


Home broadband gets two cards and no more: the bill and the speed of the plan.
The home prioritises account tasks, then services, offers and rewards.


A greeting, the number you are on with a switch for your other lines, and two doors that never move: notifications, and Noor, the assistant.
The answer is the first thing on screen. Plan, data, minutes, a bill, roaming: each card carries the one button that acts on it, and the row scrolls sideways for more.
Six services as tiles, each an icon and a short label: utility payments, roaming, credit transfer, insurance, shop and home broadband. View all opens the rest.
Offers in a sideways rail. Image first, a line of copy, one orange arrow to act on it.
Makasib rewards, filtered by what you like: food and drink, travel, shops and services, fashion, beauty, gifts and electronics. A logo, the discount, the partner.
Five tabs connect Home, All services, Payments, Makasib and Settings.
A telco already knows your number, so sign-in leans on it. One field, one code, and the home that opens already knows your plan.

Log in, join Omantel, or use guest services without an account. The Arabic switch is on the first screen, not buried in settings.


One field: your Omantel number. Apple, Google and email are there for people who would rather use them.


Four boxes for the code sent to the number you typed, a visible resend timer, and Continue pinned to the bottom.

And you land on a home that already knows who you are and what you pay.
People reach top-up from three places: a quick action on the home screen, the Payments section when they top up several numbers, and the welcome screen without logging in.
The map groups entry points, related options and card-payment stages. The screens below focus on card payment; voucher redemption is shown separately.

A big number, a keypad and quick amounts.

The selected amount stays prominent, with the current balance above the confirmation action.

The number, the amount and the total, on one screen, before money moves.

Saved cards or a new one, in a bottom sheet over the overlay.

The bank asks for its own code, in the same visual language.

The new balance, and what you might want to do next.

When it fails it says so plainly and offers a way back.
Voucher scanning, saved numbers and guest access appear alongside the card-payment states in the design files.






The palette uses six token ramps of ten steps. Orange marks actions and blue carries the brand. The contrast ratios shown here are calculated for this portfolio page against white and black text.
The values are the tokens from the design system; the contrast ratings are computed on this page.
The headless approach separates component structure and interaction rules from visual styling, with tokens defining the visual layer. An atomic approach builds larger patterns and screens from small, reusable parts. The tab group below shows how those shared rules support different levels, widths and states, alongside usage guidance and an interactive example rebuilt for this page.


Tab group / Horizontal — Auto
Default · Hover · Pressed · Disabled — hover and press the tabs to see them.

The same components support different account priorities, while shared payment patterns keep the top-up routes consistent. Documented states and colour tokens give those variants a common set of rules.
Ahmed Mowgoud — UI design, UX flows & design system
Publicis Sapient — agency
Omantel — client