Web and mobile application development

Start with users and goals

Identify users, their tasks and successful outcomes before designing screens. Consider devices and critical journeys to choose the appropriate web or mobile approach.

Project components

• Information architecture, screen design and reviewable prototypes
• Frontend, backend and APIs within the agreed scope
• Testing, environment configuration and handover planning

Plan for release

Review authentication, permissions, notifications, connectivity and external integrations. Prepare organization-owned service accounts and agree on post-release maintenance.

Choosing web or mobile apps around the user journey

Start with primary users, their repeated tasks and the environments in which they work. A procurement back office may need a desktop-friendly web application with rich tables and filters, while warehouse operators need a compact barcode-scanning interface. Responsive web or PWA may be a better first release than two separate native applications.

Separate the interface from business APIs so validation and authorisation remain server-side. Design identity, tenant boundaries, document-level permissions and audit logs early. For ERPNext integrations, use validated business endpoints with idempotency for requests that may be retried.

Good interfaces minimise steps for common work, make states and warnings understandable and avoid unnecessary buttons. Test on actual touch devices and with keyboards, slow connections, multiple tabs and accidental duplicate submissions.

Plan separate development, staging and production environments, role-based UAT, backups and error monitoring. Offline support requires explicit rules for local data, editing permissions and conflict resolution after reconnection.

Frequently asked questions

Explore related topics