How a guest orders ahead in the Majan iPhone app
Majan is a coffee shop in Saint Petersburg. We built its native iOS app in SwiftUI, along with the server that connects orders and loyalty to the shop’s iiko point-of-sale system. A guest can browse the menu before signing in. When they order, they choose pickup as soon as possible or select a time in 15-minute steps.

These screens show a demo order. The prices and sold-out items come from the till. The barista receives the order, and the guest gets a notification when the drink is ready. Payment happens at the counter. The app was released on 29 October 2026. Read the Majan case or view the app in the Russian App Store.
What should a restaurant app include in its first release?
For a Dubai café, start by deciding which job brings guests back to the app. Ordering ahead means the barista must see the pickup time. A digital loyalty card means staff need to award a stamp and recognise a reward at the counter. At Majan, the barista scans the guest’s QR code and every fourth drink is free. A different venue can choose its own rule.
| Decision for your venue |
What we agree before development |
| Menu and availability |
Which system owns prices and sold-out items? Do branches have different menus? |
| Pickup orders |
Who accepts an order, and what does the guest see if the chosen time becomes unavailable? |
| Payment |
Will the guest pay at collection or in the app? Which provider and refund process would an in-app payment need? |
| Loyalty |
What earns a reward, who can redeem it, and how will the team handle an accidental second scan? |
What goes into the estimate for a custom iOS app?
We quote from the customer journey and the work it creates behind the counter or in your office. A catalogue that lets people browse is one scope. Adding orders introduces customer accounts, order states and a connection to the team fulfilling them. A second branch changes the estimate again if it has its own menu, opening hours or staff permissions.
The proposal identifies which screens and integrations belong in version one, what access your team will provide, and what each side will test before release. If customers need Arabic, we scope native-speaker proofreading and check the right-to-left screens on iPhone. Staff tools can use English when that fits the people working with them.
How do we prepare for the App Store?
Before building, we agree who will publish the app, which countries it should be available in and who will manage updates. We plan time for testing on iPhone, store screenshots and review. For Majan, our work included the store listing, account deletion and demo access for Apple’s reviewer.
For a UAE launch, we check the selected storefront with the publisher and test the customer journey for that release. Apple reviews the submitted build and listing. Apple’s guide to App Store availability
What should you send for an estimate?
Describe one action your customer needs to complete and what should happen on your side afterwards. Include your existing website, the name of any POS or booking system, the languages you need and your intended launch date. Our iOS app brief includes a worked pickup example and a space to flag what happens if an order fails.
If customers can complete the whole task from a link, explore web application development. For a public menu, offer or enquiry form, see our website design and development service.