Mobile ordering for an 80‑location restaurant brand
I helped build and launch this guest app at Crave, working across the mobile app and shared APIs to connect ordering, payments and loyalty.
For restaurant software teams
Restaurant software & AI. Built to work together.
I help teams build ordering apps, connect POS and payments, and develop AI assistants that work with restaurant menus, documents and business data.
Umar Farooq
Software Engineer
Restaurant owner? Websites & online ordering
A closer look at my work.
Ordering apps, integrations and AI workflows I've helped build and improve.
CraveUp
From checkout to in-store operations
At Crave, I built checkout, merchant-dashboard and React Native staff-app features, including live order updates, Star and Epson printing, and Square and Clover POS integrations.
CaterVox
From catering conversations to quotes
For Crave’s catering voice assistant, I connected menus and policies, built location setup and added estimate checks. In the sandbox, conversations become saved inquiries for staff to review and quote.
Nomly
AI connected to restaurant data
I built tools for Nomly, Crave’s AI assistant, that read current restaurant menus and opening hours. They clarify the location and flag missing information, giving the assistant relevant data for its answers.
Recommendations
“His diligent personality makes you feel assured that the projects are going to be done and he gives his all. Also he is teaching and leading other junior engineers.”
Jose Miguel Navarro Iglesias
Software Engineer
Engineering in practice
The engineering behind the experience.
Integration work and production fixes, with the details behind each result.
Mobile & hardware
Receipt printing inside the staff app.
I built printer discovery, connection settings and receipt printing in the React Native staff app, including native SDK integration and error reporting.
Implemented and deployed to production.
POS integration
Connecting menus and orders to a POS.
I built catalog import and order submission, mapping menu options, prices and locations to the POS API.
A test order reached the provider dashboard; import fixes were deployed and acknowledged.
Checkout & payments
Payment succeeded. The app said it failed.
I traced the mismatch to missing checkout-session data, repaired the confirmation path and replayed the failed request in testing.
No recurrence recorded in the first two days after release.
How I work
Tell me about your projectScope
We agree on the problem, dependencies and one testable milestone.
Build & iterate
I share working builds, work through your feedback and explain what changed.
Test & release
I test the agreed flow, coordinate the release and hand over the next steps.
A delivery example
A reward-code bug, fixed that night.
I repaired a reward screen that showed an image instead of its QR code.
A colleague confirmed the fix in the released iPhone app that night.
Read the reward-code case studyUmar Farooq
Software Engineer
Based in Pakistan
About Umar
I’m Umar Farooq, a software engineer based in Pakistan. I’ve been building software professionally since 2019, with most of my experience in restaurant software.
At Crave, I’ve grown from frontend development into engineering leadership, while continuing to write and review code. My work spans ordering apps, merchant tools, POS and payment integrations, and AI tools connected to restaurant data.
Outside my product work, I mentor developers in web development and practical AI.
Can you work on an existing product?
Yes. I can work with your current codebase and team on a feature, integration or production issue. I start by understanding the existing setup and what needs to change.
Can we start with one feature or problem?
Yes. We can begin with one clearly scoped feature, integration or fix. If the cause of a problem is unclear, we can start with a focused review and agree on the next step.
How do we work across time zones?
I’m based in Pakistan. I keep progress visible through written updates and working builds, so you can review and give feedback in your own time. We agree on overlap for calls and reviews before starting.
What happens after delivery?
We agree on the handover and any follow-up support before starting. That can include setup notes, a walkthrough and a plan for ongoing fixes or improvements.
What should I send you to get started?
A few sentences about what you’re building or improving, the main problem, and any useful links. You don’t need a finished brief—I’ll review what you send and help clarify the next step.
What can I help you build or improve?
Tell me what you’re working on and where you need help. A few sentences are enough to start.
Tell me about your project
Prefer email?hello@mumar.dev