Should a Saudi business build for iPhone only, or launch on iPhone and Android together? +
Android holds most of the Saudi mobile market, so most consumer apps should launch on both, and Flutter or React Native can do that from one codebase. Native Swift makes sense when iPhone users drive your revenue, when the app depends on Apple Pay, HealthKit or widgets, or when an Android app already exists. We recommend one after reviewing your features and audience.
How do you handle Arabic and right-to-left layouts in SwiftUI? +
We use leading and trailing alignment instead of fixed left and right, so SwiftUI mirrors screens automatically in Arabic, and we flip only icons that show direction. Strings live in Xcode String Catalogs, dates can show Hijri alongside Gregorian, and digits follow the user's setting. Every screen is tested in Arabic on small and large iPhones.
Which payment methods can the app accept? +
Most Saudi apps combine Apple Pay with mada and credit cards through a local gateway such as Moyasar, Tap, HyperPay or PayTabs, and many add Tabby or Tamara for installments. Physical goods and services go through your gateway, while Apple requires In-App Purchase for digital content and subscriptions sold inside the app.
How does the app handle personal data under the Saudi PDPL? +
Privacy is designed into the screens with the PDPL in mind: clear consent prompts, explicit consent for sensitive data such as health information, minimal collection and encrypted Keychain storage. Face ID checks run on the device, so the app never receives biometric data. If your backend must stay in the Kingdom, it can run on a Saudi cloud region; cross-border transfers and the final legal position are for your advisers to confirm.
Can the app verify users through Nafath? +
Where your use case needs national identity verification, such as fintech onboarding, and your business is eligible, we integrate Nafath through an approved provider and your backend. For everyday sign-in, Sign in with Apple, a phone number with SMS one-time codes, or email are usually simpler for users.
Do you handle App Store submission and the Arabic store listing? +
Yes. We set up App Store Connect, signing and TestFlight, and prepare Arabic and English descriptions, screenshots, privacy details and review notes. If Apple rejects a build, we address the cited guideline and resubmit. We publish under your own Apple Developer account, so the source code and the listing stay yours.
Will the app work on iPad and with VoiceOver in Arabic? +
Yes, if you plan for it. SwiftUI layouts adapt to iPad size classes, and we test VoiceOver reading order and Dynamic Type in Arabic and English, since Arabic script often needs more line height at large sizes. Saudi government apps are held to WCAG 2.1 AA; for private apps we apply the same checks as good practice.