phoenix
phoenixPhoenix - Your AI Assistant
Inactive session will be ended in 24 hours
End Session

Dental Practice UI Modernization & Speed Upgrade

  • Posted:
  • Proposals: 50
  • Remote
  • #4512778
  • Open for Proposals
Óscar P.Talha M.Osama Bin S.CYTNHIA W.Khalid H. + 45 others have already sent a proposal.
  • 5

Description

Experience Level: Expert
Looking for an experienced full-stack developer to modernize and upgrade our healthcare web platform. The main goal is to overhaul the front-end user interface using modern component-driven frameworks (React / Next.js) and lightweight styling (Tailwind CSS) to achieve fast loading speeds and flawless mobile responsiveness.

Key Responsibilities & Scope:
- Interface Rebuild: Developing a clean, responsive, and modern UI from scratch for service pages, practitioner directories, and location listings.
- Interactive Features: Integrating smooth multi-step appointment scheduling forms, interactive service calculators, and user-friendly navigation modules.
- Speed & Optimization: Ensuring top-tier Core Web Vitals performance, seamless content rendering, and robust URL redirection mapping to maintain smooth search engine indexing.
- Content Management Integration: Connecting the front-end to a secure, structured backend content repository for effortless daily management by our administrative team.

Please review the attached technical document for a detailed breakdown of milestones, architectural requirements, and project phases. Estimated timeframe is ~60-80 hours.

New Proposal

Login to your account and send a proposal now to get this project.

Log in

Clarification Board Ask a Question

  • Naresh S.

    Hi Amanda,

    I've reviewed the technical specification. Could you please confirm whether the existing backend APIs and CMS will remain unchanged, with this project focused only on rebuilding the frontend in React/Next.js + Tailwind? I'd also like to understand if there are any authentication or API changes planned during the migration so I can propose the smoothest implementation approach.

    Thanks,
    Naresh

  • Eight Veer Ltd

    Hi Amanda, which system will remain the source of truth for appointment availability, practitioner schedules and patient submissions after the migration, and will the Next.js frontend need real-time two-way integration with an existing practice-management platform, or only pass enquiries into WordPress?

    To begin immediately, we would need:

    - Access to the current website, code repository and a staging environment through a buyer-created, limited-access route.
    - The current URL/content inventory, together with the approved brand assets and any existing UI references.
    - Documentation for the booking, calculator and any third-party integrations, including sandbox or test access where available.

    Once these are received, we can begin immediately.

  • Artem B.

    Hi Amanda

    I checked your job details, and I have a few questions.

    Is this a complete frontend rebuild or a phased migration from the existing platform?
    Are the current designs being retained, improved, or replaced completely?
    Will you provide Figma designs, branding guidelines, and responsive layouts?
    Do you prefer Next.js App Router or Pages Router?
    Should the new frontend use server-side rendering, static generation, or a hybrid approach?
    Does the platform need authenticated patient or practitioner areas?
    Are there existing reusable components that should be migrated?
    What backend or CMS is currently being used?
    Should the existing backend remain, or do you expect backend modernization as well?
    Which CMS would you prefer for daily content management?