What shapes a mobile app for Lebanon
An app that assumes fast data, stable power and card payment will struggle in Lebanon. Designing for the real conditions is what makes one succeed.
| Topic | What it means for your app | Decide early |
|---|---|---|
| Data cost and download size | Users notice what an app costs them in data. A large download, or an app that fetches heavy images on every screen, is removed | A size budget for the download and for a typical session |
| Interrupted connections | A connection can fail in the middle of an order or a form. Work that vanishes at that moment is rarely repeated | Which actions are saved on the device and sent later |
| Payment as it really happens | Cash on delivery is still common. Money transfer companies and their wallets are widely used, and cards work where they are tied to accounts funded in foreign currency | The payment routes supported, and how each is confirmed in the app |
| Two currencies | Prices are usually set in dollars, and customers may pay in dollars or lira. The app has to show what is owed without ambiguity | The currency rule, agreed with your accountant |
| Customers abroad | Lebanese living overseas order for relatives, pay bills and book services at home. They use foreign phone numbers, foreign cards and other time zones | Whether the diaspora is a target, and what changes for them |
| Three languages | Arabic, English and French are all in use. Many users type Arabic in Latin letters when they search | The app's languages, and how search copes with mixed input |
| Store accounts and fees | Apple and Google require a company to enroll with documents, and their yearly fees are paid by card | That enrollment starts early, with a card the stores accept |
Workflows we build into Lebanese apps
Each of these is designed around a connection that cannot be relied on.
Order that survives a dropped connection
For delivery, retail and restaurant apps.
- Customer builds an order
- The order is saved on the phone at each step
- The connection drops and the customer continues
- The order is sent when the signal returns
- The customer sees a clear confirmation
Cash on delivery with a record
For any business whose drivers collect payment.
- Customer chooses to pay on delivery
- The amount is shown in the agreed currency
- Driver confirms collection in the driver app
- The customer receives a receipt
- The office reconciles each driver's collections
Order from abroad for someone at home
For gifts, groceries, pharmacies and services.
- Customer abroad signs in with a foreign number
- Chooses a recipient and address in Lebanon
- Pays by international card
- The recipient is notified in their language
- The sender sees delivery confirmed
Appointment with reminders
For clinics, salons and professional services.
- Customer books a time
- Receives a confirmation by notification and message
- Gets a reminder that works without opening the app
- Reschedules if needed
- The business sees the day's bookings offline
What we build
Small, efficient apps
Downloads kept compact and screens that fetch only what they need, measured against a budget throughout the build.
Offline-tolerant ordering and forms
Local saving, queued sending and plain status messages, so users always know whether something went through. Our guide to planning offline mobile app workflows explains the design choices.
Payment options that match reality
Cash on delivery with reconciliation, card payment through a provider that serves Lebanon, and transfer references where you use them.
Dual-currency display
Amounts shown under one clear rule, with the rate source your accountant specifies.
Driver and staff apps
Companion apps for delivery and branch staff, with collections, proof of delivery and a day's work available offline.
Three-language interface
Arabic, English and French, with search that understands Arabic typed in Latin letters.
What we need from you
- Who will use the app, in Lebanon and abroad
- How customers pay you today, by share if you know it
- The currency rule you apply to prices and receipts
- The systems or spreadsheets that hold orders and stock
- A person who can test builds on an ordinary phone and connection
Ownership and licensing terms are defined in the project agreement.
A readiness checklist for an app in Lebanon
Before development starts
0 of 8 checkedWhat to do next
Tell us what the app should do, how your customers pay and whether people abroad will use it. We will reply with a first release, the offline behavior we would build and the size budget we would hold to. Start a conversation or book a 30-minute call.
Not sure an app is needed? Our comparison of a PWA and a mobile app explains when a web app is enough.
Common questions
Why does app size matter so much?
Because users pay for data and have limited storage. A large app is postponed, then forgotten, and one that consumes data in use is deleted. We set a budget at the start, choose images and libraries with it in mind, and measure each build. Content that is not needed immediately is fetched later, and only on request.
What happens if the connection drops during an order?
Nothing is lost. The order is stored on the phone as it is built and sent when the connection returns, with a message telling the customer which state it is in. The server recognizes a repeated submission, so a retry does not create a second order. We test this by cutting the connection at every step.
Can the app take card payments in Lebanon?
Yes, through a payment provider that serves Lebanese merchants, for cards that work online. Many customers will still choose cash or a transfer, so the app should treat those as first-class options with proper records. Which providers are available to your business, and on what terms, is something to confirm with them and your bank.
Can relatives abroad use the app to order for family in Lebanon?
Yes, if it is designed for them. That means accepting foreign phone numbers at sign-up, international cards at payment, a recipient who differs from the payer, and notifications to both. It is a valuable group for many Lebanese businesses, and it is far easier to include from the start than to add afterwards.
