• Projects 6
  • Rating 3.9
  • Rating 776

Budget: 9999 UAH Deadline: 21 days

Andriy, you are transitioning from Bubble to a full-fledged Next.js frontend to eliminate the limitations of the builder and gain complete control over speed and SEO. This requires careful integration with the existing FastAPI via REST and proper handling of complex states, such as an admin panel or payment integrations.

My plan is to migrate the page structure to the App Router, set up authorization with roles, and adapt the design considering new features like fiscalization or integration with delivery services. I will work according to a phased plan: first, the basic frontend for the existing API, then the integration of additional modules.

Do you have up-to-date documentation for the current FastAPI endpoints for quick frontend integration?

  • Projects -
  • Rating -
  • Rating 361

Budget: 9999 UAH Deadline: 7 days

Ready to take on the frontend migration.

I work specifically with this stack (Next.js 14 App Router, TypeScript, TailwindCSS, shadcn/ui). The fact that the backend on FastAPI is already functioning as a separate REST API will significantly simplify the work: we will pull in types, configure requests, and quickly assemble a new UI.

Regarding the main part:

I will build a convenient responsive UI for the client side and admin panel.

I will set up route and role protection (admin/client) through Next.js Middleware.

  • Projects -
  • Rating -
  • Rating 342

Budget: 9999 UAH Deadline: 5 days

Hello.
As you can see in my portfolio, I have extensive experience with Next.js 14+ (App Router), React 18+, TailwindCSS, shadcn/ui, and TypeScript.
I promise to achieve perfect results using my experience and skills.
I look forward to a long-term collaboration.
Thank you.

  • Projects 13
  • Rating 4.9
  • Rating 6 949

Budget: 9999 UAH Deadline: 4 days

Hello, I am ready to help with the migration of the frontend from Bubble.io to Next.js 14 App Router, React, TypeScript, TailwindCSS, and shadcn/ui. I have relevant experience in full-stack development and transferring interfaces to a modern React stack without changing the existing REST API. I envision the implementation as follows: first, recreate the structure of pages and components in Next.js, then connect the existing FastAPI backend through typed API requests. I will separately check responsiveness, form states, navigation, and compliance with the behavior of the current Bubble frontend. I can quickly get into the project and work carefully, without unnecessary interference in the backend. A couple of examples: https://chess-217-154-170-186.nip.io/ https://zem.center/

github.com/onyx144

  • Projects -
  • Rating -
  • Rating 472

Budget: 9990 UAH Deadline: 10 days

Good day!

I have reviewed the task, and at this stage, everything is clear.

Experience: 3+ years of full-stack development, specializing specifically in Next.js/React/TypeScript, with complete production projects on this stack, including work on admin panels, role-based authorization, personal accounts, and integration of external APIs.

What I would like to clarify before estimating the scope:
How many pages/screens are approximately in the current Bubble site (an estimated number to assess the scale)?
Is there already prepared documentation/API schema from FastAPI, or will I need to figure out the endpoints myself during the migration?
Payment integration, which provider is currently used in Bubble, do I need to keep the same one, or can it be changed?

  • Projects -
  • Rating -
  • Rating 385

Budget: 9600 UAH Deadline: 21 days

Good day. I see that the backend on FastAPI is already ready as a clean REST API and does not depend on Bubble - this simplifies migration, as the frontend simply switches to existing endpoints without rewriting logic.

Approach: I will set up Next.js 14 on App Router, break down the pages and admin panel into shadcn/ui components with Tailwind, and separately create an authorization layer with roles (client/admin) using tokens from your API. The admin panel for managing templates and scenes will be moved to a separate section with its own navigation to avoid mixing with the client part. I will connect payment integration and email newsletters through existing providers if they are already set up on the backend - I will simply call the necessary endpoints from the frontend.

The basic scope (pages, authorization, dashboard, admin panel) can realistically be completed in 21 days, while payments/email/SEO and additional adjustments will be handled in separate stages after agreeing on the details.

Similar to this, I worked on Boseco, a service request management platform with role separation and an admin part, where the frontend also operated separately from the backend logic via REST.

Please let me know if there is already a ready design/layout of the current pages from Bubble for transfer, or should I create it from scratch based on a reference?

  • Projects -
  • Rating -
  • Rating 556

Budget: 9876 UAH Deadline: 14 days

Hello Andriy!

I can perform the migration to **Next.js 14 (App Router), React, TypeScript, TailwindCSS, and shadcn/ui** with connection to the already prepared FastAPI REST API.

I can also take on:
— responsive layout for all pages;
— personal account and role-based authorization;
— SEO optimization for Next.js;
— payment system integration;
— improvements to the admin panel;

  • Projects 43
  • Rating 5.0
  • Rating 3 182

Budget: 9999 UAH Deadline: 10 days

Good day, I am well acquainted with the stack you want to use for the new website, so I will create a new frontend and connect it to the existing backend without any issues.

  • Projects 33
  • Rating 5.0
  • Rating 8 257

Budget: 9999 UAH Deadline: 14 days

It is necessary to completely replace the Bubble frontend with a modern Next.js 14 stack, keeping the existing FastAPI backend unchanged.

Approach: first, an audit of all Bubble pages and mapping to App Router routes, then implementing auth via JWT with role-guard middleware (admin/client), followed by components on shadcn/ui + Tailwind. I will move the payment integration to a separate server action with an idempotency key to avoid double charges on repeated requests. SEO will be handled through generateMetadata at the level of each layout. I will implement i18n for the English version using next-intl with a separate locale segment in the URL.

A risk to consider: if there is complex workflow logic on the frontend in Bubble that effectively replaces the backend, it needs to be either transferred to FastAPI or implemented in Next.js API routes before starting the migration.

How many pages are there in total, and are there already design mockups (Figma or at least screenshots of the Bubble site)?

The list does not show proposals concealed by the client or freelancer with a Plus profile, as well as proposals violating rules