NIMNEXUS

User manual

How to use the attendee app and the event admin backoffice, and how to run a test pass against them. Written for release 1.0.

Version 1.0 Demo tenant: Krungsri Tech Day 2026 No backend

Where to start

Two addresses, one for each audience. Both are ordinary web pages — nothing to install, no app store, no account to create.

Attendee · phone
Mobile app
https://nimnexus.srv1791075.hstgr.cloud/

Open it on a phone. On a desktop browser it appears inside a phone-shaped frame, which is fine for review but test the real thing on a handset where you can.

Organiser · desktop
Event admin
https://nimnexus-admin.srv1791075.hstgr.cloud/

Built for a laptop screen. It works down to phone width — the sidebar collapses to icons and wide tables scroll — but the tables want room.

Password required
Getting into the admin

The backoffice asks for a username and password in a browser dialog before it loads. Those credentials are handed out separately — they are not written on this page. The attendee app needs none.

Everything is loaded with one invented event: Krungsri Tech Day 2026, theme AI for Humanity, Wednesday 7 October 2026 at Samyan Mitrtown, Bangkok. Both surfaces read the same event, so a ticket tier you rename in the admin is the tier an attendee is offered.

Attendee app

Eight screens covering the journey from finding an event to rating it afterwards. Tap through them in order the first time — later screens assume you have a ticket.

  1. Discover

    The opening screen lists events. Search by name, topic or partner, and narrow with the This week, Free and Onsite chips. Only Krungsri Tech Day 2026 is open for registration; tapping the others tells you registration opens soon.

  2. Event detail

    Date, venue, host and headcount, then the description, the speaker strip (swipe it sideways), a four-item agenda preview and the ticket prices. Get tickets at the bottom moves you on.

  3. Select ticket

    Pick one of three passes, set a quantity, and fill in your details. Type your own name in Full name — it carries through to the e-ticket, the check-in screen and your profile, which makes it easy to find yourself later. The PDPA consent box is ticked by default.

  4. Payment

    What you see depends on the pass. A free pass shows a confirmation note and no payment fields. A paid pass offers card, PromptPay and bank transfer — choose PromptPay to see the QR, or bank transfer for the account details. The button label always states the exact amount.

  5. E-ticket

    Confirmation, a QR code and your booking reference. Add to Apple Wallet is a visual placeholder: it confirms on screen but does not write a real pass.

  6. My schedule

    The full nine-session agenda. Tap a star to add or remove a session; the count shows on your profile. The banner at the top takes you to check-in.

  7. Check in

    The QR you would show at the 5th-floor desk. Pressing I've arrived — check in flips the status pill to Checked in and marks you present on the schedule. It is one-way — to test it again, reload the page.

  8. Feedback

    A star rating, a recommendation score and an optional comment. Submit feedback stays disabled until you have given a star rating, which is deliberate.

Moving around

The bottom bar switches between Discover, My tickets and Profile. Use the arrow at the top left to go back a screen — on a phone you can also swipe in from the left edge.

Event admin

Eight sections in the left sidebar. Unlike the attendee app there is no required order — go where the job is. The number beside each entry is how many records it holds.

Dashboard

Four figures — registrations, ticket revenue, check-in percentage and days to the event — over an agenda snapshot and a live list of the most recent arrivals. Every number is derived, so it moves as soon as you change anything.

Event setup

Details edits the name, tagline, date, time, venue and description; saving updates the bar at the top of every screen. Access & visibility controls which groups may register — Employees, Affiliates, Partners, Public — and states the resulting policy in a sentence underneath.

Agenda & sessions

The nine-session programme with track, speaker, capacity and status. + Add session opens a form; time and title are required. New sessions save as Draft and drop into the right place in the running order automatically.

Speakers

Twelve speakers as cards, each showing organisation, assigned session and whether they are Confirmed or still Invited. New speakers start as Invited.

Exhibitors & booths

Fourteen partners across booths A1 to C4, with category and confirmation status. New exhibitors start as Pending.

Registrations

The full list, newest first, 25 per page. Search by name, filter by segment, and check anyone in with the link at the end of their row. Each attendee carries a booking reference under their name — names repeat at this volume, so the reference is what identifies a person.

Check-in

The door view: how many are in, the rate as a bar, and how many are still expected. Search for a name and check them in. Cancelled bookings are hidden here; waitlisted ones are shown but cannot be admitted.

Reports

Registrations by segment and revenue by ticket tier. The free tier shows a full-width grey bar rather than an empty one — it earns no revenue by design, which is not the same as having no data.

Running a test pass

Four controls exist purely so the product can be tested end to end. They are part of the 1.0 test build, not of the eventual product.

The demo clock

Top right of the admin, Pre-event / Event day. A real event only reaches the check-in state once, on one morning; this switch lets you visit both states on demand. Pre-event shows nobody checked in and counts down the days. Event day shows roughly three-quarters of attendees already through the door. Anyone you check in by hand stays checked in across both.

Reset demo data

Bottom left of the admin sidebar. Returns everything to the seeded baseline — added sessions and speakers disappear, manual check-ins are undone, edited event details revert. Use it between test runs so each one starts from the same place.

Suggested scenarios

Try thisExpected result
Add a session with no titleRefuses to save and says time and title are required
Add a session at 14:15Appears between Lunch (12:00) and Responsible AI (15:00), not at the end
Filter registrations to Partner, then searchSearch applies within the filter; the count updates; paging resets to page 1
Check someone inDashboard check-in percentage rises, they appear in Recent check-ins, the row's link disappears
Turn off Public under Access & visibilitySummary sentence lists only the three remaining groups
Flip the demo clock to Pre-eventCheck-in rate drops to 0%, revenue is unchanged, days-to-event counts down
Rename the event and saveNew name shows in the bar at the top of every admin screen
Book a free pass in the attendee appPayment screen shows no card fields; the button reads Confirm registration

About the data

Everything you see is invented, and generated the same way every time.

WhatHow muchNotes
Registrations264248 active, plus cancellations and a workshop waitlist
Sessions909:00 to 16:45, across Main Stage, Solution Stage and Workshop Center
Speakers12Confirmed and invited
Exhibitors14Booths A1–C4
Ticket tiers3Tech Day Pass free · Workshop Pass ฿1,200 · Executive Summit Pass ฿3,500

The 264 registrations come from a fixed seed, so every tester sees the same list in the same order. That is what makes a bug report reproducible: if you write down a booking reference, the person opening the report will find the same record.

Nothing here is real

All names, speakers, partner companies, artwork and figures are invented for demonstration. No real personal data is collected, stored or transmitted. This is not an official Krungsri product.

Known limits

Release 1.0 is a working front end. Knowing what is deliberately absent saves you filing it as a defect.

No server, no accounts

There is no backend and no sign-in. Nothing you enter leaves your browser, so two people testing at once will not see each other's changes.

Changes are per-browser

The admin remembers your work in that browser, so a reload keeps it. A different browser, a different device, or a private window starts from the seeded baseline again.

Payment is a mock-up

No card is charged and no PromptPay QR is real. Never type a genuine card number, and treat the QR codes as artwork — they are generated patterns, not scannable codes.

Wallet and email do nothing

Add to Apple Wallet confirms on screen only. No confirmation email or SMS is sent at any point.

One event

The other events on the Discover screen are there to prove the list works. Only Krungsri Tech Day 2026 can be opened and booked.

English only

No Thai interface yet, though the content and currency are Thai.

Reporting a problem

A report someone else can reproduce is worth several that they cannot.

Include these five things:

Which surface

Attendee app or event admin, and which screen or section.

Device and browser

For example "iPhone 15, Safari" or "Windows laptop, Chrome" — layout problems are usually specific to one.

Demo clock position

Pre-event or Event day. Several figures differ between the two, and a report without it can look wrong when it is not.

The exact record

The booking reference, session time or speaker name involved — not just "an attendee".

What you expected

What you did, what happened, and what you thought would happen instead.

Before you report a display problem

Press Reset demo data and try once more. The admin keeps your previous work in the browser, so an older test session can occasionally explain odd-looking figures.