What you will set up.
Turn the responsive event experience into an installable, branded PWA with a cached static shell and connected attendee tools.
Before you begin
Back up the site, use staging and gather any provider credentials without placing secrets in page content.
ExploreWhat you will verify
Check the public result, affected account roles, empty and error states, and any schema, email or notification output.
ExplorePlan and package notes
This tutorial is for NexDirectory Pro. Free remains fully responsive in the browser. Pro adds PWA installation, custom app identity and cached branding and static assets; live attendee tools require connectivity.
Put this guidance into practice.
Confirm Pro and app identity
Install the separate Pro companion plugin, then choose the app name, icons, accent colour and access rules.
Choose the connected experience
Configure itinerary, chat, direct messages, Q&A, polls, presence, maps and calendar actions. A custom webhook is built in; OneSignal and Firebase require site integration code.
Test installation and updates
Install the PWA on a phone, confirm that branding and static assets load from the cached shell, then reconnect and test every live attendee tool.
Common questions.
Should I do this on a live site?
Use staging first, particularly for imports, payments, routing, profile changes and external service credentials.
Does this require Pro?
Yes. Pro adds the installable branded PWA, cached branding and static assets, custom identity and connected attendee tools. Live tools require connectivity.
Where can I troubleshoot the result?
Use the support centre and diagnostics guide, including your exact WordPress, PHP and NexDirectory versions.