Back to Archive
Case StudyPlatformsUI / UX

SPIDS Week 2025 – Medical Conference Event Platform

A modern conference website for SPIDS Week 2025 in Saudi Arabia, designed to present event programs, speakers, registration details, and sponsor information with a professional and responsive UI.

Role
Lead Engineer
Timeline
Production
Industry
Web Platform
Status
Shipped
spids-week-2025
SPIDS Week 2025 – Medical Conference Event Platform
01Overview

What this system is

SPIDS Week 2025 is a medical conference platform built to showcase event schedules, speakers, registration workflows, and event information in a clean and organized interface. The project focuses on performance, accessibility, and structured content delivery for large-scale events. During my work at the company, I contributed to enhancing UI sections, improving responsiveness, optimizing components, and refining user experience across multiple pages.

02The Problem

What we needed to solve

The event required a professional digital platform to manage conference information, improve attendee experience, and provide clear access to program details, registration, and sponsorship opportunities.

03The Solution

How we shipped it

Enhanced and customized a React & Next.js based event platform by improving layout structure, optimizing reusable components, refining UI responsiveness, and updating multiple sections to align with the event branding and usability standards.

04Architecture

How the system is wired

A modular architecture separating presentation, application, and data layers with REST contracts between the frontend and backend. Designed for clean scaling, observability, and predictable deployments.

Data flow
01
Presentation

Server-rendered + responsive client UI with reusable components and animation primitives.

02
Application

Business logic in service classes, validated input, role-aware authorisation, and queueable side-effects.

03
Data

Relational schema with indexed lookups, soft deletes, and migration-backed evolution.

04
Integration

REST APIs, webhooks, and third-party SDKs surfaced through thin adapters.

05Tech Stack

Engineering choices

Frontend
Next.jsReactTypeScriptTailwind CSS
Backend
REST API
06Gallery

In the wild

SPIDS Week 2025 – Medical Conference Event Platform
SPIDS Week 2025 – Medical Conference Event Platform
SPIDS Week 2025 – Medical Conference Event Platform
11Challenges Solved

Hard problems, handled

Impact
Challenge 01

The event required a professional digital platform to manage conference information, improve attendee experience, and provide clear access to program details, registration, and sponsorship opportunities.

Resolution

Enhanced and customized a React & Next.js based event platform by improving layout structure, optimizing reusable components, refining UI responsiveness, and updating multiple sections to align with the event branding and usability standards.

Impact
Challenge 02

Maintaining performance under realistic production load.

Resolution

Indexed queries, paginated lists, image optimisation, and lean client bundles kept the platform responsive end-to-end.

12Performance

Built to stay fast

Optimised images and lazy-loaded routes for fast first paint.
Cached read-heavy endpoints and indexed all hot lookup paths.
Pruned unused dependencies and tree-shook client bundles.
Graceful loading states across every async surface.
13UI / UX

Design and interaction

Consistent design tokens — spacing, type scale, radii, motion curves.
Tuned for both desktop precision and mobile thumb reach.
Empty states, error states, and skeletons across every screen.
Reduced-motion fallbacks and accessible colour contrast.
14Production Readiness

Ready to ship and operate

Environment-scoped configuration with no secrets in source.
Migrations + seeders that recreate the full state from zero.
Error boundaries and logging on critical paths.
Reproducible builds, ready for CI deployment.
15System Features

What it does

Conference landing page with countdown and hero section
Event program and schedule pages
Registration and sponsor sections
Responsive multi-device layout
Optimized navigation and UI components
Dynamic content structure for event data
16Technical Decisions

Why we chose what we chose

Decision 01

Built on Next.js, React, TypeScript.

Mature ecosystem, strong typing where applicable, and predictable performance characteristics for the workload.

Decision 02

REST-first integration boundary.

Keeps clients (web, mobile, partner) decoupled and trivially swappable without coupling to a single transport.

17Outcome

Results

Production
Status
7+ features
Surface area
5 technologies
Stack depth

Building something similar?

Let's scope your platform — dashboard, mobile apps, APIs, the full stack.