How long does app development take?
The schedule depends on the complexity of workflows, integration readiness, approvals, testing and release requirements. Ask for phased milestones rather than an unsupported universal deadline.
Can an Android app use our current website database?
Often it can use approved APIs built around the existing system. Direct database access from the phone is generally inappropriate. The backend architecture and permissions need review.
Do we need native Android or cross-platform?
Native Android can be a strong fit for Android-focused products and device-specific features. Cross-platform options deserve evaluation when additional platforms, team capacity and UI parity are important.
What happens after publishing?
Updates, compatibility reviews, crash monitoring, policy changes and support become ongoing responsibilities. Discuss them in the original project scope.
More questions worth exploring
Who owns the source code?
The development contract should specify repository access, licences, third-party rights and handover arrangements.
Do we need a backend?
Most multi-user and transactional apps need a managed source of truth and secure APIs. The scope depends on business requirements.
Is a low-cost app always a better deal?
Compare security, testing, documentation, support and change costs alongside the initial quote.
Can an app run offline?
Some tasks can be available offline when designed deliberately. Payments or centralized checks may still need connectivity.
How do we handle Google Play changes?
Review the current official Play requirements near each submission and maintain an update plan.