The story
Frodor connects people who cook with people who want food at the door. The landing page had to say that fast: Chow, Chill, Connect, then show why the apps matter for customers and vendors. It was built as one warm page, not a dry brochure.
The Frodor landing page was built here, with help shaping the admin console: the site that sells the apps, and the tools ops use for orders, vendors, and rides.
The problem
Frodor needed a public face that felt as lively as the food, and an admin console ops could trust for vendors, orders, rides, and the menu.
What shipped
The live site opens with a hungry hero in more than one language. Features switch between customer and vendor stories. A marquee and FAQ answer the usual doubts. The CTA points people to the right store links. Header and mobile nav keep the path clear while you scroll.
How it was built
The landing page was built in React, Vite, Sass, and GSAP. Sections load cleanly, scroll stays smooth, and the layout holds up on small screens. The goal was a brand page ops and marketing could stand behind while the apps did the rest.
Admin console
Alongside the site, we worked on the ops console. Vendor verification lets reviewers check documents and approve or reject in one place. Order lists stay filterable under load, with update and reassign-to-chef behind a confirm. Ride requests get a dispatch board with filters and a vendor drill-in. Meal categories, templates, and home banners let ops edit the catalog without a deploy.
Outcome
- Visitors get one clear story from hero to download.
- Customer and vendor paths sit side by side without confusion.
- Ops can verify vendors, move orders, dispatch rides, and edit the menu in product, not in chat.
Stack, and why
- ReactShared UI language for the landing page and the admin console.
- SassCustom layout and type that fit the Frodor brand.
- GSAPMotion on the landing page that feels warm, not loud.