Podium Prophets
Back to Blog
GuidesApril 26, 2026·9 min read

Podium Prophets Goes Mobile — Q2 2026 Preview

Native F1 prediction app coming Q2 2026 to iOS and Android. Push notifications for deadlines, full feature parity with the web app, predict on the go.

It's Saturday. Qualifying starts in 90 minutes. You're in a pub, on a train, walking the dog, doing literally anything that isn't sitting at a laptop. You meant to lock in your predictions earlier in the week and didn't. Now you're staring at your phone trying to drag drivers around a tiny browser tab while the deadline ticks down.

I built Podium Prophets for friend groups exactly like this, and the web app is genuinely good on a phone. But "genuinely good in a mobile browser" still loses to "native app I tap from the home screen." So I'm building the mobile version. iOS and Android, native, shipping Q2 2026.

This post is the honest preview of what's coming, what isn't in v1, and why I'm doing it native instead of just slapping a PWA wrapper on the existing site.

If you're brand new here, the F1 Predictions for Beginners guide is the place to start. If you're trying to pick between prediction apps, the 2026 prediction games comparison covers the full field including which ones already have mobile apps.


What's coming Q2 2026

Native apps for both iOS and Android. Same codebase under the hood, same Postgres backend, same scoring engine, same Google sign-in. You install the app, log in once with the account you already use on the web, and everything is there. Predictions, leagues, championship picks, your garage, your league standings, your Chaos Mode toggle, all of it.

The point of the rebuild isn't a redesigned product. It's the same product, finally on the platform where most of you actually use it. GSC tells me mobile already drives more clicks than desktop on the web app, and mobile CTR is six times higher than desktop. People want this on a phone. I'm just making the phone version stop being a fallback.

A few things that are shipping at launch:

  • Full predict flow with drag-and-drop P1 to P10 cards. The drag interaction is rebuilt for thumbs from the ground up, not just the web version with bigger touch targets.
  • Championship picks for driver and constructor, separate tab, same logic as web.
  • Private leagues: create, join, invite, manage. Bulk invites work on mobile.
  • Garage and prophet profile: badge collections, equipped helmet, titles.
  • Chaos Mode: full toggle, magenta theme included. The meme championship comes to mobile too.
  • Results dashboard: weekend-by-weekend scoring breakdowns and league grids.

If you can do it on the web app today, you can do it on the mobile app at launch. That's the bar.


Push notifications: the actual reason this exists

Every other piece of the mobile app is "nice to have." Push notifications are the part that fixes a real problem.

Right now, the web app sends opt-in email reminders for missing predictions and scored sessions. Email works, but email is the slowest part of the internet. Nobody opens email between sessions. The reminder lands at the wrong time, gets buried, and you miss the deadline anyway.

Push notifications fix this. Three triggers that matter:

  1. Predictions open for the next qualifying or race session. One ping, you tap, you submit, it takes 90 seconds.
  2. Deadline approaching for any session you haven't predicted yet. Configurable lead time. The default will be one hour before lights out, which lines up with how the web app's missing-prediction emails already work.
  3. Scored when results come in. Tap the notification, see your score, and check whether you beat your friend.

There's a fourth one for league invites, and a fifth for Chaos voting if you're toggled in. Each notification type is individually toggleable, because some people want every ping and some want only deadlines and absolutely nothing else.

Most F1 prediction apps don't lean on push at all. The official F1 Calendar app uses push for race-day reminders and people seem to like it for that. None of the prediction apps I've poked at make push the centrepiece. That's the gap I'm filling.


What "feature parity" means (and where it bends)

Feature parity at launch means: anything you can do on the web app, you can do on the native app. With one honest caveat about the heavier analysis tools.

The full session analysis suite (race pace scatter, long-run strip plots, team pace hierarchy, qualifying breakdowns, telemetry lap comparison, the circuit intelligence panel) is built around large interactive Recharts visualisations. Some of those work great on a phone. Others were built for laptops and would either need a different visual treatment on mobile or a redesign that respects thumb targets and screen real estate.

Honest call: the predict flow, leagues, results, garage, and Chaos Mode all ship at launch. Some of the heaviest analysis modules might stay web-first for a few weeks while I rebuild the mobile-native version. You'll be able to tap into them from the app, but for the deepest telemetry views you may bounce out to the web for the first weeks. I'd rather be honest about that than pretend the launch covers 100% when 95% is the truth.

Everything else, the prediction game itself, is fully native at v1.


Why native instead of a PWA

Reasonable question. The web app is already responsive, fast, and installable as a PWA on iOS and Android. Why bother with a native build at all?

Three reasons, in order of how much they actually matter:

Push notifications. PWAs have push on Android and (technically) on iOS now, but the iOS implementation is fragile, requires the user to "Add to Home Screen" first, and frequently breaks on iOS updates. For a prediction app where the entire value of notifications is "they reliably show up before a deadline," fragile isn't acceptable. Native push is rock solid.

Deep links. "Tap an invite link, open the app on the right league screen" is a much cleaner experience as a native universal link than as a web fallback. Friend-group invites are how this app grows. Friction in the invite flow kills growth, and native deep linking removes that friction entirely.

App store presence. "Predict F1" and "F1 prediction game" are real searches in both App Store and Play Store. Some of the apps I'm competing with already rank for those queries. I want to rank too, and you can't rank in stores you aren't in.

I considered Capacitor, Expo, React Native, and a few other paths. The mobile app is its own focused codebase, sharing types and API contracts with the web app but with a UI built for the platform.


What is NOT in v1

Honest list, because nothing kills trust faster than launching with surprises hidden in the patch notes.

  • Some collectibles features. A bigger collectibles system is in flight on a parallel branch (cards, sets, completion bonuses, trade flow). The mobile app at launch shows your existing badges, helmet, and titles. The full new collectibles surface lands in a follow-up update once the parallel work merges.
  • Chaos meme image upload. The flow that lets users upload meme images for community voting is also on a separate branch. Community-voted text questions are in v1. Image-upload memes follow shortly after.
  • Heavy analysis modules. As above. Predict-flow analysis (quick-fill from FP3 results, weekend data drawer) is in. The deepest telemetry overlays are web-first for the first few weeks.
  • Public discovery features. Public-league discovery and the global leaderboard ship eventually. Private leagues for friend groups are the v1 priority.

Nothing on this list is "we'll see." All of it is on the roadmap. None of it is in v1.


Beta and launch updates

There isn't a public TestFlight signup yet. If that changes I'll post it on the homepage and on @podiumprophets on X. The plan right now is a quiet TestFlight round with friends and existing users in late Q2, then a soft launch on both stores, then a broader push when the App Store metadata is dialled in and the first reviews are positive.

If you want to be in the test cohort, follow on X and reply to the launch tease post when it goes up. I'll add interested folks manually, because the only thing worse than no testers is too many testers all reporting the same bug.


A small note on timelines

I said Q2 2026. I mean Q2 2026. I'm not committing to a specific date because mobile shipping is its own chaos: App Store review delays, last-minute push provisioning weirdness, the bug that only happens on Pixel 6a in Hungarian locale, all of it. If it slips a few weeks, I'd rather take the time and ship a version I'm proud of than rush a buggy launch to hit a date I made up on a blog post.

The web app keeps shipping in the meantime. Nothing about the mobile build slows the existing roadmap. Predictions, scoring, leagues, Chaos, and the analysis tools all keep getting better in parallel.


TL;DR

iOS and Android apps. Q2 2026. Free. Same account, same data, same leagues. Native push notifications for prediction deadlines and scored sessions. Full feature parity for the prediction game itself, with a couple of heavier analysis modules and the new collectibles surface following shortly after launch.

If you're already on Podium Prophets, you don't need to do anything. Your account will work on mobile the day the app drops.

If you're not yet, start at the homepage and run a season on the web. By the time the mobile app lands, you'll already have the muscle memory.

See you on the App Store.

T

Tebe

Solo developer and F1 fan behind Podium Prophets. Built this to replace our group's prediction spreadsheet — now it's open to everyone.

Ready to Predict?

Put your F1 knowledge to the test. Automatic scoring, private leagues, and built-in session analysis.

Start Predicting