Building iWeb Live

The brief

iWeb Live began with a clear brief: build a one-day tech conference platform that could support the whole event, not just promote it. It needed to introduce the conference, make the programme easy to understand, bring speakers and sponsors into one community, and help attendees plan their own day.

More than a landing page

A simple event landing page would have handled the date, venue and ticket information, but it would not have helped once somebody decided to attend. The experience needed to keep working before and during the event. That meant treating the programme, sign-in, personal schedules, meetings and updates as connected parts of one product rather than separate pages added around a homepage.

Two connected journeys

I broke the experience into two main journeys. The attendee journey starts publicly, with the event story, programme, speakers and sponsors. After signing in with the event password and an emailed one-time code, attendees move into MyLive, where they can build a timetable, request sponsor meetings and receive useful notifications during the day.

The organiser journey sits behind that experience. The control centre gives the team a practical place to manage the event information, programme, community, meeting requests and attendee communications without exposing that complexity to the people attending.

What I built

The platform includes the public event experience, a structured programme, speaker and sponsor community pages, attendee sign-in, MyLive personalised timetables, sponsor meeting requests, in-app notifications and the organiser control centre. I built the branded experience in Lovable around a Supabase-backed structure and authentication flow, so the public and signed-in areas could share one reliable foundation.

Keeping complexity calm

The main UX challenge was not adding the functionality. It was making that functionality feel calm, clear and easy to navigate. A conference day already asks people to process a lot of information, so the interface needed a strong hierarchy, direct labels and predictable routes. MyLive had to feel useful at a glance, while organiser controls needed enough depth without becoming difficult to manage.

What I learned

This project taught me more about designing systems that serve public and authenticated users at the same time. They have different needs, but they should still feel like they belong to the same experience. Clear boundaries around what is public, personal and organiser-controlled made the product easier to understand and helped each journey stay focused.

The biggest lesson was that complex functionality does not need to look complex. When the structure is considered properly, a system with schedules, access, meetings, notifications and administration can still feel straightforward to the person using it.