Lotto Wizard Mobile

Mobile App Path

Lotto Wizard now runs as one shared mobile experience across iPhone, Android, and the web.

This mobile experience is not a disconnected mockup. It calls the same Lotto Wizard generation, scoring, Draw DNA, and number-checking logic through the shared service layer so mobile stays aligned with the desktop product.

Same scoring model Same supported draw types Same Draw DNA output Responsive mobile-style flow

Open Mobile Experience Review Portal

1 Shared engine across desktop and web path

5 Supported Australian game types exposed

2026.04.14.14 Current bridge-aligned release

Live Mobile Experience

The phone-style experience already runs against the same Lotto Wizard service layer.

Start the service, load the supported games, then generate picks or check a line. This gives you a real mobile-ready surface without rewriting the lotto engine twice.

How To Use It

Three quick steps

Run py -3 -m backend.server from the project root.
Open this page and click Load Games.
Generate a run or check a saved line through the service.

Why This Matters

One engine, more surfaces

The desktop UI no longer owns the prediction logic.
The same API can sit behind a responsive portal, then native apps later.
You can evolve the mobile UX without changing the scoring rules underneath.

Bridge offline Connecting to Lotto Wizard services.

Connection

API base URL

Use localhost while testing, or switch this to your hosted API base for the live mobile experience.

Generate Picks

Game Load games to begin. Prediction lines System size System games

Official play style details will appear here for the selected game.

Systems only mode Include Draw DNA Merge official snapshot

Generate a run to see live cards and Draw DNA here.

Prediction cards, system lines, official draw info, and Draw DNA will appear here.

Check My Numbers

Check a line to see its score, hit summary, and latest draw comparison.

Your checked line summary will appear here after the first lookup.

Service Guide

The mobile app already runs on the same product stack as desktop.

What matters is the architecture: one reusable lotto engine, one API contract, then as many front ends as you want on top of it.

Discovery

`GET /api/games`

Returns the supported game list, number rules, market labels, and score-guide thresholds so the app can configure itself automatically.

Generation

`POST /api/generate`

Returns predictions, system games, official snapshot data, optimization details, analytics context, and Draw DNA cards in one response.

Checking

`POST /api/check-numbers`

Scores a user-entered line against the same rules as the desktop app and returns a readable summary for the mobile surface.

Keep desktop and mobile aligned

The desktop app remains the stable commercial release while the mobile surface stays on the same scoring and data model.

Use the same shared mobile experience everywhere

The same mobile surface can sit behind customer sign-in and account-linked access without changing the front-end model.

Ship native store builds when the backend is settled

Once the service layer is stable, native iPhone and Android builds can stay thin and reuse the same endpoints without duplicating logic.