Build and test a custom booking app with Emergent

Write the booking requirements before generation

Thanks to Emergent for sponsoring this video.

Luke builds the subset of a booking tool he uses, including meeting lengths, prices, admin login and calendar support. Owning the code also makes maintenance part of the job.

1. List meeting types, lengths, prices and availability rules.
2. Specify the intended admin access and confirmation behaviour.
3. Build the first version using the demonstrated Emergent route.
4. Complete a test booking before adding further options.

Test timezones and integrations deliberately

The recording finds and repairs a timezone bug. A booking that looks right in the builder can still display the wrong time to a visitor.

1. Test each meeting duration and its displayed price.
2. Compare the chosen slot, confirmation and calendar entry.
3. Repeat with a different visitor timezone.
4. Fix the reproduced mismatch and repeat the same cases before release.

Keep payment testing and publication distinct

The original video demonstrates a real $1 payment and publishing. That is evidence from the recording, not an instruction to make an unapproved live charge.

1. Use the provider’s supported test route while developing the payment flow.
2. Inspect success, cancellation and failed-payment behaviour.
3. Verify the saved booking and confirmation agree with the payment result.
4. Review the live configuration and deployment independently before accepting customer bookings.

The takeaway

The example shows a working custom flow and a repaired bug. It does not establish a complete replacement for every booking platform or remove the need for ongoing maintenance.