Building WeSyria: a public-services platform, gifted to the Homs governorate

For most people in Syria, a routine government request still means a queue, a stack of paper and a day off work. WeSyria was built to put those services behind a single secure account on the phone in your pocket. We designed and built the whole platform and gifted it to the Homs governorate — not as a commercial contract, but as a contribution to a city reconnecting and rebuilding. Here is how it came together, and why we gave it away.

The problem: routine requests, in person, in line

Public services in Syria had barely any digital layer. Applying for a document, booking an appointment or following up on a request meant showing up in person, often more than once, with no way to track where things stood. The cost of that friction falls hardest on the people who can least afford to lose a day. A simple, trustworthy digital front door was missing.

Why we built it as a gift

This one wasn't an engagement with an invoice at the end. As Syria reconnects to the world, the gap between what citizens need and what's available is widest in exactly the places that have the least. We designed and built WeSyria and gifted it to the Homs governorate because we could, and because the return we cared about was a working public service, not a payment.

Discovery: one account, the heavy hitters first

Government services are a sprawl, so the discipline was choosing the few that mattered most and doing them well. We scoped the first version around a single secure login covering the requests people make again and again: official documents, appointments and the ability to track a request through to completion. A narrow, reliable first version beats a broad, fragile one — especially when trust is the whole point.

Architecture: secure, Arabic-first, built for the grid

We built WeSyria on Flutter for one iOS and Android codebase, with a Next.js web portal, a Node services layer and Postgres for the records core. Two constraints shaped everything: security, because this is citizens' official data, and resilience, because the grid and the network can't be assumed. The pieces that carry the product:

• One secure account — every service behind a single trustworthy login, not a dozen disconnected forms.
• Document requests — apply for and track official documents online instead of in a queue.
• Appointments — book a government office visit at a time that works, without the wait.
• Status tracking — follow every request through to completion, so nothing disappears into a drawer.

Design: clarity and trust, for every citizen

GovTech has the widest possible audience — every citizen, every level of digital comfort — so the bar for clarity is higher than for a consumer app. We made WeSyria Arabic-first and right-to-left from the frame, kept the language plain, and designed each flow so that someone using it for the first time, on a modest phone, could finish without help. In public services, an interface that confuses people isn't a cosmetic problem; it's a barrier to the service itself.

The outcome: delivered to Homs

Innoveev designed and built the platform and gifted it to the Homs governorate. It's the kind of work our Damascus roots make us want to do — using what we know how to build to make something concretely better for people in the region we come from.

What we'd do again

Three calls held up. Scoping to a few high-frequency services done well instead of a broad shell. Treating security and reliability as the foundation rather than a later hardening pass. And designing for the least confident user, not the most — because in GovTech, that's who the product is really for. If you are building services for the public, those are the decisions we'd tell you to get right first.