Expensify (New Expensify) is a chat-centered financial collaboration application built in TypeScript and published under the MIT license, aimed at developers and contributors who build and extend expense management workflows across web, iOS, and Android.

What it is

New Expensify is described by its maintainers as a complete re-imagination of financial collaboration, centered around chat. The repository holds a single TypeScript codebase that targets three platforms — web, iOS, and Android — and it lives in the React Native and JavaScript ecosystem, with React Strict Mode guidance and a Left Hand Navigation (LHN) design document included in its contributor guides. The project carries 5,023 stars, 4,011 forks, and 2,252 open issues, with the most recent push recorded on 2026-09-16. It is released under the MIT license, and the hosted application is available at https://new.expensify.com.

The concrete problem it addresses is the older, form-and-spreadsheet model of expense reporting. New Expensify moves that work into a conversational surface, so that financial collaboration happens inside chat rather than through detached submission forms and email threads. In place of the previous generation of the Expensify client, this repository is the rebuilt application itself, and the README frames the work as the next generation of Expensify, inviting feedback and code contributions against the new client.

Key capabilities

• One TypeScript codebase serving web, iOS, and Android, where each platform is started through npm run , for example npm run web, with per-platform guides in contributingGuides/SETUP_WEB.md, contributingGuides/SETUP_IOS.md, and contributingGuides/SETUP_ANDROID.md.
• Chat-centered financial collaboration as the core product model of New Expensify, rather than a peripheral messaging add-on.
• Onyx state management, with debugging enabled through the USE_REDUX_DEVTOOLS environment flag and render tracking through USE_WDYR.
• API integration against separate endpoints, where EXPENSIFY_URL and SECURE_EXPENSIFY_URL are distinguished, and sign-in is handled at https://www.expensify.com/api/BeginSignIn.
• Partner authentication constants, EXPENSIFY_PARTNER_NAME and EXPENSIFY_PARTNER_PASSWORD, used by the app when authenticating.
• Realtime transport through Pusher, configured with PUSHER_APP_KEY.
• Local tunneling for web testing through ngrok, controlled by NGROK_URL, SECURE_NGROK_URL, and the USE_NGROK flag.
• AI-assisted device testing through the .claude/skills/agent-device/SKILL.md /agent-device skill for Claude Code, which drives iOS and Android simulators or devices and requires npm install -g agent-device.

Who uses it and how

• Open-source contributors working from the repository's contribution guides, code of conduct, and contributor license agreement, which govern how changes are accepted.
• Mobile engineers testing on iOS and Android simulators and emulators, including browser testing inside those simulators.
• Expensify engineers testing against the API in a local development environment, who the README directs to separate internal instructions.
• React Native developers who need to reason about strict-mode rendering behavior and left-hand navigation structure, both documented in the contributing guides.
• Teams that want chat-based expense workflows without running anything themselves, since the hosted application is published at the project homepage.

Getting started

Local development starts with brew install nvm && nvm install, then brew install watchman, then npm install, then a platform command such as npm run web. The node and npm versions are pinned strictly by the engines field in package.json and the .nvmrc file, so npm install fails if the wrong version is used.

How it compares

The facts provided name no comparable tools and no list of paid products that this project replaces, so no direct contrast on licence, hosting, data ownership, or cost can be drawn. On the supplied evidence, New Expensify stands alone in this registry.

When to use it — and when not to

Anyone self-hosting must expect to manage a pinned Node toolchain, Watchman, and the individual web, iOS, and Android build setups, plus credentials for the Expensify API and Pusher, since the README warns external contributors against creating a .env file at all. It is not a fit for teams looking to operate their own expense backend, because the documentation covers local development only and describes no database, storage, SMTP, or production deployment path. The repository is also carrying 2,252 open issues and lists no topics, which signals a large, active, and correspondingly noisy project rather than a small, settled one.