Description
A property-listings phone app: players browse for-sale and rental properties with photos and filters, book a viewing in a real time slot, and contact the listing agent. It is the discovery layer over a server's existing housing economy — the storefront, not the ownership system itself.
Prompt Template
You are writing a FiveM resource for esextended (exports['esextended']:getSharedObject()).
The full prompt template and its reference Lua are part of a one-time pack. Pick your depth — both are lifetime access, no subscription, ever.
- 60 prompts + syntax-validated reference Lua
- Lifetime access — pay once
- All 510 prompts — the full library
- Per-prompt profit/trend intelligence (CSV + playbook)
- Lifetime free updates — new niches as the market moves
$49 for 60 · $199 for all 510 + intelligence — one-time, no subscription.
Expected Output
The reference Lua lives at content/expected-outputs/phone/22-property-listings-app.lua. It implements a server-held catalog with type/price/beds filtering, slot-validated viewing bookings that reject…
The full prompt template and its reference Lua are part of a one-time pack. Pick your depth — both are lifetime access, no subscription, ever.
- 60 prompts + syntax-validated reference Lua
- Lifetime access — pay once
- All 510 prompts — the full library
- Per-prompt profit/trend intelligence (CSV + playbook)
- Lifetime free updates — new niches as the market moves
$49 for 60 · $199 for all 510 + intelligence — one-time, no subscription.
Known Failure Modes & Corrective Prompt
- Client-trusted catalog — Claude filters and books on the client; players double-book or fabricate listings. Keep the catalog, filtering and slot booking server-side.
- Anim before load —
TaskPlayAnimno-ops if the dict is not loaded; alwaysRequestAnimDict+while not HasAnimDictLoaded(dict) do Wait(0) end. - One-sided net event — defining
props:showListings/viewingConfirmedon only one side breaks the booking round-trip; both client and server useRegisterNetEvent+AddEventHandler.
Corrective re-prompt: "Keep the catalog and bookings on the server: filter listings server-side, validate that a booked slot belongs to the listing and is free before reserving it, and relay the agent handle on contact. The client must only render and send requests. Never store the catalog or book slots on the client."
Framework Integration
- ESX: as written —
exports['es_extended']:getSharedObject()andESX.GetPlayerFromId(src)for the contact relay. - QBCore: swap to
exports['qb-core']:GetCoreObject()andQBCore.Functions.GetPlayer(src); the catalog/booking logic is identical. - QBox: use
exports.qbx_core:GetPlayer(src); listings, filters and slot validation are unchanged.
Profit Potential
$150–$2000/mo on Tebex (expected ~$500). [INFERRED] priced inside the $50-389 script band against the signal-scraper tebex_snapshot corpus (n=100, median seller $11.85K/mo); a stable housing-RP niche with steady unit volume.
Trend Signal
→ stable — inferred: Phone front-end to the housing economy — the discovery layer, not the ownership system.
Sales Angle
The discovery front-end to whatever housing system the server already runs — browse, filter, book a viewing without replacing the ownership backend. Recommended Tebex price $169.
Difficulty & Ship Time
intermediate · ships in 3-5h.