
iOS, Android and operations tools
Vehicle service marketplace
Drivers can find a garage, book car care and follow the job from their phone.
Read case studyiOS and Android
We design and build iOS and Android apps for businesses in Qatar, from bookings and marketplaces to the dashboards behind them. Explore anonymized project cases and a publicly listed app.
View app projects
The portfolio includes project screens and interactive redesign previews. Client identities are kept private.

iOS, Android and operations tools
Drivers can find a garage, book car care and follow the job from their phone.
Read case study
Mobile recruitment app
Candidates can browse vacancies, apply using one profile and track their applications. Employers can publish roles and review applicants.
Read case study
Mobile app design preview
A patient app design that puts doctor visits, physiotherapy, nursing and lab tests in one place for families arranging care at home.
Read case study
Mobile web app
Shoppers can discover offers near them, explore by category and save deals they want to revisit.
Read case study
Automotive commerce app
A marketplace demo for finding parts for Chinese vehicles, checking compatibility and comparing supplier options.
Read case studyApps your customers use to browse, book, order and get in touch.
Apps for your own staff, with the daily work of the business on a phone.
Appointments, service requests and status updates in the customer's hand.
Marketplaces that connect customers with vendors or service providers.
Field work, checklists, approvals and reporting for teams on the move.
The numbers and alerts a manager needs, on a phone.
Apps that connect to your CRM, booking tools, payment systems and internal software.
Publishing on the App Store and Google Play, and the updates that follow.
A working application often needs more than customer screens. We scope the backend, admin dashboard, user roles, service or product management, and the APIs that connect them. For a marketplace, the scope can also include vendor access and order management.
Plan the experience in Arabic and English, including layouts that read from right to left, Qatar phone numbers and prices in QAR. Map what customers do from signing up to booking or buying. We review payment gateways, Apple Pay where supported, verification codes, maps and notifications with your chosen providers.
Agree on design reviews, development milestones, testing, store submissions and support after launch. Allow time for App Store and Google Play reviews and any approvals from your providers.
A booking app, a marketplace and an internal staff app need different journeys. Start with the actions each person must complete: finding a service, choosing availability, submitting a request, accepting a job or checking progress. Our vehicle services project connects customer requests with provider dashboards and an operations layer. These examples clarify the customer and management work required in the quotation.
View case study. See JobMe on the Qatar App Store. The listing names OcttoApps Technologies W.L.L. as the developer.
Identify the developer accounts, domain, payment merchant account, messaging provider and existing systems the app will depend on. Agree who owns each account and who receives access. Testing should cover complete journeys, including failed payments, expired sessions, empty lists and unavailable services, alongside the main booking or purchase flow.
If people can create an account, plan for account deletion from the start. Apple requires users to be able to start the process within the app. For apps covered by Google Play’s policy, give users a way to request deletion in the app and on a public web page.
Agree on which records to delete, which to keep and why, and who handles requests. Check which steps depend on outside services. Test the process from registration through deletion, including confirmation, failures and records you need to keep. Make sure privacy and store disclosures reflect what the app does and which SDKs it uses.
Review the current Apple guidance on account deletion and Google Play guidance on account deletion when scoping the release.
Yes. OcttoApps develops mobile products for iOS and Android. We recommend the implementation approach after reviewing the required features, device capabilities, integrations and maintenance needs.
The cost depends on the features, user roles, design, backend, dashboards and integrations. A booking app has a different scope from a marketplace with multiple vendors. Share your requirements for a quote that lists what we will deliver and any recurring costs.
Yes. We can include an admin dashboard and payment integration in the agreed scope. Gateway onboarding, supported payment methods and transaction fees depend on the payment provider and merchant account.
The schedule depends on the agreed scope, integrations, feedback and external approvals. We define milestones after reviewing the requirements, rather than giving one delivery period for every type of application.
Publication support can be included in the project. The app must meet the stores’ requirements, and final approval is controlled by Apple and Google. Developer accounts and store fees should be identified in the quotation.
Send a short description of the business, the people using the app, the main customer journey and any systems it must connect to. Reference apps can help explain expectations. Separate launch requirements from later ideas so the quotation can define a realistic first release.
A focused first release can cover the essential customer and management journeys. Later features should be prioritised against user feedback and the operating process. We discuss that boundary before agreeing the scope, architecture and milestones.
An assessment starts with the source code, backend, developer accounts, dependencies and known issues. That review helps establish what can be retained, what needs repair and what access is required before a maintenance or redevelopment quotation is agreed.