What Actually Works on iOS — The Narrow Stack

Three architectures that ship. None of them are "a TestFlight app that plays poker for you." All of them are honest about where the smart part actually lives.

If you read the sandbox page, you know what's off the table. This page is the inverse — the things you can do on a stock iPhone, with the App Store working as designed, that materially help a poker player or operator. We'll go from least to most invasive.

Option 1 — Analytics-overlay companion app

This is the most common iOS-compatible architecture, and the most boring one. You install a normal, App-Store-legitimate app on your phone. It does not see, touch, or drive your poker app. It does, however, talk to a backend server that you also feed your hand histories or live hand events into — through whatever channel works (HUD desktop client, OCR'd screenshots emailed to a server, a stat-feed API from the room if one exists).

The phone shows you, in real time, what the backend computes: ranges, pot odds, opponent tendencies, ICM. You decide what to do, and you tap the poker app yourself. This is allowed because the iPhone app is talking only to its own server and rendering its own UI. It is not driving the poker client. Apple has no objection. You also get nothing automated — you are still the one playing.

Useful for: serious players who want a stat layer, study mode, post-hand analysis on the same screen they played on. Not useful for: anyone whose actual goal was "the bot plays while I sleep."

Option 2 — Web-app shell with the bot on a server

One step closer to the "bot" concept. The actual poker-playing logic — including the part that reads the table and decides what to do — lives on a server. That server may be running a desktop poker client of its own (a virtualized Windows box, headless), or it may be talking to a room that exposes an API, or it may be driving an Android phone over ADB in your closet. The iPhone is a dashboard for that server. You see what the bot is doing, you can pause it, you can re-tune ranges.

This is technically allowed by iOS — you are just running a custom client that talks to your server over HTTPS. App Store review still applies, though, and review will reject it if the marketing or behavior is gambling-related without the right entitlements. The common dodge is to ship the dashboard as a progressive web app on a Safari home-screen icon, skipping the App Store entirely. That works. It's also why nobody has a polished, App-Store-distributed app for this — the people building it route around the store on purpose.

If you see a slick "poker bot iOS app" with App Store screenshots and five-star reviews, it is almost always category 1 (analytics, no automation) being marketed dishonestly. Always read the small print before you pay anything.

Option 3 — Jailbreak and sideload

The third option is the one nobody wants to recommend and that we'll mention only for completeness. A jailbroken iPhone — and on modern iOS versions, that's a small and shrinking population — can install tweaks that hook into other apps' UI, including a poker client's. People have shipped these. They are unstable, they break with every iOS update, and they require you to keep a device on an old iOS version you don't update. They also have a long history of bundled malware, because the same person willing to sideload an unsigned tool is the person whose credentials become collateral when the bundle ships with a keylogger.

If your reason for searching "poker bot iOS" was that you have a specific jailbroken-era iPhone you want to dedicate to this, fine — talk to someone, scope what's possible. But this is not where new builds are happening, and it is not what we'd point a first-time customer at.

The honest assessment

Out of the three: analytics overlay is the only one where you get a clean App Store experience, and it's the one where the phone doesn't do any of the bot's work. Web-app shell is the one most real operations look like, and it routes around iOS rather than running on iOS. Jailbreak is technically "on iOS" but is not a category we'd build a new product in.

If any of those sound like the actual thing you wanted when you searched, ask for TestFlight access — it's the contact form, not a build, and we'll talk about which of these makes sense for your setup.