Mobile / App
go60 opens in the browser you already have on your phone, with no separate build promised and nothing sitting in your storage. Everything we publish about handset access lives on this page: the screens we render, how sign-in works from a phone, and where to confirm whether anything has changed for your device.
Phone access on go60 is a browser session, so you get the same lobby rearranged for a handset rather than a second piece of software. The menu folds into one button, tiles for Cricket Scorer and the rest of the catalogue sit in a rail you flick sideways, and the account menu keeps your wallet and transaction history one tap away. We keep the help pages readable at phone width too, since that is where you go when a button does not respond or a screen looks unfamiliar.
Everything below is behaviour you can check on your own handset in a minute, with no extra software in the way. We describe the page as it renders, not as we would like it to render.
The main menu folds into one button in the corner. Tap it and the lobby sections, your account route and the help pages appear as a short scrollable list, which keeps a handset screen from filling with links.
Catalogue tiles sit in a horizontal rail you scroll with a thumb. Cricket Scorer, the football markets and the crash titles are grouped rather than stacked, so you reach a section without typing. The same tiles render at every width.
Your wallet, sign-in and sign-out sit behind the account button, and each one loads as its own page instead of a panel that traps you. If a form looks cut off, turn the phone sideways before you submit.
Help and support pages use the same type size as the lobby, with links that stay tappable. When something will not open, check whether the page finished loading first, because a half-loaded page leaves buttons unresponsive on a weak connection.
Three things decide whether phone access works well: the address you open, the browser you open it in, and whether you sign in only after the page has finished loading. Start at the site address you know instead of a forwarded link, confirm your browser carries its current update, then sign in with the email and password tied to your account. If a step stalls, reload once before retyping anything. Keep the tab open until the lobby tiles or the account area draw, since closing a load halfway is the usual reason a sign-in looks like it failed.
Type the address you know into your browser, or use the bookmark you saved. Skip shortened links from messages, because a forwarded address can point away from our site.
Let the tiles and the account button draw fully before you tap. If text overlaps or a menu refuses to open, refresh once, then try another browser on the same phone.
Use the email and password you set when the account was opened, on the sign-in route in the menu. Read the fields and limits shown there before you confirm anything inside the wallet.
A short check before you sign in saves a second attempt later. None of these points needs an installed file, since they are all things you can see in the browser you already use.
Open the site in the browser that came with your phone or one you update yourself. If a page loads but buttons ignore taps, a stale browser version is the first thing to rule out before you try again.
Text, tiles and the menu button should sit inside the screen without sideways dragging, because we size type for phone reading. Turn the handset to landscape when a table or form looks cramped, and pinch only where the page allows zoom.
Access to the wallet and lobby needs a signed-in account opened through the account page, with the details you entered there. Anything the pages ask you to confirm is shown inside your own account area, not in a message.
We do not publish a device list with model numbers. Read the notice on this page and the help pages linked from it before you change settings, and treat any outside claim about supported handsets as unconfirmed until you see it here.
The routes below are the ones we publish on the site, and they work the same on a phone as on a wider screen. Nothing needs a separate phone build to reach them.
The help pages cover signing in, wallet routes and what each screen expects from you. Open them from the menu before you retype a password, because most stuck screens clear once a page finishes loading properly. They read the same at phone width.
Details about your own account sit behind the account button, where sign-in history and wallet routes are listed. Check there first when a page tells you something is missing.
Refresh once, then switch browser. If the problem survives both, note the exact screen you were on and the wording of any message before you contact our support page, so the reply does not start from zero.
Four habits keep phone access clean, and none of them takes long. Run them in order the next time you open the site from a new handset. Each one is something you can verify yourself.
Check the domain in the address bar matches go60 before you sign in. A page that looks familiar but sits on another domain is the single thing worth catching early, and the bar shows it every time.
Our help pages set out what each screen asks for, including the sign-in fields and the wallet routes. Skim them before you change phone settings, so a slow screen does not send you into menus you did not need to touch.
Do not save your password in a shared handset's browser, and sign out when you finish. If you lend the phone to someone, sign out yourself rather than counting on a closed tab to end the session.
If you cannot get back into the account, follow the recovery route shown on the sign-in screen instead of opening a second account. A duplicate account splits your wallet and history, which is harder to sort out later.
You ask about handset access more than anything else on this page, so the six answers below stay short and stay on the same point. Read the one that matches your screen before you change a setting.
No separate build is listed for download on this page. You open the site in your phone browser, sign in through the account route in the menu, and the lobby renders at phone width. If that changes, the notice appears on this page.
Use a browser you keep updated, whether that is the one that shipped with the phone or one you installed yourself. If a menu will not open or buttons ignore taps, updating or switching browser fixes it more often than changing any other setting.
The layout rearranges rather than shrinks. The menu collapses into one button, catalogue tiles move into a rail you flick sideways, and tables scroll inside their own frame. Games and account routes stay the same; only the arrangement changes with width.
Yes, through the same email and password you set on the account page. The wallet and transaction routes load as their own pages on a phone, and any fields or limits you need to confirm are displayed there, so read them before you submit.
Refresh once, then try a different browser on the same handset. If it still fails, note which screen you were on and what the message said, then open our support page. That detail saves a round of questions before anyone can help.
This page carries the current position, and the help pages linked from the menu repeat it. Check here before you act on a link or file someone sends you, because a claim about a phone build that is not on this page is not something we have published.