#028Tutorial4 min
Use Hackaiz from a phone
Navigate the web workspace, locate a project and review a report on a smaller screen.
Hackaiz team · updated 21/11/2026

01Use the web workspace on your phone
The signed-in Hackaiz workspace includes a layout for small screens. Open the website in your phone’s browser and sign in through the authentication page. The instructions here describe the web interface; they do not require installing an application from a mobile store or granting access to the contents of your phone.
The main difference is navigation. The wide sidebar used on a large display gives way to a bottom bar and a menu drawer. This makes the existing workspace reachable in a narrower view, but it does not change the meaning of analysis results or the authorization needed for the targets you assess.
03Find the right project without a desktop sidebar
On Monitored projects, use Search platforms to enter part of the project name, repository or address. Check the identifying text before opening a card: long names can be shortened visually on a small display. The card opens an available report when one exists, or takes a project without a report toward analysis.
For a project’s older runs, tap the header magnifying glass and select the project in the Projects group. This opens the project detail, which contains Scan history. The quick search offers a limited project selection rather than an unlimited inventory. Use a saved project-detail address when the item you need is not offered there.
When reading an individual analysis, inspect its completion state and coverage before acting on the finding count. Danger, To fix and To watch carry the same meaning on your phone as on a computer. A narrow view does not make a stopped run a successful one or extend the set of checks that ran.
04Keep sensitive actions deliberate on a small screen
You can reach Analyze from the workspace header, but take time to confirm the target and selected checks before starting work. Analysis actions use credits. Unticked checks are not run or billed. For websites and APIs, proof of domain control is still mandatory: use the _hackaiz DNS TXT record, the HTTPS verification file or the project AI file-creation instruction.
If you want a PDF, the analysis page’s Shareable report section uses the browser’s print workflow. Choose a recipient profile and PDF, then follow the print or save options your device provides. A blocked print window requires allowing that window; it is not evidence that the report vanished. Text file is another available output if printing is impractical.
For code changes, do not rush a review because the screen is small. Fix proposals are draft GitHub pull requests, meaning proposed changes for a human to inspect and approve; they are never merged automatically. Move a detailed comparison to a larger screen when needed, rather than treating a brief report summary as sufficient approval.
On a shared phone, use Sign out in the menu when finished and avoid leaving saved reports in a place another user can browse. A report may contain sensitive technical evidence. The language and theme controls are also available in the drawer, so you can adjust readability without changing the target or launching an analysis.
Frequently asked questions
Take the next step
Was this article helpful?