Revolico

Frontend and product UI for a high-traffic classifieds marketplace.

I worked across frontend engineering and product UI for Revolico, improving marketplace flows, admin interfaces, performance, feedback loops, and production reliability for a high-traffic classifieds platform.

Revolico Google Play

Role: Frontend Developer + Product UI/UX
Period: 2017-Present
Ownership: React/Next.js frontend, public-facing marketplace UI, admin interfaces, publishing/search flows, performance improvements, feedback mechanisms, testing, and product UI support.

25%

TTFB reduction

30%

stronger engagement metrics

1,000+

actionable user insights from feedback mechanisms

Revolico mobile search resultsMobile marketplace results with search, active filters, promoted listings, and view controls.

Revolico mobile listing detailListing detail view with product imagery, metadata, description, and direct contact actions.

Revolico mobile filter panelFiltering interface for category, location, and price constraints in a compact mobile flow.

Revolico tablet listing detailLong-form detail page showing listing content, media, metadata, and marketplace actions.

Revolico mobile detail page variationMobile listing variation with stacked content, related listings, and publishing context.

Problem

Keep a large marketplace searchable, fast, and understandable

A classifieds marketplace has to support many user intentions at once: browsing, searching, filtering, publishing, contacting sellers, managing listings, and navigating many categories.

In Revolico's context, the product also needed to remain fast and usable for users in Cuba, where connection quality can be a major constraint.

Users / context

Buyers, sellers, businesses, admins, and mobile users

Revolico serves buyers searching for products, services, housing, jobs, cars, technology, and general goods; sellers publishing ads; businesses seeking visibility; admins managing platform operations; and mobile users on web or app workflows.

Public descriptions emphasize direct buyer/seller contact, free ad posting, visibility, speed, broad marketplace categories, and optimization for Cuban connections.

Constraints

High traffic, broad categories, publishing speed, and modernization

Public marketplace pages needed to be reliable and performant across many categories, including vehicles, real estate, technology, jobs, services, home, family, and general goods.

The product had to support fast publishing, predictable search and filtering, admin moderation workflows, connection-quality constraints, and long-running modernization without breaking existing behavior.

Design decisions

Favor scanability, direct navigation, and performance-aware UI

Marketplace UI depends on repetition and confidence. Category navigation, listing title, price, context, images, and contact affordances needed to be easy to parse without decorative weight.

Publishing and admin flows needed clear form states, errors, progress, filters, permissions, and edit flows so the product could move quickly without creating operational ambiguity.

Keep category navigation direct.
Optimize listing scanability.
Support quick publishing with clear form states.
Treat admin UI as product UI.
Keep interaction patterns lightweight for performance.

Interaction / UI system

Marketplace components for search, listings, publishing, and admin workflows

The UI system can be shown through homepage/category navigation, search results, listing grids, ad detail pages, publish-ad flows, filters, sorting, pagination, admin user/listing management, moderation flows, promoted-ad surfaces, and mobile store screenshots.

The component angle includes marketplace cards, buttons, inputs, dropdowns, breadcrumbs, pagination, image selectors, category taxonomy UI, admin table/filter patterns, and performance-aware image handling.

Implementation collaboration

React/Next.js frontend work for a high-traffic marketplace

I worked as frontend developer and product UI contributor on public-facing features and admin interfaces.

The implementation included React/Next.js, Apollo Client, GraphQL, Styled Components, SSR/SSG, SuperTokens, i18next, Jest, Cypress, Cucumber, feedback mechanisms, performance work, backend/frontend collaboration, and testing coverage.

Outcome

Performance, feedback loops, and product reliability

Confirmed outcomes include 30% stronger engagement metrics from iterative releases and feedback-informed product work, approximately 25% TTFB reduction through performance and backend/frontend collaboration, and 1,000+ actionable feedback insights.

The work also improved reliability through test coverage and supported scalable React/Next.js development for a high-traffic classifieds marketplace.

Asset slots

Planned visual evidence

The page is structured for public marketplace visuals, anonymized admin views, and product-system artifacts.

Hero visual: public marketplace homepage, search, or listing screen.
Core flow: search/listing to detail to contact or publish flow.
Admin proof: blurred interface with tables, permissions, filters, or moderation flow.
System proof: buttons, filters, dropdowns, pagination, image selector, and listing card elements.
Performance and feedback proof: small visual blocks for TTFB reduction, engagement lift, and feedback loop.

Stack

Tools and implementation context.

Next.jsReactTypeScriptGraphQLApollo ClientStyled ComponentsSuperTokensi18nextJestCypressCucumberSSR/SSGPerformance optimization