Samuel's Development

Appearance

Phone v0.1.0 ​

sd-phone is an iOS-themed in-game smartphone: lockscreen with Face Unlock and passcode, customizable homescreen, notification banners with persistent unread badges, an app switcher, and 45+ apps backed by real server modules.

Highlights ​

  • Communication: Messages (SMS, group threads, GIFs, money and location cards), Mail with global multi-account inboxes, Calls over pma-voice (1:1, group and company rings), Contacts with AirShare, Dark Chat, and a Radio app.
  • Social with real accounts: Photogram (posts, stories, DMs, live video streaming), Birdy, Cherry, Vibez, and Streaks all run on a shared accounts engine with registration, sign-in, and password resets delivered by in-game mail or SMS.
  • Camera and media: the Camera app renders the live game view into the phone (photo, video with voice capture, selfie mode), a Photos gallery with editing, Music with AirShare library sharing, Voice Memos, and video-capable Photogram feeds.
  • World integration: Services (company directory, dispatch-style messaging, phone multijob), Garages and Homes bridged across ten-plus garage and housing systems, Wallet over the framework's bank, Maps with CDN-streamed tiles, Weather synced to the in-game sky, Ryde ride-hailing between real players, and a boss-gated Weazel News newsroom.
  • Games: online multiplayer Chess, Connect Four, Battleship, and Wordle with lobbies and stats, plus single-player arcade games with server-side leaderboards.
  • For developers: an extensive export surface, first-party events on every lifecycle moment, custom apps so any resource can ship its own phone app (with ready-made templates for plain JS, React and Vue), and a drop-in lb-phone compatibility layer covering exports, events, dependencies and lb-phone custom apps, with a one-command data migrator. The lb-tablet layer answers its dispatch and MDT exports the same way.

Framework support ​

The phone talks to the world through a bridge layer that auto-detects the running framework (qb-core, qbx_core, ESX, ox_core, ND) and the installed inventory, banking, housing, garage, and dispatch resources. Nothing framework-specific leaks into the apps themselves.

ox_core and ND are newer additions. ox_core needs its group types mapped to jobs and gangs in configs/framework.lua; ND needs no configuration at all, because nd_groups already flags which groups are jobs. Neither backs every feature: see the boot message the phone prints on startup for exactly what is and is not wired on yours.

Getting started ​

Head to Installation for dependencies and setup, then Configuration for the per-app config walkthrough.