The problem
Frappe Desk is a powerful interface, and it is built for everyone: developers, administrators and the clerk who enters invoices. End users often need a smaller, faster surface. They want the screens for their own work, in their own language, and a client that feels fast on a slow connection.
In Algeria and other French-speaking markets, the default language matters too. A team that works in French all day should not have to switch.
What we built
Foxmayn One is a front end for Frappe and ERPNext sites. It re-implements the parts of Frappe Desk that end users touch. It runs as a desktop app and as a web app, from one code base.
- Sixteen ERPNext areas with their own screens: accounting, assets, buying, CRM, customization, manufacturing, projects, quality, selling, stock, support, website, users, integrations, tools and settings.
- Generic list and form views that work for any DocType, so a custom DocType gets a usable screen without extra work.
- French first. The default language is French.
- Sign-in with email and password, or with an API key.
How it works
Foxmayn One talks to your Frappe site over its REST API, through frappe-react-sdk. Data is cached with SWR and kept in IndexedDB, so a reload shows the last known data at once and then refreshes it. That gives the app a fast start and some tolerance for a weak connection.
The interface is React 19 with Vite, TypeScript, TanStack Router and Jotai for state. Styling uses Tailwind 4 and shadcn/ui components. The desktop build wraps the same web code in Tauri 2, which uses Rust for the native shell.
Because the app uses the standard REST API, it works with each user's own Frappe permissions. It does not need a custom app installed on the site.
Where it stands
Foxmayn One is early and in development. The repository is private. It has five commits, from 15 June to 3 July 2026. There is no released desktop build and there are no customers.
Be clear about what that means:
- It does not match Frappe Desk feature for feature. It covers the common screens of the areas above, plus the generic views.
- It has no automated tests and no CI yet.
What it shows about our work
We know Frappe from both sides. We write custom apps on the server, and we have built a client that reads the same data. That helps when we design custom Frappe apps: we think about the screen the user will see, not only the DocType behind it.
Next
Tests come first, then a measured comparison with Frappe Desk on real sites. A signed desktop build will follow. If your team needs a lighter client for ERPNext, talk to us. Our open-source tools for Frappe are public today.