Native Android in Kotlin and Java, cross-platform where that's the right call, always talking to a backend built and maintained by the same engineers, not handed off to a separate mobile shop that has to reverse-engineer the API.
Kotlin and Java, for when performance and platform integration matter more than shipping to iOS and Android from one codebase.
One codebase to both major platforms, the right call for most business applications where native-only APIs aren't the point.
For ERPNext implementations specifically, mobile access to HR, inventory, and approvals workflows without a separate app to maintain.
These two screens are the official Frappe Mobile app, not a bespoke build, connected to an ERPNext instance we implemented. It's what "mobile access to your ERP" actually looks like without a separate app to maintain.
Custom native and cross-platform app screenshots are on the way. This page describes what we actually build, not a stock photo of someone holding a generic phone mockup.
