Back to Blog
Engineering3 min read

How We Optimized RegalScene for Flexibility, Performance, and Scalable Public Viewing

RegalScene Team·
performancescalabilityarchitecturetemplate engineoptimizationpublic viewer

As RegalScene evolved from a residential viewer into a flexible visual sales engine, we had to solve more than just UI changes.

The system needed to become template-driven, secure, scalable, and ready for different industries.

The latest upgrade focused on three major areas: flexibility, performance, and controlled public data delivery.

Template-driven architecture

Previously, many parts of the experience were based on residential assumptions such as units, bedrooms, bathrooms, floors, and residential lead actions. That works for housing projects, but it does not work for logistics zones, commercial districts, or industrial parks.

Now, the project template controls the inventory structure, asset types, display fields, CTA labels, lead forms, compare fields, and viewer behavior.

This means RegalScene can support different domains without rewriting the system for every client.

The template is selected during project creation and applies consistently across the admin dashboard, CSV import, visual editor, viewer, lead forms, and analytics.

Smarter inventory import and validation

The CSV import flow is now template-aware. A logistics project can require fields like asset type, clear height, loading docks, cold-chain readiness, and lease option, while a residential project can continue using residential fields.

The system validates imported data against the project template — ensuring that asset type values match the allowed types, status labels are resolved correctly, and required fields are present.

This helps keep data clean and prevents mismatched inventory from entering the wrong project type.

Controlled and lightweight public viewing

A public interactive map should deliver only the data relevant to the current view. It should not load the entire project inventory upfront, and it should respect admin settings for what information is publicly visible.

We changed the public resolve flow so the viewer receives only lightweight summaries for assets linked to the current scene. Full asset details are fetched only when the user clicks a linked asset, and even then, the response is filtered based on the project template and admin settings.

What this means in practice

  • The initial scene load is smaller and faster — only summary data for linked assets
  • Full detail including price, images, and custom attributes loads on demand
  • Price visibility is controlled by admin settings — if pricing is hidden, the data is not sent at all, not just hidden in the UI
  • Attachment URLs such as brochures and spec sheets are only included when the related CTA action is enabled
  • Unlinked inventory items are never exposed to the public viewer
  • Each asset detail request is verified against the scene's published overlays

For example, a project may contain hundreds or thousands of inventory records, but a scene may only need a small subset. RegalScene now avoids loading everything upfront.

Better overlay visibility

On the viewer side, we improved overlay visibility so available assets are easier to discover on aerial and satellite backgrounds, while reserved, sold, leased, and unreleased assets remain visually clear without creating noise.

Each inventory status has a distinct visual treatment with appropriate fill, border, and hover behavior — making the map immediately understandable without requiring a legend.

A stronger foundation

The result is a stronger platform foundation.

RegalScene is now more adaptable for different clients, production-ready for public and embedded usage, and better prepared for large-scale master plan experiences.

This upgrade is not just a feature update. It is a platform maturity step — ensuring that as RegalScene supports more industries and larger projects, the experience remains fast, scalable, and reliable for every user who interacts with it.