Mobile App Development

A mobile app development service designs, builds, and publishes apps for Android and iOS phones. Legia does it with a cross-platform or native approach as needed, complete with backend and security, then publishes it in your company's name.

Cost depends on the number of screens and flows, the platform and approach chosen (cross-platform or native), backend needs and integration with existing systems, and special needs such as camera, location, or on-device data storage. Legia gives the figure after the needs assessment, and that stage can be taken separately.

Native apps are built separately for Android and iOS, so they cost nearly twice as much, with the highest performance. Cross-platform apps are built once for both systems and are quicker to update. Legia chooses the approach to fit the need, cross-platform, native, or both, and explains the reasoning at the assessment stage.

A mobile app is installed from an app store and can use the phone's camera, GPS, and notifications, but needs updating to follow Android and iOS versions. A web app opens in a browser without installation and is quicker to update, but access to phone hardware is limited. Legia says which makes more sense from the first session, including when a web app is enough.

The app is published using accounts in your company's name, not Legia's. The source code, documentation, and signing files are all handed over to you, so future updates do not depend on Legia.

There are two kinds of running costs. First, developer account fees: Apple charges annually, Google is a one-time payment. Second, the cost of updating the app to follow the Android and iOS versions released each year. Without updates, an app can be rejected from the store or stop working.

Yes. Legia covers fixes for errors in its work during the warranty period agreed in the contract, followed by a subscription maintenance scheme for updates following Android and iOS versions, fixes, and server upkeep. Your internal team can also take over with the documentation handed over.

The same as web apps: role-based login, an activity log recording who changed what and when, automatic server-side backups, and security checks on the system. The scope of checks and the backup schedule are agreed at the needs assessment stage.

Yes. A mobile app needs a server and API to store data and connect its users, and Legia builds them together. If you already have a system, the app can be connected to it and the scope is assessed at the needs assessment.

That can be discussed. An app can be designed to store data on the device and sync it when a signal returns, and this need adds complexity and cost. Whether it is worthwhile for your app is determined at the needs assessment stage.

Not necessarily. Apps for employees can be distributed internally without going through the app stores, which is faster and keeps the content out of public view. For apps used by customers, publishing on the app stores is still needed.

An app with a mid-size scope generally takes 3–6 months from the needs assessment to release on the app stores. Review by Apple and Google adds a few days to a few weeks, and rejection on the first submission is common.

Changes are logged as separate requests, assessed for their impact on time and cost, then agreed before they are carried out. No extra work is done first and billed at the end.