AS Amr Shbib Solution Architect
CV

Solution Architect · Engineering Lead · Available for advisory & lead engagements

Transforming business ideas
into scalable apps, software & websites.

I'm Amr Shbib — Solution Architect, Engineering Lead, and React Native Expert. I architect and ship production-grade apps, software, and websites end-to-end — across mobile (iOS / Android / React Native), web, desktop (Electron), and backend (Node.js / Laravel). I lead teams, design the systems, write the hardest native modules myself, and turn vague business ideas into products that actually ship.

See selected work Book a consult
  • 8Years building production apps
  • 30+Apps shipped to App Store & Play
  • 6Open-source NPM libraries
  • 1In-house MDM platform replacing SOTI / Intune
01 — About

An engineer who learned to lead, a leader who still writes the hardest code.

I started 8 years ago as a React Native developer in Damascus. I've since shipped delivery platforms in the UAE, fashion & commerce in Saudi Arabia, fintech in Riyadh, outdoor-tourism in Lebanon, and the entire MyThings stack in Jordan. Along the way I kept getting handed the same kind of problem: turn a vague business idea into a system that actually runs.

Today I lead mobile at MyThings — a Jordanian delivery platform. My team and I designed and built the customer, partner, driver, admin, analytics, ticketing, chat and (most recently) a complete Mobile Device Management platform, end-to-end and in-house.

I'm a working architect, not a powerpoint architect. I write the Swift / Kotlin native modules myself, ship the hard release that everyone else is scared of, and still spend most of my week unblocking engineers — code reviews, design docs, hiring, roadmaps, estimates, conversations with clients.

02 — What I Do

End-to-end ownership across the product lifecycle.

From the first whiteboard conversation to the production-on-call rotation — here's where I'm useful.

03 — Leadership

How I lead — multiply engineers, protect focus, ship.

A

Team management

I run a tight mobile team across iOS, Android and web. 1:1s, performance, growth planning, hiring. Career paths that aren't accidents.

B

Mentorship

Pairing on hard bugs, walking juniors through architecture trade-offs, weekly tech reviews. Engineers leave my team better than they joined.

C

Code reviews & standards

Reviews that teach, not gate-keep. Linting / formatting / type-safety baselines that catch the easy stuff so reviews can focus on design.

D

Technical ownership

When a release is on fire I'm in the trench. The hardest native modules, the gnarliest production debugs — I do the work I expect.

E

Release management

Staged rollouts via CodePush + App Center + Fastlane. Dev / staging / prod lanes. Instant rollback when something looks off in the field.

F

Agile, with judgement

Lightweight Scrum / Kanban. Sprint planning that's about outcomes, not story-point theatre. Estimates I'm willing to commit to in writing.

G

Client & stakeholder comms

Translating between product, business, and engineering — without translation losses. Proposals, scope docs, and weekly status the room can act on.

H

Cost & roadmap planning

Estimates grounded in real teams and real velocity. Roadmaps that show what gets cut, not just what gets built.

04 — Architecture & System Design

Systems I've actually designed and shipped.

Not bullet-point architecture. Real platforms that survive production weather.

05 — AI Engineering

Production AI work — Claude, custom agents, and skills.

Not slides. Real shipped agents, custom Claude Code skills, MCP integrations, and LLM features running in production.

06 — Projects

Selected production work — 8 years of shipped platforms.

Filter by type. Tap "View Details" to see the app in action.

07 — Case Studies

Two deep dives into platforms I'm proud of.

Case Study · MDM Platform

Building Our Own MDM — replacing $720K/yr of SaaS.

In-house · 2025

A year ago MyThings was about to pay six figures annually to rent the platform managing devices we already owned. SOTI MobiControl, Microsoft Intune, VMware Workspace ONE — all want $2–$12 per device per month. A 5,000-device fleet pays up to $720,000 every year just to stay in control.

Every expert said buy. We decided to build. Not out of recklessness — because we'd seen what our team could do. We owned customer, partner, driver, admin, analytics, ticketing and chat already. An MDM was just the next thing.

Today our in-house MDM runs the entire delivery-device fleet: kiosk lock-down, real-time telemetry, fleet-wide OTA in minutes, instant remote wipe — all from a single control plane. Zero third-party vendors in the stack. Built by Jordanian hands, owned by MyThings.

$720KAnnual saving at our scale
$25BGlobal MDM market by 2030
0Third-party vendors
100%In-house, in-team
  • Single control planeEvery operational device managed from one dashboard.
  • Locked Kiosk ModeRestricted to operational apps only — no detours.
  • Real-time telemetryBattery, connectivity, location, performance — streaming live.
  • Fleet-wide OTAPush updates to thousands of devices in minutes.
  • Remote wipeLost or stolen device — wiped instantly from anywhere.
  • End-to-end ownershipDevice security, network protocols, distributed systems — ours.
"MyThings is not a device-management company. We're a delivery company — but our engineering team refused to place limits on what they could build."
Case Study · MyThings Ecosystem

One platform, four apps, one team — full-stack ownership of a national delivery service.

2022 → today

Took the MyThings mobile org from "we contract things out" to a self-sufficient team that ships every layer of the stack. The ecosystem now spans four production apps — Customer, Partner, Driver, Admin — backed by a backend, an analytics stack, an internal ticketing system, and an in-house live chat.

Drove the architecture: a shared design system, shared native-module layer (HMAC signer, background location, scanner SDK), staged release pipeline with CodePush + Fastlane, and a single observability + crash pipeline across all four apps.

4Production mobile apps
1Shared native-module layer
DailyOTA releases via CodePush
FullIn-house engineering
  • Shared design systemOne token set, four apps, two platforms — visual consistency by default.
  • Native-module layerHMAC, background location, scanner SDK — reused across the fleet.
  • Staged release pipelineDev / staging / prod via CodePush + App Center + Fastlane.
  • ObservabilityOne Firebase / Crashlytics / Sentry pipeline across all four apps.
08 — Professional Experience

The roles that shaped how I build.

    Bachelor of Science, Information Technology

    2015 — 2020 · Arab International University

    Specialization in Artificial Intelligence · AGPA 2.9.

    ICPC · 7th Place

    2017 — 2018

    Syrian Private Universities Collegiate Programming Contest.

    09 — Tech Stack

    What's in my actual production stack.

    Each chip below is something I've shipped — not something I read about.

    10 — Achievements

    Highlights from 8 years of shipping.

    Open-source — 6 NPM libraries

    Maintained packages used in production by my own apps and teams elsewhere.

    11 — Contact

    Let's build something worth shipping.

    Lead, architect, advisor — full-time or fractional. Always happy to chat about hard problems.

    Opens your mail app with the message pre-filled — usually I respond within a working day.