Frontend & UX
Modern frontend and UX that converts
Magento's legacy frontend (Luma, Blank) is obsolete: heavy, slow and with mediocre UX. We build frontends with Hyvä Themes — 10x faster than Luma, no Knockout.js, with Alpine.js and Tailwind. Or if you prefer, 100% custom design from scratch.
Hyvä Themes — the modern frontend for Adobe Commerce
Hyvä replaces Luma with a modern stack: Tailwind CSS + Alpine.js + no jQuery, no Knockout.js, no RequireJS. The result: ~50kb of JS instead of ~1MB. Perfect Core Web Vitals. 10x better developer experience.
We're official Hyvä licensees and have shipped dozens of stores on this stack across Mexico and LATAM.
- JS <100kb total (vs 1MB+ on Luma)
- Tailwind CSS for styling
- Alpine.js for interactivity
- LCP < 1.5s on product pages
- Lighthouse score 95+
- 2x faster dev velocity
UX/UI that converts
A pretty design without conversion data is art, not design. Our UX process includes research with real users, wireframes, navigable prototypes, moderated usability tests and post-launch heatmaps.
- User research with interviews
- Wireframes + Figma prototypes
- Usability tests with 5-8 users
- Post-launch heatmaps (Hotjar)
- A/B testing of variants
- Data-driven iterations
Obsessive performance (Core Web Vitals)
Google penalizes slow stores in ranking. Users abandon if LCP > 3s. Our builds target LCP < 2s, CLS < 0.1, INP < 200ms. Continuous monitoring with Real User Monitoring.
- LCP < 2s (target 1.5s)
- CLS < 0.1 (no layout shift)
- INP < 200ms (interactivity)
- Lazy-loaded images + WebP/AVIF
- Inlined critical CSS
- RUM with web-vitals.js
Alternatives: custom frontend or PWA Studio
Beyond Hyvä, we build 100% custom frontends (React, Next.js, Vue) if the project justifies it. For very specific cases we use Adobe PWA Studio (headless Magento with GraphQL). We help you pick the right one.
- Next.js + Magento GraphQL (headless)
- Vue Storefront (headless)
- Adobe PWA Studio (official)
- Nuxt.js for SEO-first
- Custom React with SSR
Accessibility (WCAG 2.1 AA)
Accessibility isn't optional — it's a legal requirement in several countries and it's the right thing to do. All our frontends meet WCAG 2.1 level AA: contrast, keyboard navigation, screen readers, aria-labels.
- AA contrast on all text
- Full keyboard navigation
- Screen reader compatible (VoiceOver, NVDA)
- aria-labels on interactive components
- Visible focus and logical order
- axe-core audit in CI
Frequently asked questions
- Does Hyvä work with my existing Luma modules?
- Hyvä replaces the frontend, not the backend — all your backend modules keep working. For Luma modules with a custom frontend, there are official ports or we port them ourselves. Hyvä has an ecosystem of ~300 compatible modules that grows every month.
- How much does a Hyvä license cost?
- €1,000 EUR one-time per domain for commercial use (very cheap vs what you gain in performance). As a partner we help you acquire it and build it into the process.
- Can I have a headless checkout but keep the catalog on Luma?
- Technically yes, but it fragments the experience and doubles maintenance. We recommend migrating everything to the same frontend. If you already have Luma consolidated and want to move to Hyvä gradually, we start with checkout (biggest impact) and then catalog.
Related services
Adobe Commerce
Adobe Commerce (formerly Magento) implementation with all native capabilities: catalog, checkout, payments, promotions, Page Builder and more.
Learn more →Adobe Commerce B2B
B2B stores with purchase lists, quotes, approvals, customer-specific pricing and corporate account management.
Learn more →Adobe Experience Manager (AEM)
AEM Sites + Assets + Forms and Adobe Target: enterprise CMS, DAM and personalization at scale for omnichannel experiences.
Learn more →Adobe Experience Platform
AEP + Real-Time CDP + Customer Journey Analytics + Analytics + Data Collection: unified data architecture to activate real-time personalization.
Learn more →Want to discuss your project?
We'll assess your case at no cost and propose a concrete path forward.
Book a call