Mobile apps — software that works in the field, at your dealers and in your customers' pockets

Mobile app development — why, and for whom?

The decision to build a mobile app often starts with "our competitor has one, so we should too." The real question is different: which task will be done faster or more accurately on a phone than it is today? Without a clear answer to that, the app gets downloaded, opened a few times and forgotten.

In our experience, the mobile apps that create the most value are usually tied to the company's own workflow: a technician closing work orders in the field, a sales rep entering orders during a customer visit, a dealer checking stock and account balance, a customer tracking the service status of their device. What these apps have in common is that they talk to a system running behind them.

Globya has been building web, e-commerce and business software since 2000. We treat a mobile app as an extension of those systems, and the same team builds the app, the server side, the admin panel and the integrations.

iOS and Android — native or cross-platform?

There are two ways to build an app. With native development, two separate apps are written: Swift for iOS and Kotlin for Android. With a cross-platform approach (such as Flutter or React Native), a single codebase produces apps for both platforms.

For most business apps, cross-platform is the more balanced choice: one codebase, shorter development and maintenance time, and the same behavior on both platforms. In special cases that lean heavily on the camera, Bluetooth devices or demanding graphics, native may be the better fit. We make the call based on what the project needs and put the reasoning in writing. The detailed comparison is on the iOS and Android app development page.

Field, dealer and customer apps

The three types of app we build most often:

• Field app: For technical service, installation, inspection and maintenance teams — work orders, photo reports, signatures, location, and working without an internet connection (offline mode).
• Dealer app: Lets dealers place orders, see stock and prices, and follow their current account. It is often the mobile face of a B2B dealer portal.
• Customer app: Order and service tracking, appointments, loyalty programs, notifications.

These apps create value not on their own but when they work together with your ERP, CRM or e-commerce platform. That is why we handle the integration side within the same project. For scenarios and sample screens, see the field and dealer apps page.

The PWA option — maybe you don't need an app store at all

A PWA (Progressive Web App) is a web application that opens in the browser but can be added to the phone's home screen and used like an app. It needs no store approval, updates reach everyone instantly, and a single codebase runs on every device. Many features, such as notifications, offline use and camera access, are possible with a PWA today.

If your user base is well defined (employees, dealers) and being visible in the app stores isn't a goal, a PWA is often the faster and more economical route. On the other hand, there are still limits on some device features and on iOS. We compared which option makes sense in which situation on the PWA or mobile app page.

App Store and Google Play publishing

Writing the app is only part of the job; publishing it in the stores is a separate process. It includes opening developer accounts in your company's name, the privacy policy and data usage declarations, screenshots and descriptions, test builds and the review process. Store reviews sometimes mean a rejection and a resubmission; we build that into the plan from the start.

Accounts are always opened in your company's name, so you own the app. The work doesn't end at launch either: the stores require compatibility with new operating system versions every year, and user reviews need replies and crash reports need monitoring. We write these steps into the maintenance plan from day one. For the step-by-step process, read the app store publishing process page.

How we work

1. Discovery call: We listen to your needs by phone and get to know the users and the workflow.
2. Scope and decision: We recommend native, cross-platform or PWA with our reasoning and draw up the list of screens.
3. Design and prototype: We test the screens with real users through a clickable prototype.
4. Development and testing: We distribute interim builds to test users and move forward based on their feedback.
5. Launch and maintenance: We handle the store release and keep up with operating system updates and ongoing support.

KVKK compliance — KVKK being Türkiye's Personal Data Protection Law — is built into the design from the start for any personal data the app collects, at no extra charge. Pricing follows a written proposal after the discovery call. To talk it through, call +90 850 432 55 13 or write to us through the contact page.

Frequently asked questions