A useful cost discussion starts with what the application must achieve, not an unverified rupees-per-screen promise.
Scope and roles
Estimate separately for customers, staff, managers and administrators. Each distinct permission set, approval flow and exceptional case adds specification and testing work.
Integration depth
A standalone catalogue differs from an app connected to inventory, CRM, payment collection or distributor accounts. Ask who provides usable API documentation and test data.
Practical lens: The best decision depends on users, the existing business system, data risk and the outcome the app needs to deliver. Validate these conditions before committing to features.
One-time and recurring costs
Separate discovery, UX, implementation and testing from hosting, licences, store charges, monitoring and planned updates. An apparently low quote can omit critical lifecycle work.
Compare like with like
Request an itemised scope, milestones, acceptance conditions, handover, warranty boundaries and a change-request process before comparing vendors.
Example from a business workflow
A field-sales app with offline order drafts will generally need more integration testing than a brochure-style application, even when it has fewer screens.
Questions to take into your project discussion
Turn the guidance into a brief by confirming each of these items with the people responsible for the product:
- User journeys and roles
- External API responsibilities
- Testing and release inclusions
- Support and asset ownership
What to do next
Write a one-page summary of your user groups, current workflow, necessary integrations and decisions still open. Evaluate trade-offs against those facts. For an Android-specific requirement, Archeet Infotech can discuss the implementation scope; work such as specialist SEO or hosting belongs with the relevant group concern.
These official resources explain relevant Android and platform practices. Project-specific decisions require verification at implementation time.