Skip to content
Smart Lead Tech
Home
Services
Our work
Saudi Arabia
About us
Blog
Contact us
🇸🇦العربيةContact now
Smart Lead Tech

Smart software solutions

Follow us

Company

  • About us
  • Our work
  • Our services
  • Saudi Arabia
  • Restaurant POS
  • Contact us
  • Book a call

Quick links

  • Blogs
  • Pricing
  • Refund policy
  • Privacy policy
  • Terms and conditions
  • Data deletion

Contact us

  • Egypt — Head Office

    Office 6, Bldg 23, Makkah Al-Mukarramah St., Omraneya, Giza 3540203, Egypt
  • Saudi Arabia — Branch

    Bldg 2646, Secondary 123, Street 7697, Ishbiliyah Dist., Jubail 35416, Kingdom of Saudi Arabia
  • Email address

    help@smartleadtech.com
  • Phone number 🇪🇬

    +20 102 201 4671
  • Phone number 🇸🇦

    +966 53 044 7112

© 2026 Smart Lead Tech. All rights reserved.

  • Smart Lead Tech Information Technology LLC·Commercial Register ⁦61239⁩·Tax ID ⁦774-391-316⁩

  • Smart Lead Tech Software Establishment·CR ⁦7054902585⁩·VAT

One codebase from the cashier to a salon marketplace: 10 lessons from two years of Flutter

The TtaKkaa ecosystem alone is four apps: cashier, kitchen display, customer app and store dashboard. Add Beauty Map and Home Beauty for beauty services, and Meshareeb for beverage delivery in Kuwait. All Flutter. Here a…

02/24/2026 — 8 min read

Three devices — a cashier terminal, a kitchen display and a customer phone — running one Flutter codebase

The TtaKkaa ecosystem alone is four apps: cashier, kitchen display, customer app and store dashboard. Add Beauty Map and Home Beauty for beauty services, and Meshareeb for beverage delivery in Kuwait. All Flutter. Here are ten lessons you will not find in the docs.

1. “Offline first” is not optional in point of sale

Restaurant internet drops at the lunch peak. TtaKkaa Cashier completes the order locally, prints, and syncs later with clear conflict resolution. Had we built it “online, then add offline” we would have rewritten it.

2. The kitchen display is a different app even if it shares code

A KDS is not touched; it is read from two metres away. Huge type, high contrast, exactly three colour states. We shared the data layer and models, and not a single widget.

3. Four languages mean four directions of thinking

The TtaKkaa Store dashboard supports four languages. The lesson: never write left or right; only start and end, and test Arabic and Urdu together because they break different assumptions.

4. Maps need a strategy, not a library

In Beauty Map (a women’s salons directory) and Home Beauty (at-home beauty services) the map is the product. Marker clustering, viewport-based loading and tile caching are early decisions that determine whether the app works on a mid-range phone.

5. Payments are built once and wrapped well

One payment module supports Gulf and Egyptian providers behind a single interface. Meshareeb and TtaKkaa Customer use the same module, and any new provider is added in one place.

6. Thermal printing is a small hell — isolate it

Printers differ, and their protocols are older than the team. An independent print layer with a simple interface and recorded fixtures for every model we run. Never let the printer touch order logic.

7. State: few tools, much discipline

We chose one state-management solution and stuck with it across every app. Switching tools cost an older project a whole month without a single feature.

8. Performance is measured on the cheapest device your customers use

We keep an old Android phone in the office named “the real customer”. Every release runs on it first. Meshareeb in Kuwait runs on drivers’ phones, not developers’ phones.

9. Real-time orders: WebSocket with a fallback plan

An order appears in the kitchen within a second over WebSocket, and when the connection drops it falls back to polling without the chef noticing. The silent fallback is the feature.

10. On-device AI starts small

The first smart feature in Home Beauty was suggesting the best appointment slot from a client’s booking pattern — a tiny model running on the device, no data leaving the phone. It worked because it was small and clear, not because it was “smart”.

Flutter is a promise of one codebase. Keeping the promise comes from the layers you separate wisely, not the code you share enthusiastically.

Share

Projects related to this article

  • AI SystemsPythonNext.jsDocker

    SLT OCR — Arabic-first Document Data Extraction

    An Arabic-first computer-vision engine that turns invoices, purchase orders, receipts, ID cards and KYC packs into data you can trust — a verification model per field, human review when needed, processed in memory only.

    Show more
    SLT OCR — product landing on desktop and phone
  • POS SystemsFlutter

    TtaKkaa Cashier — Restaurant POS Suite

    End-to-end POS for restaurants & cafés: tables, kitchen, inventory, live reports.

    Show more
    TtaKkaa Cashier POS application screen
  • POS SystemsFlutter

    TtaKkaa Kitchen — Restaurant Kitchen Display Suite

    A professional Kitchen Display System (KDS) for real-time order flow: display, prep and dispatch — synchronised over WebSockets.

    Show more
    TtaKkaa Kitchen System — chef-facing order display

Related Blogs

  • Flutter-built POS application

    Flutter for POS systems: offline-first done right

    POS apps do not run in perfect conditions. The internet drops, power cycles, and the branch still must sell. This note captures the pattern we use on TtaKkaa Cashier to keep operations smooth regardless of connectivity.T…

    11/05/2024 — 8 min read

  • Scalable NestJS architecture

    Scalable NestJS architecture — from module to monorepo

    Our large NestJS projects start as "one app with modules". Today anything with more than ten modules lives inside a monorepo. This note explains when we make each leap and what the team gains from it.Stage 1: Single app …

    10/18/2024 — 10 min read

  • Pragmatic SOLID in Laravel 11

    Clean repositories and services in Laravel 11 — pragmatic SOLID

    Everything here comes from shipping dozens of real-customer APIs. The goal is not "SOLID for its own sake"; it is two things: testable code and clear layers that never mix.The layer cake we default toRoute: endpoint name…

    12/14/2024 — 13 min read