App / Mobile
You can reach the h885 lobby from the browser already on your phone, with no store trip and no file to sideload. Sign in with the email and password on your account and the same wallet, game list and help pages you use on desktop open in a layout sized for a handset.
Everything we run loads as a web page, so the route you take on a phone is the route you take anywhere. Tap the menu and the lobby categories, the signed-in account area, the wallet page and the help pages stack into one scrollable column. Game discovery uses the same rails as desktop: Cricket Stats Hub and Football Betmaster carry cricket and football, with live tables and slots beside them. If a native build is offered for your handset, the device check on this page says so; if not, the browser version carries the whole session.
A phone earns its place by how little it asks of you. The layout keeps the menu, the wallet link and the sign-in form inside thumb reach, and widens cleanly on a desktop screen. Four behaviours follow.
On a phone the lobby stacks into one scrolling column instead of the wide desktop grid. Category tiles, live tables, slots and the sportsbook sit in the order you reach for them, and the header stays put between the wallet and the games.
The email and password fields hold their position while you scroll, so a sign-in you begin in the lobby finishes without hunting for the form again. Autofill on your phone works normally here, which suits a session with one hand free.
The menu lists the lobby, the signed-in account area, the wallet page and the help pages inside a single drawer, so you are never more than two taps from what you came for. Wallet entries for Nagad, Upay and bank transfer sit on that page as configured.
Headings, buttons and the chip row on this page are tuned for a handset first, then widened for desktop. Tiles keep their labels readable on a small screen, so a slot room or the Cricket Stats Hub card is easy to pick out.
Getting in from a phone takes a few moves and none of them involve a store. Open this site in the browser you already use, then sign in with the email and password registered on your account; the form stays in reach on every page until you finish it. From there the lobby, the wallet page and the help routes are a tap away. If a native build is ever released, the device check on this page names the handsets it is offered for.
Type the h885 address into your phone browser, or open the bookmark saved on the handset. Check the domain in the address bar before you enter anything.
Hold the phone in portrait and give the column a moment. If the layout looks cramped, switch off desktop-site mode and reload once.
Enter the email registered on your account and your password, then let the confirmation finish before tapping through to the lobby.
Add this page to your home screen so the next visit is one tap, and sign out whenever the phone passes to someone else.
Before you blame the phone, work through the four checks below. They take in the browser, the screen, the account and the handsets a native build is currently offered for — the same ground the device check on this page walks you through.
Keep your phone browser updated through your handset settings. An older build can drop the layout rails and hide parts of the menu.
Portrait suits the lobby, the tiles and the sign-in form. If text spills past the screen edge after a reload, desktop-site mode is the setting to switch off.
Sign-in uses the email and password registered on your account, and the wallet page opens inside that session. If the confirmation stalls, use the published recovery path rather than opening a second account.
The device check on this page names the handsets a native build is currently offered for. Where a model is not listed, the browser version is the route to use.
When something goes wrong on a phone, the fix usually sits on the page in front of you. Our published help routes pick up sign-in trouble, wallet questions and device access, and you open them from the same menu you use for the lobby.
The help section sits inside the main menu, so you can open it without leaving the screen you are on. It takes in sign-in, the wallet page, device access and the account routes you need, written to be read while scrolling.
Our contact route is published on the help pages, along with what belongs in a message: the email registered on your account, the handset you are using and what the page did when it failed.
If the sign-in form will not accept your details on a handset, follow the recovery path linked from that form instead of registering again. Staying on one account keeps your wallet history and saved game list together.
Phones make it easy to tap the wrong thing, so the checks below earn their place. They run through the domain in your address bar, the device guidance we publish, the credentials you keep on the handset and the recovery route when something looks off.
The address we operate from is this domain, and it should be in the address bar before you type a password. If a link arrives by message and the spelling does not match, close it and open the site yourself.
We publish what the mobile layout needs and what the device check looks for. Reading it once saves you from chasing an app package that does not belong to us, and it tells you when a native build is offered for your handset.
Keep your password off shared handsets and stop the browser from saving it when the phone passes between people. Sign out at the end of a session, and change the password from the account page if you think it has travelled.
If a sign-in fails or the page behaves oddly, go to the published recovery path rather than replying to whoever contacted you. Queries about your wallet can wait until you have confirmed you are on our domain.
These are the ones we hear most from people signing in on a handset for the first time — native builds, browser behaviour, and what to do when a page will not load.
Access runs through your phone browser, and that version carries the full lobby, wallet page and account routes. If a native build is released for a handset, the device check on this page names the models it is offered for.
The same account, the same wallet and the same game list load either way; only the layout changes. On a handset the rails stack into one column and the menu holds your routes, while desktop spreads the categories across a wide grid.
The email and password on your account work on both. Sign in where you are and your wallet balance, saved games and account pages follow the account rather than the device. Sign out on a shared machine when you finish.
The layout is built for a handset first, so text sizes, buttons and the chip row are tuned for a narrow screen. If it looks cramped, your browser may be forcing desktop-site mode — switch that off and reload.
Refresh once, then check that your browser is up to date and desktop-site mode is off. If the form still does not appear, use the recovery path linked from the sign-in page and send our support route your registered email and handset.
Once you finish signing in, the session stays with your account until you sign out. You can close the tab, come back through the address or your home-screen shortcut, and the lobby recognises you on the next visit.