Services

Five things Mayaal builds.

Every service below traces back to something in the work — not a capability deck. Where a claim has a number attached, the number is real and the project it came from is linked.

01 — Smart TV

Applications for televisions

Smart TV is a genuinely different discipline, and most teams underestimate it. There is no pointer, no keyboard worth using, no reliable network, and a rendering budget from about 2014. Every navigation decision has to survive being driven by a four-way pad from three metres away.

Mayaal has shipped on Samsung Tizen and the older Orsay SDK, and builds for LG WebOS. That covers the full lifecycle: interface design for the ten-foot experience, offline content packaging so the app works when the connection doesn't, the content pipeline your own editors run, and store submission and certification.

Proof: Manal Alalem reached 300,000 users in 19 countries and came pre-installed on new Samsung televisions across the Middle East, with a Samsung "Recommended App" listing and a top-ten position in the region.

Platforms
Samsung Tizen · Orsay SDK · LG WebOS
Covers
Ten-foot UX · offline packaging · content pipeline · store submission
Shipped
10 TV applications

02 — Mobile

Applications on both stores

Flutter gives one codebase across iOS and Android; where a project genuinely needs native, it gets native. Either way the commitment is the same — including the unglamorous last twenty percent that stops most cross-platform projects: store review, push infrastructure, offline state, and the platform differences Flutter doesn't paper over for you.

The range runs wider than it looks. Offline-first content apps that ship their entire catalogue in the bundle. Live-tracking fleet tools where a supervisor's map has to stay honest about where a vehicle actually is. Multi-sided products with a merchant app, a consumer app and an admin panel that all have to agree about one order.

Proof: Alwali Driver and Supervisor as a paired fleet system; Layalina Yummy sharing one content backend with its Smart TV edition; Mayal Food across five surfaces at once.

Stack
Flutter · Dart · Android · iOS · Firebase · REST · SQLite
Covers
Architecture · offline-first · live tracking · push · store submission
Shipped
20 mobile projects · 13 live on the stores

03 — Web

Websites and web platforms

From a company site that has to load fast and say the right thing, up to multi-sided platforms where several different kinds of user have to be served from one system without any of them seeing the others' mess.

The web work in the portfolio leans towards the second kind: a homework marketplace connecting students, teachers and bookshops; a construction-trades directory with a build-cost calculator; a city-wide directory where residents find a local business and order from it in the same session.

Proof: 6aleb as a three-sided marketplace, Moqawel as a directory with real utility built in, and Taghteat Al Hafer as a city platform with merchant onboarding.

Stack
HTML · CSS · JavaScript · PHP · Java · MySQL
Covers
Company sites · multi-sided platforms · directories · ordering flows
Always includes
An admin panel your team can run

04 — VAS

Value-added-services platform software

Mayaal builds VAS platform software for companies in the VAS business — SMS and MMS messaging engines, the web portals subscribers interact with, and the administration tooling behind both.

One thing is worth stating plainly, because the industry is full of vaguer claims: Mayaal builds and delivers the platform, it does not operate it. The companies that buy it run their own services and hold their own carrier relationships. Nothing here claims traffic, subscribers or operator integrations that belong to a client.

Software written to be handed over gets built differently. It has to be configurable rather than hard-coded, because the next client's requirements are not this one's. It has to ship with an admin panel another company's operations team can actually run. And it has to be documented well enough to survive without the people who wrote it.

Proof: the VAS platform, delivered to VAS providers to operate as their own.

Covers
SMS/MMS messaging engines · subscriber portals · admin tooling
Stack
Java · PHP · MySQL · REST APIs
Model
Built and delivered to the client — not hosted or operated by Mayaal

05 — Backend

Backends, APIs and admin panels

Every app on this site has a second half nobody sees: the APIs it talks to, the database behind those, the push infrastructure, and the administration panel somebody uses on a Tuesday morning to change a price or approve a merchant.

That admin panel is where projects quietly succeed or fail. A client who has to phone the developer to change a menu item does not have a working product. So the default is that anything an operator would reasonably want to change is changeable by them, without us.

Mayaal builds these as part of a product, and separately where a client already has apps but nothing solid underneath them.

Core
Java · PHP · REST APIs · MySQL / MariaDB · MongoDB
Also
Firebase · push notifications · file & media handling
Always
An admin panel, documented and handed over

Engagements

Three shapes that tend to work.

Mayaal takes on a small number of projects at a time, and is honest about it up front rather than three weeks in.

Full build

End-to-end delivery of a product — the model behind most of the work on this site. Scoped up front, built, submitted where stores are involved, and handed over with documentation that assumes we won't be here next year.

Design to build

You have the design finished and need it built properly. Several projects here started exactly that way. It is its own discipline: the value is fidelity to the intent, plus making the parts the design didn't cover behave sensibly.

Ongoing support

For products that are already live and need to keep moving — new features, store updates, platform changes that break things whether you planned for them or not. Retained time each month rather than a one-off project.

Not sure which one you need?

That's a normal place to start. Describe the project and the shape usually becomes obvious within one conversation.

Start a conversation See the work first