If you're reading this on a phone: good. That's kind of the point.
BudgetPilot is now on Google Play. Same account you use on the web. Same workspaces, budgets, transactions, recurring payments. We didn't build a "lite" version that only shows charts and then tells you to open a laptop.
iOS is coming soon. Not "someday." Soon. We're not going to pretend it's already out when it isn't.
Why we bothered with mobile at all
Most of our early users lived in the browser. That was fine for evening catch-up sessions. It was terrible for the moment you're at the supermarket wondering whether this week's groceries are already over the line.
We kept hearing the same thing in different words: "I only open BudgetPilot when I'm at my desk." Which sounds harmless until you realize that desk time is exactly when people are least likely to change a spending decision. The useful moment is earlier — in the aisle, in the rideshare, after the coffee order you didn't plan.
So we shipped Android first. Not because we love Google more than Apple. Because a big chunk of our early users were already on Android, and getting something into their pocket mattered more than waiting for a perfect dual-platform launch that would have slipped another quarter.
What shipping actually looked like (the unglamorous bits)
I'm not going to write the LinkedIn version of this.
We spent weeks arguing about connection pools and environment variables. We had a build that kept pulling the wrong Node version and installing the wrong Expo SDK because someone ran the command from the wrong folder. We had a Sentry upload step fail the entire Android release because an org slug wasn't set. None of that belongs on a marketing page. It belongs here, briefly, so you know this wasn't magic — it was a lot of small, annoying, necessary work.
The product side was clearer. We already had the web app doing the heavy lifting: workspaces, imports, budgets, insights. Mobile had to feel like the same system, not a second product with different rules. That constraint saved us. We weren't inventing a new finance philosophy for phones. We were making the existing one reachable when you're not at a desk.
What we hope this does for you
Here's the honest goal, without the slogan font:
We want BudgetPilot to be the place you check when money feels fuzzy — and for that check to take under a minute. Not a second job. Not a guilt machine. Just: what's left in this category, what's renewing soon, did that import land correctly.
If you share finances with someone, we want the shared workspace to be the thing you both trust, so you're not trading screenshots of bank apps. If you run a side hustle next to a salary, we want those contexts to stay separate so one number doesn't lie about the other.
We're not trying to replace your judgment. We're trying to reduce the amount of administrative sludge between you and a decision you already know you should make.
Android now. iOS next. Web stays.
Android — live on Google Play (search BudgetPilot, or use the link at the bottom of this post).
Web — still the fullest experience, still where a lot of setup and imports will feel easiest.
iOS — coming soon. If you're on iPhone, please don't read "coming soon" as a polite never. We're actively working toward it. We'll say when it's actually available, not before.
Until then, the web app works on mobile Safari. It's not as nice as a native app. We know.
If you try it this week
Install it. Sign in with the same account. Open your personal workspace first — don't try to configure five side projects on day one. Look at this month's spend, check one recurring payment you keep forgetting about, and see whether the phone version makes that check feel natural.
If something feels off, tell us. Support is support@budgetpilot.ai. We read it. Especially now.
Thanks for sticking with us through the web-only stretch. Having the app on a real store listing is a small line on a changelog and a much bigger line for us.