Max Igoshev.
Email

Roblox game UI for mobile and PC

HUD, onboarding and menus for Roblox games, built and wired up in Roblox Studio. One interface that adapts to touch screens and keyboards, so mobile players are not an afterthought.

  • Roblox HUD demo after the quest: level 6, quest done, Moon Howl skill unlocked

HUD and skill bars

Health, mana, quest tracker and skill buttons that stay readable over bright scenes, with cooldowns, locked states and unlock moments.

Mobile and PC from one layout

A thumb arc of big buttons on touch screens, key labels on PC, switched automatically by input type and scaled to the screen.

Onboarding that teaches by doing

A first-run tip shows one action at the moment it matters, then a short quest and a reward lead the player to the next mechanic.

Built and tested in Studio

Luau scripts with server-side rules, checked in play mode, not a picture of a screen.

Case: playable HUD demo

The screenshot above is the demo running in Roblox Studio after the quest: level 6, quest done, the new skill unlocked. Everything you see is built in code, with no third-party assets.

The flow it shows

  1. A first-run tip dims the screen around the first skill, with a pulsing ring and the right hint for the device: “Press E” on PC, “Tap 🔥” on a phone.
  2. A quest asks for five hits on a training dummy. Each hit shows a floating damage number, a flash on the dummy and a progress bar update.
  3. Completing the quest drops a “Quest complete” banner and levels the player up.
  4. The level-up unlocks a locked skill with an animation and a short message, so the player knows exactly what changed.

What makes it work on every device

  • One layout for two inputs: a bottom row with key labels on PC, a thumb arc of large buttons on touch, switched by the last input the player used.
  • The whole HUD scales to the screen, so small phones keep the same proportions instead of overlapping panels.
  • Panels sit on soft dark backgrounds and never cover Roblox’s own top bar or player list.
  • Settings for mouse and trackpad camera speed and for touch button size.

How it is built

  • One shared config module holds every skill’s cost, cooldown, damage and unlock level, used by both server and HUD.
  • The server checks every rule (unlock, mana, cooldown, range, damage); the HUD only shows state and asks to cast.
  • Three scripts in total: a shared config, a server script and the HUD.

How we start

You tell me which screens matter most. I build a small working piece first in a separate place, so you can play it and judge it before giving any access to your game. Communication is in writing, in your time zone.