Agency Phone v2 - New Features and Improvements

What Is New in v2

Agency Phone v2 represents the biggest update since the original launch. Based on extensive community feedback and months of development, this release brings a completely redesigned interface, new applications, deeper framework integration, and further performance improvements. Every aspect of the phone has been refined to deliver a more immersive and polished experience for players.

Redesigned User Interface

The v2 interface features a modern glassmorphism design language with smoother animations and improved visual hierarchy. The home screen now supports customizable wallpapers and app icon arrangements, letting players personalize their phone. Notifications have been completely reworked with a new notification center that groups alerts by app and supports quick actions directly from the notification. The overall look and feel brings the in-game phone much closer to what players expect from a real smartphone.

New Applications

Several new apps expand what players can do with their phone. A dedicated gallery app lets players save and view in-game screenshots. The notes app provides a simple but effective way to store information during roleplay. An improved banking app with transaction history and transfer capabilities gives players a complete mobile banking experience. The marketplace app enables player-to-player item listings, creating a new layer of economic roleplay.

Performance Improvements

While Agency Phone already maintained 0.00ms idle usage, v2 further optimizes active usage scenarios. The app loading system has been rearchitected to use lazy loading, meaning apps only initialize their UI components when actually opened. This reduces the memory footprint when the phone is open and results in faster app switching. The NUI communication layer has been streamlined to reduce the number of events fired between the client and interface.

Upgrade Path

Existing Agency Phone users can update to v2 through the standard Tebex download process. The migration is designed to preserve existing data including contacts, messages, and call logs. A detailed migration guide is available in the documentation, and the Agency Scripts Discord team is standing by to help with any upgrade questions. We recommend testing the update on a development server before deploying to production to ensure compatibility with your custom configurations.

Installation & Setup for v2

Upgrading from v1 to v2 follows a standard Tebex download update. Pull the new version from your Tebex library, replace the resource folder on your server, and restart. The migration script in sql/migrate_v1_to_v2.sql handles schema changes — run it once against your existing database before restarting the resource. Existing contacts, message history, and call logs are preserved.

If you're installing Agency-Phone for the first time on v2, import phone.sql, drop the resource folder, and add ensure agency-phone to server.cfg. The resource auto-detects QBCore or ESX. Standalone setups implement the adapter in config.lua.

Configuration Options in v2

The v2 config.lua is fully backward-compatible with v1 configs, with additional options for new features:

• Wallpaper library — specify allowed wallpaper URLs or enable the player-upload CDN endpoint.
• App icon layout — grid size (4x5, 4x6) and whether players can rearrange app positions.
• Notification center behavior — max stored notifications, swipe-to-dismiss threshold, quick-action buttons per app.
• Gallery storage — screenshot CDN endpoint and per-player storage quota (in MB).
• Marketplace settings — listing expiry duration, whether listings require admin approval, and transaction fee percentage.
• Banking app integration — connect to QBCore banking, ESX banking, or a custom banking function.
• Lazy loading — which apps use lazy initialization (all by default in v2) and whether to preload specific apps on phone open.

Framework Compatibility in v2

v2 maintains the same framework adapter pattern as v1. If you customized the adapter in v1, your changes carry forward — the adapter interface is unchanged. New apps added in v2 (gallery, notes, marketplace) all route through the same adapter functions. No new framework-specific implementations needed for the new features.

Why the v2 Redesign Matters for Roleplay

The v1 phone was already the best-performing FiveM phone on the market. v2's redesign addresses a different problem: the gap between how the phone looks and how a real smartphone feels. The redesigned home screen with customizable wallpapers and rearrangeable app icons is the first change players notice — but what it actually does is give players ownership over their phone's personality. A phone that feels personal is a prop that players invest in as part of their character.

The notification center redesign has the most practical impact on daily gameplay. In v1, notifications appeared as toasts and disappeared. In v2, they accumulate in a center with quick actions: accept/decline a call from the notification, reply to a message without opening the SMS app, approve a marketplace transaction. The reduced friction from fewer menu-opens-per-action compounds across a session into noticeably smoother phone use.

The marketplace app opens an entire economic layer that previously required out-of-character coordination. Players who want to sell items to other players list them in the marketplace; buyers browse and purchase without leaving the phone. Negotiation happens in DMs. Pickup coordination happens in SMS. The whole transaction is in-character, which is what transforms a transaction into RP.

What Didn't Change in v2

The core performance characteristics didn't change because they didn't need to. The 0.00ms idle usage, the framework-agnostic adapter pattern, the lazy-loading architecture — these are the foundations the v2 UI is built on. We added the new gallery, notes, and marketplace apps without touching the performance layer. v2 is heavier in features, not in resource usage.

The contacts, SMS, and calls apps are visually refreshed in v2 but functionally identical. Players who relied on specific behaviors in v1 — threading, group SMS, call logs — find the same behaviors in v2 with improved visual presentation. The migration is smooth for established communities specifically because we didn't change what was already working.

Frequently Asked Questions about v2

Can I revert to v1 if v2 causes issues on my server?

Yes, v1 downloads remain in your Tebex library. Your v1 database schema is compatible — the migration SQL only adds tables, it doesn't modify existing ones. Reverting means switching back to the v1 resource folder and ignoring the new tables. Not ideal, but safe if a critical compatibility issue arises in the first days of a v2 deployment.

Does the marketplace app require any special backend setup?

The marketplace uses the existing oxmysql database. No additional backend is needed. Listings are stored in a new phone_marketplace table created by the migration SQL. The marketplace is entirely server-contained with no external API dependencies.

Can admins moderate marketplace listings?

Yes. Enable the approval mode in config.lua and new listings appear in a moderation queue accessible through Agency-Admin or through the phone's own admin panel (accessible to players with the admin flag). This is recommended for servers where players might attempt to list prohibited items or circumvent in-game economy restrictions through the marketplace.

Is the gallery storage shared across characters on the same account?

By default, gallery storage is per-character, not per-account. Screenshots are associated with the character who took them. For multi-character systems where players want to share screenshots between characters, set Config.GalleryByAccount = true to use the player identifier instead of the character identifier as the storage key.

Requirements

• FiveM server (QBCore, ESX, or standalone)
• oxmysql
• cfx.re account with valid Agency-Phone license
• Photo CDN endpoint for gallery feature (optional, falls back to URL-only if not configured)