You're standing in a checkout line, your phone buzzes, and a position you opened three days ago just cleared its take-profit level. The first thing you do is pull up the dashboard, not search an app store for something to install. There's nothing to install from a store, because the thing you're looking at was never built to live in one.
That's the honest answer to "does this have a crypto trading bot mobile app": yes, but it's a Progressive Web App, not a download, and the distinction matters more than it sounds like it should. A full-time job that doesn't leave room to babysit charts all day is exactly why a phone view exists in the first place, and the version worth having is the one that shows you the real dashboard, not a stripped-down summary screen someone designed to fit a smaller box. There's a second reason it matters. You shouldn't have to hand trade permissions on a real crypto balance to a server you've never seen, just to get that phone view in the first place.
TradeArmor is where I put all of this to work: self-hosted, my keys never leave my hardware, three years of live BTC/USDC signal history behind it, 15 indicators running in real time, a plain-English AI strategy builder, and DCA, grid, futures, copy trading, backtesting, paper trading, and tax exports built into the same platform. See the full feature set before the rest of this post, which is about one narrow question: what happens when you take that platform out of the room where the machine lives and put it in your pocket.
What a Crypto Trading Bot Mobile App Actually Means
Type "crypto trading bot mobile app" into a search bar and most of what comes back assumes you mean a native download, an icon from the App Store or Google Play that talks to a company's server somewhere. That's not what TradeArmor ships, and it's not an oversight.
A Progressive Web App is a website that installs. Add it to your home screen and it opens full-screen, no browser chrome, no address bar, an icon that looks and behaves like any other app on your phone. Underneath, it's still your dashboard, still running on your machine, still reachable only through whatever access path you've set up for it. Nothing about the install process routes your data anywhere new. It's the same page, wearing a home-screen icon instead of a bookmark.
Installing It on iOS and Android
The process takes under a minute either way, and it's the same whether you're on your home Wi-Fi or reaching the dashboard through a Cloudflare Tunnel or VPN.
On iPhone: open the dashboard URL in Safari, tap the Share icon, then "Add to Home Screen." That's the entire install. iOS requires Safari specifically for this step; Chrome on iOS can't trigger the home-screen install because Apple routes all iOS browsers through the same underlying engine restrictions.
On Android: open the dashboard URL in Chrome, tap the menu, then "Install app" (some versions show "Add to Home Screen" instead, same result). Chrome may also prompt you automatically after a couple of visits.
Either way, you now have an icon. Tap it, and you're in the dashboard, full-screen, same real-time WebSocket feed as the desktop view. No separate login flow, no account to create in an app store, because there was never a separate app to register in the first place.
Push Notifications Work Differently on Each Platform
This is the part most guides skip, and it's the part that actually changes what you should expect.
iOS added web push for installed PWAs in iOS 16.4, announced by WebKit in early 2023, and it comes with one hard rule: the notification permission prompt only appears after the PWA has been added to the home screen. A Safari tab, no matter how long it's been open, will never ask you to allow notifications. Install first, then grant permission, in that order, or it doesn't work at all.
Android is looser. Chrome can request and deliver push notifications even from an open browser tab, not just an installed PWA, though Android's own battery management can quietly delay or drop notifications for anything you haven't opened in a while. The fix is the same either way: keep the PWA installed and open it occasionally, and the platform treats it like the app it's pretending to be.
Once notifications are granted on either platform, they behave like any other push alert: lock screen, notification center, the whole normal experience. The alerts guide covers which events actually trigger one, new positions, DCA buys, partial sells, stop-losses, daily summaries, so your phone doesn't turn into a slot machine going off every time an indicator so much as twitches.
The Custody Difference Nobody Puts in the App Store Listing
Here's the part worth sitting with. A native mobile app from a SaaS bot vendor is a thin client. It opens, it authenticates against the vendor's cloud backend, and every piece of data it shows you, your positions, your balance, your API key permissions, already lives on a server you don't control. The app icon just makes that arrangement look polished.
A native app is a browser wearing a blazer. The custody decision was made the day you pasted an API key into that vendor's web dashboard, months before you ever downloaded their app. The mobile app didn't create that trade-off. It just made it easier to check on from a train platform.
TradeArmor's PWA can't do that, structurally, because there's no TradeArmor cloud backend holding your keys to begin with. The dashboard you're looking at on your phone is a window into your own machine, the same one your desktop browser was already pointed at. The full self-hosted versus SaaS breakdown covers this trade-off beyond mobile specifically, and the API key security guide covers exactly which permissions your exchange key should carry regardless of what device you're checking it from.
Getting the URL to Install It Against
None of this works from outside your home network until the dashboard has a URL reachable from wherever you actually are. On the same Wi-Fi as the machine, the local address is enough and installing the PWA takes the two taps above. From anywhere else, you need one of the remote-access paths, a Cloudflare Tunnel with an identity check in front of it, or a home VPN, both covered start to finish in the remote access guide. Set that up once, then point the PWA install at whichever URL it hands you instead of the local one, and the phone icon works the same whether you're on the couch or three states away.
Somewhere, a SaaS bot's App Store listing is bragging about "bank-grade encryption" for an app whose entire security model is a password field and a support team's promise. TradeArmor skips the permissions-dialog theater, the app-store review cycle, and the update button, because the thing installed on your phone is a window, not a vault with someone else holding the key.
Pricing
The mobile PWA, remote access, and the real-time dashboard behind both of them ship on Starter at $19.99/mo, same as Pro at $49.99/mo and Enterprise at $89.99/mo. It isn't a feature that gets added at a higher tier. Every plan includes the 30-day money-back guarantee and free updates for the life of the subscription, so checking the bot from your phone costs nothing extra regardless of which tier you land on.
Underneath this feature sits the same engine that runs everything else, cava-signals, 15 real-time indicators, the AI strategy builder, DCA, grid, futures, copy trading, backtesting, paper trading, and tax exports, self-hosted on a machine that's yours. See how the mobile PWA fits into the rest of the platform, or compare the three tiers and add the one home-screen icon that doesn't cost you custody of your own keys.
Past performance is not indicative of future results. Signals are algorithmic outputs, not personalized investment advice.