Schedule a consultation

Mobile development

Mobile application development

Applications for the people who are not sitting at a desk — customers, field staff and approvers on the move.

A mobile application is worth building when the work genuinely happens away from a desk: a technician recording a job on site, a salesperson capturing an order, a director approving a payment between meetings, a customer checking a statement.

The hard parts are rarely the screens. They are offline behaviour when the network drops, syncing without creating duplicates, permissions, device fragmentation and the app store release process. We raise those in the requirements stage, because they shape the estimate.

We will also tell you when a mobile-friendly web application would serve you better than a native app — it usually costs less and is faster to change.

What you receive

  • Requirements covering offline, sync and permissions
  • Screen designs and interaction flows for review
  • Builds for testing on your own devices
  • Store submission support where applicable
  • Documentation, training and a maintenance plan

Scope of work

What this engagement covers

Android applications

  • Native Android builds for target device ranges
  • Offline capture with background sync
  • Camera, location and document capture where needed
  • Push notifications and reminders
  • Play Store release and update process
  • Device and OS version compatibility testing

iOS applications

  • Native iOS builds for supported device ranges
  • Interface conventions consistent with the platform
  • Secure local storage and authentication
  • Push notification handling
  • App Store submission and review support
  • Version and compatibility testing

Cross-platform applications

  • A single codebase across Android and iOS where suitable
  • Shared business logic with platform-specific behaviour
  • Faster iteration for internal tools
  • Consistent design across platforms
  • Trade-offs explained before the approach is chosen
  • Migration path if native becomes necessary

Internal & workforce apps

  • Field data capture and job completion
  • Attendance, expense and reimbursement capture
  • Approval workflows for managers on the move
  • Inventory and delivery confirmation
  • Integration with your back-office systems
  • Role-based access and remote deactivation

How we work

Working with us on this

How an engagement runs at Vanesh Nadar & Co. Four stages: review of the current position, a written scope and fee, execution to an agreed calendar, then review to stop problems recurring. STEP 1 Review We look at your records, filings, registrations and any open notices, and tell you plainly where things stand. STEP 2 Scope & fees A written scope: deliverables, timelines, what we need from you and the fee — agreed before any work starts. STEP 3 Execute Work carried out to an agreed calendar, with a named point of contact and documented handovers. STEP 4 Review & improve Recurring issues are traced back to the process that caused them, so the same problem does not return next quarter.
  1. ReviewWe look at your records, filings, registrations and any open notices, and tell you plainly where things stand.
  2. Scope & feesA written scope: deliverables, timelines, what we need from you and the fee — agreed before any work starts.
  3. ExecuteWork carried out to an agreed calendar, with a named point of contact and documented handovers.
  4. Review & improveRecurring issues are traced back to the process that caused them, so the same problem does not return next quarter.
Every engagement runs through the same four stages. Nothing begins until the scope and the fee are agreed in writing, and the fourth stage exists so that a problem found this quarter does not simply reappear in the next one.

General information only. The content on this page is general in nature and is not professional advice. Statutory applicability, thresholds and due dates depend on your specific facts and on the law in force at the time. Please speak to us before acting on anything you read here.

Questions

Frequently asked questions

Native or cross-platform?

Cross-platform is often the better economics for internal applications and straightforward customer apps. Native tends to win where you depend heavily on device capability or need the highest level of polish. We will recommend one and explain the trade-off rather than defaulting.

Will the app work without internet?

It can, if that is specified upfront. Offline capture with later synchronisation is a design decision that affects the data model and the estimate, so we settle it during requirements rather than adding it afterwards.

Do you handle app store publishing?

We prepare builds and support submission to the Play Store and App Store, including the assets and declarations required. The developer accounts are normally registered in your business name so you retain control.

Can it connect to our existing systems?

Yes, where those systems expose an interface. If they do not, we may build a small service layer in between. That is scoped as part of the project.

Speak to a Chartered Accountant

Tell us what you need — accounting, tax, GST, audit, advisory, Zoho Books or a software build. We will come back to you with a clear scope and the next step.

WhatsApp us