What affects the cost, what we'll need from you and how we'll check the work.
01
Should we build a native app or a cross-platform app?
The choice depends on the app's tasks and device requirements; VMarket Digital builds native and cross-platform apps. Swift and Kotlin support native work, while React Native and Flutter can share code. An app suits a useful recurring task. If customers only need to read about your service and contact you, improving the website may come first.
02
What determines mobile app development costs?
Mobile app costs depend on the functions required, supported platforms and connections to your business systems. Device features and release preparation also affect the work. The free growth audit scopes the need before a build is proposed, so you can assess which features are necessary and discuss the responsibility for later product updates.
03
How long does an app build take, and what input do you need?
An app's schedule depends on its features, integration access and the time needed for approvals and testing. We'll need examples of the task customers perform and access to relevant systems. Someone from your business must review the behaviour as it develops. Store release requirements also belong in the schedule we agree before building.
04
Can a mobile app use our existing customer and sales systems?
Yes, an app can use existing business systems when their interfaces support the required data and actions. We check access before deciding how the integration should work. A request made in the app should reach the staff workflow that handles it, with enough context that the customer isn't asked to explain everything again.
05
How will we measure whether customers find the app useful?
We agree measures around the task the app is meant to support, including completion and repeat use where tracking allows. Downloads alone don't show that people found it useful. We look for places users abandon a task and compare app requests with business records, while making any limits in the available data explicit.
06
What should the app contract say about source code and maintenance?
The app agreement should define source code rights, store account access and responsibility for maintenance. We discuss those items alongside any third-party dependencies before the build is approved. Ask for the release handover and future update arrangements in writing, including any ongoing commitments, so your business knows who handles platform changes after launch.