Implementing a Booking Date and Time Picker Component

When developing a booking service for a network of medical clinics, we found that every fifth patient lost their reservation due to a time zone bug. The server stored all dates in UTC, while the frontend converted them to local time with an error—slots shifted by an hour during daylight saving time transitions. An audit revealed that 95% of problems were related to conversion. This is a typical story: the UI calendar seems simple, but under the hood it requires real-time synchronization, time zone awareness, and double-booking protection. Without a solid architecture, users see unavailable slots or lose their bookings.

Problems We Solve

Time Zone Conversion

Server stores time in UTC, client displays in the user's local time zone. If conversion is incorrect, a user might book a slot for tomorrow but see it as today. Proper conversion is critical:

// Convert server UTC to user's local time
const localSlot = utcToZonedTime(slot.datetime_utc, userTimezone);
const displayTime = format(localSlot, 'HH:mm', { timeZone: userTimezone });

For multi-regional projects, we let users explicitly choose a time zone—this reduces errors significantly. In one project with 10 time zones, complaints about incorrect times dropped by 80% after adding an explicit selector.

Double-Booking

We use pessimistic locking: when a slot is selected, it is temporarily reserved for 10 minutes. If the user cancels or does not complete the booking, the lock is released. Under peak load, this is more reliable than optimistic locking.

For critical resources (e.g., doctors, hotel rooms) we choose pessimistic locking; for mass events where occasional collisions are tolerable, we use optimistic locking.

Backend lock implementation with Redis and TTL:

import redis

r = redis.Redis()

def reserve_slot(slot_id, user_id, ttl=600):
    key = f"slot:{slot_id}:reserved"
    if r.setnx(key, user_id):
        r.expire(key, ttl)
        return True
    return False

Typical implementation mistakes:

• Not handling daylight saving time: slots can duplicate or disappear.
• Storing timestamps in local format on the server—always use UTC.
• Forgetting lock timeouts: if the user closes the browser, the slot remains taken forever.

How We Do It (Case Study)

On a medical clinic project, we diagnosed that 95% of booking failures were due to time zone conversion bugs. We redesigned the backend to store all dates strictly in UTC and added a datetime_utc field to every slot. On the frontend, we used date-fns-tz to convert to the user's local time. For double-booking protection, we implemented pessimistic locking with Redis (10‑minute TTL). After deployment, booking loss dropped to nearly zero. The entire solution was built in 2 weeks.

Our Technology Stack

Frontend: React 18 / Next.js, TypeScript, date-fns-tz.
Backend: Laravel 11 or Django 4, PostgreSQL, Redis.
Infrastructure: Docker containers, CI/CD pipeline.

Comparison of popular date libraries:

What's Included in Our Work

• Development of a calendar component with range selection and exception handling
• Backend logic for time slots with Redis caching
• Booking API with server-side validation (availability, time zones)
• Component documentation and data schema
• Code coverage with unit and integration tests
• Deployment instructions

Our experience: over 10 years and 40+ successfully implemented projects. Clients typically reduce support incidents by up to 25%.

Process and Timelines

Estimation: We review your requirements and existing systems, then provide a fixed quote.

Implementation steps:

1. Collect data and analyze requirements
2. Design frontend and backend architecture
3. Develop and test the component
4. Deploy and verify on your infrastructure

Time estimates:

• Basic component for one resource: 2–3 business days
• Multi‑region support, complex recurrence logic, integration with external systems (CRM): up to 2 weeks

Cost is determined after a free consultation. Contact us to get started.

Step-by-Step: Time Zone Conversion (Our Approach)

1. Server stores all dates in UTC — no exceptions.
2. Client receives slot list with datetime_utc field and user's time zone (from profile or geolocation).
3. Using date-fns-tz on the frontend, convert each date to local time before rendering.
4. When submitting a booking, send slot_id only — the server determines UTC from the slot ID.

Get a consultation — our engineers will help you choose the best solution for your project. Request a quote for your booking component.

Frontend Development with React: From Audit to Production

Bundle grew to 3.1 MB gzip — that's a real figure from a project that came to us for an audit. The cause: moment.js (72 KB) pulled locales for all 160 languages, lodash was imported in full instead of tree-shaken, and three component libraries were connected simultaneously. TTFB was excellent, but TTI on mobile was 14 seconds. Users left, conversion dropped by 40%. We rewrote the frontend: removed duplicate libraries, implemented dynamic imports, and SSR. Result: bundle reduced to 850 KB gzip, TTI to 2.1 seconds, LCP to 1.8 s.

Frontend is not about "drawing prettily". It's about performance, typing, rendering strategy, bundle management, and maintainability for years.

Why is Next.js the Standard Choice for SEO?

React is our primary UI framework for complex interfaces. Next.js is the standard choice for projects with SEO requirements or SSR. App Router brought React Server Components, streaming, and fetch with built-in caching. Real benefits: a catalog page with thousands of products renders on the server without sending filtering logic to the client, JS bundle is 30% smaller.

But App Router is a different way of thinking. "use client" must be placed consciously. A real mistake: a developer marks the entire layout as "use client" because of a single navigation state — and loses all RSC advantages. Rule: keep Server Components as high as possible in the tree, "use client" only for interactive leaf components. ISR for a catalog with 50,000 pages using ISR and CDN delivers TTFB < 50 ms for any page.

How Does TypeScript Prevent Bugs in Production?

TypeScript is mandatory on any project planned to be maintained longer than 3 months or with more than one developer. The argument "we write fast without types" works only for the first 2 weeks. After that, bugs related to undefined values appear every week.

Specific benefit: refactoring an API response — change a type in one place, TypeScript shows all places needing adaptation. Without types, a production bug appears in a week. strict: true in tsconfig.json is mandatory. noImplicitAny, strictNullChecks, strictFunctionTypes. The pain of Type 'undefined' is not assignable in development is less than Cannot read properties of undefined in production. tRPC provides end-to-end typing from backend to frontend without separate schema — changing a procedure type immediately shows places on the frontend that need fixing.

Vue 3 + Nuxt 3 — An Alternative SSR Stack

Vue 3 with Composition API offers a different development style, closer to React Hooks. <script setup> and composables make code more reusable. Nuxt 3 is a framework for Vue with SSR/SSG, similar to Next.js. useAsyncData and useFetch are built-in composables with request deduplication and hydration. Auto-imports are convenient but can confuse during debugging. Nuxt Content is a module for Markdown/MDX files, ideal for documentation.

Hydration mismatch is a specific pain of SSR in Vue and React. Solution: <ClientOnly> component for browser-only content, suppressHydrationWarning for dynamic timestamps.

Performance: Metrics and Tools

Bundle analysis is the starting point. @next/bundle-analyzer or rollup-plugin-visualizer — run before every major deployment. Goal: no page should require > 200 KB JS gzip for first paint.

Dynamic imports for heavy components:

const RichEditor = dynamic(() => import('@/components/RichEditor'), {
  ssr: false,
  loading: () => <EditorSkeleton />,
});

Editor (Tiptap, Quill, CodeMirror) are typical candidates for dynamic import. Without this, they end up in the main bundle. React DevTools Profiler for finding unnecessary re-renders. React.memo, useMemo, useCallback are targeted tools. Premature memoization of everything adds overhead without benefit. Profile first, optimize later.

Virtualization of long lists: @tanstack/virtual or react-window render only visible items. Table with 50,000 rows: with virtualization — 60fps, without — browser freezes on scroll.

State Management: Without Overengineering

For most applications, it's enough to have:

• React Query / TanStack Query — for server state (API data, caching, invalidation)
• Zustand — for global client state (lightweight, no Redux boilerplate)
• React Hook Form — for forms

Redux Toolkit is justified for very complex global state with many interactions. For most tasks, it's overkill. Recoil, Jotai — atomic approaches for independent pieces of state.

How to Choose the Right CSS and Design System?

Tailwind CSS latest version is our standard choice for new projects. Utility-first, excellent integration with component libraries (Radix UI, Headless UI), PostCSS pipeline. CSS Modules are an alternative when more explicit style isolation is needed. Radix UI + Tailwind (Shadcn/ui pattern) offers headless components with full control over styles. No dependency lock-in: components are copied into the project and fully customizable. Storybook is used for documenting the component library.

React DevTools Profiler — the official tool from the React team.

Testing

E2E tests via Playwright — for checkout, authentication, critical forms. Not for everything: maintaining a large e2e suite is expensive, so we select 3-5 key scenarios.

What's Included in the Scope (Deliverables)

Every frontend project we deliver includes:

• Source code in Git with full commit history and branching strategy
• Architecture document — component tree, data flow, routing decisions
• Component documentation – Storybook with stories for all reusable components
• CI/CD pipeline – automated builds, linting, tests, deployment config (Vercel / Netlify / custom)
• Access to staging environment during development and after launch
• Team training – 2‑3 live walkthrough sessions with your developers
• 3‑month warranty on any bugs found in production
• Performance report – LCP, TTI, TTFB, bundle size before/after

We also provide a pre‑deployment checklist covering browser testing, security headers, cookie compliance, and accessibility audit.

Estimates and Scope

Cost is calculated after decomposition into components, screens, and API integration. We use N+1 estimation: add 20% for risks.

What Does a Typical Performance Audit Reveal?

A recent e‑commerce project had LCP of 4.2 seconds and a monthly cloud bill of $3,000. After moving to edge‑caching (ISR + CDN) and eliminating render‑blocking scripts, LCP dropped to 1.1 seconds, and the bill fell to $1,800. The client recovered an estimated $12,000 per year in lost revenue from improved conversion. That's the kind of before‑after we regularly deliver.

Comparing tools: Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. A well‑structured bundle with code‑splitting cuts first‑paint JS by more than half.

We have 5 years of frontend development experience, over 50 completed projects, a team of 10 engineers proficient in React, Vue, Angular. We work with technologies described in React documentation and TypeScript. Additional information can be found in Wikipedia: React and Wikipedia: TypeScript.

What Stack to Choose for Frontend Development with React?

We compare tools by real metrics. Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. Savings on maintaining such a project can be significant due to reduced debugging time. If you need a lightweight SPA with minimal cost, React + Vite is enough. For a content site with SEO, Next.js with ISR gives TTFB below 50 ms even with 50,000 pages.

Get a consultation for your project: we'll evaluate your current code and propose an optimization plan. Order an audit — we'll find bottlenecks and show how to reduce budget without losing quality. Contact us to start the discussion.