LoveUI Pro Roadmap

LoveUI Pro is the paid layer of LoveUI. It adds larger blocks, advanced examples, and complete product systems on top of the free component library.

The free library will continue to include the primitives and foundation pieces developers need every day. Pro is for the bigger screens and sections that usually take longer to build well: polished marketing blocks, app navigation, analytics, charts, dashboards, settings screens, auth flows, data views, and complete templates.

The goal is simple: give you clean source code you can install, read, edit, and ship in your own product.

Core components and foundational blocks will remain free and open source. Pro expands the registry with deeper, more complete versions.

What Pro Is For

LoveUI Pro is built for developers and teams who want to move faster without giving up control of their codebase.

Pro focuses on:

• More complete blocks for real product pages
• Pro versions of every major block category
• Advanced chart and analytics blocks
• Application navigation and dashboard systems
• Practical auth, settings, billing, and team screens
• Larger templates that connect blocks into full product flows
• Private registry access with installable source code

Pro is not a black-box design kit. It follows the same LoveUI model: install the source, keep what you need, and change anything.

What Exists Now

The Pro foundation is already in place.

Private Registry Access

LoveUI Pro has a protected registry path, checkout flow, access checks, login, and CLI token support. Pro users can install private registry items after signing in with the email connected to their purchase.

Current install paths include:

npx loveui-pro login --email you@example.com
npx loveui-pro add pro-area-chart

You can also use the regular CLI with the Pro namespace:

npx love-ui login --email you@example.com
npx love-ui add @love-ui-pro/pro-area-chart

Pro Charts

Charts are the first large Pro system.

Current Pro chart families include:

• Area charts
• Bar charts
• Line charts
• Pie and donut charts
• Radar charts
• Radial charts
• Scatter charts
• Funnel charts
• Treemap charts

These include many variations for labels, legends, stacked views, active states, dense data, custom axes, comparison views, and dashboard-style reporting.

The chart system also includes shared chart UI for palettes, responsive containers, legends, tooltips, and metric-friendly layouts.

Pro Blocks Already Started

Pro block work has started across practical page and app categories.

Current Pro block areas include:

• Header blocks for SaaS, commerce, and enterprise navigation
• Sidebar blocks for app shells, workspaces, mail-style layouts, and team switching
• Download blocks for products, platforms, release links, and integration discovery
• Stats blocks for analytics, metrics, growth, and reporting sections
• Command palette examples for app search, quick actions, async search, and AI-style launchers

These are the start of the larger Pro block library.

The Main Pro Direction

The next major push is to add Pro blocks across the full block library.

Free blocks give you strong starting points. Pro blocks should go deeper. They should feel closer to a finished production section, with better composition, more realistic content, stronger responsive behavior, and useful states.

For each block category, Pro versions should usually add:

• More complete layouts
• More realistic product copy and data
• Better mobile behavior
• More interaction detail
• More advanced variants
• Dark mode support
• Clean source structure
• Composition examples that show how the block fits into a real page

The public blocks are the foundation. Pro blocks are the production pass.

Pro Blocks For Every Category

LoveUI Pro is moving toward Pro versions for every major block category.

404

Pro 404 blocks will be more useful recovery screens, not just simple missing-page messages.

Planned directions:

• Product-style 404 pages
• Search and navigation recovery
• Suggested links and recent pages
• App-style empty route states
• Support and contact fallbacks

Auth

Auth blocks will expand into complete account entry flows.

Planned directions:

• Sign in and sign up screens
• Magic link and one-time code screens
• Password reset flows
• Team invitation screens
• Organization selection
• Account handoff and success states

Blog

Blog blocks will support content-heavy sites, changelogs, product updates, and editorial pages.

Planned directions:

• Article index layouts
• Featured post sections
• Category and tag layouts
• Author cards
• Changelog-style feeds
• Newsletter and content CTA sections

Contact

Contact blocks will go beyond a basic form.

Planned directions:

• Sales contact pages
• Support request flows
• Office and location layouts
• Community/contact hub pages
• Multi-step contact forms
• Success and error states

CTA

CTA blocks will focus on conversion moments across marketing and product pages.

Planned directions:

• Trial signup sections
• Demo request sections
• Newsletter capture
• App download CTAs
• Upgrade and billing CTAs
• Product launch CTAs

Download

Download blocks are already started in Pro and will become a larger system for software, plugins, and product releases.

Planned directions:

• OS-specific download cards
• Version and release metadata
• Requirements and compatibility
• Plugin marketplace layouts
• Integration search
• Update and release note links

FAQ

FAQ blocks will support support pages, pricing pages, product pages, and docs.

Planned directions:

• Pricing FAQs
• Product onboarding FAQs
• Support category FAQs
• Accordion and split-page layouts
• Searchable FAQ sections
• Contact fallback states

Features

Feature blocks will expand into richer product storytelling.

Planned directions:

• Product capability grids
• Feature comparison layouts
• Interactive feature sections
• Screenshot-led feature blocks
• Benefit and outcome sections
• Persona-specific feature groups

Footer

Footer blocks will support more complete product and company navigation.

Planned directions:

• SaaS footers
• Developer tool footers
• Commerce footers
• App store and download footers
• Large resource menus
• Newsletter and social sections

Header

Pro header blocks are already started. This category will continue to grow because navigation is one of the highest-impact parts of a real product page.

Planned directions:

• SaaS headers
• Commerce headers
• Enterprise platform headers
• Product menu navigation
• Account actions
• Search and cart patterns
• Mobile navigation drawers
• Theme and utility controls

Hero

Hero blocks will include stronger first-screen product storytelling.

Planned directions:

• SaaS product heroes
• Launch page heroes
• Dashboard preview heroes
• Developer tool heroes
• Waitlist heroes
• App and mobile product heroes
• Conversion-focused hero variants

Image Gallery

Image gallery blocks will support product visuals, portfolios, media grids, and commerce galleries.

Planned directions:

• Product screenshot galleries
• Responsive media grids
• Portfolio layouts
• Commerce galleries
• Editorial galleries
• Lightbox-ready compositions

Integrations

Integration blocks will support product ecosystems and connected-tool pages.

Planned directions:

• Integration directories
• Search and filter layouts
• Integration detail sections
• Connected app grids
• Partner and tool matrices
• Setup and connection states

Logo Cloud

Logo cloud blocks will support customer proof, partner proof, and social trust.

Planned directions:

• Customer logo rows
• Partner matrices
• Animated logo strips
• Industry-grouped logo clouds
• Proof sections with metrics
• Case-study linked logo groups

Onboarding

Onboarding blocks will support product setup, activation, and first-run experiences.

Planned directions:

• Setup checklists
• Multi-step onboarding screens
• Progress summaries
• Empty states with next actions
• Workspace setup flows
• Product activation flows

Pricing

Pricing blocks will become a deeper Pro system because pricing pages often need more than static cards.

Planned directions:

• Plan comparison tables
• Monthly/yearly toggles
• Usage-based pricing sections
• Enterprise sales CTAs
• Checkout handoff sections
• FAQ and trust sections
• Billing-page variants

Sidebar

Pro sidebar blocks are already started. This category will keep expanding into complete app navigation systems.

Planned directions:

• Collapsible app sidebars
• Workspace and team switchers
• Nested navigation
• Notification navigation
• Account menus
• Mail and inbox layouts
• Mobile app navigation

Stats

Stats blocks are already started in Pro and will continue to grow with more dashboard and marketing uses.

Planned directions:

• KPI sections
• Growth metrics
• Revenue summaries
• Usage stats
• Team and product metrics
• Comparison cards
• Analytics-ready metric layouts

Testimonials

Testimonial blocks will support stronger proof sections for product pages, launches, and agencies.

Planned directions:

• Customer quote grids
• Founder quote sections
• Case study previews
• Rotating testimonial layouts
• Logo and quote combinations
• Persona-based proof sections

Command Palette

Command palette blocks are already started in Pro and will become part of the application system.

Planned directions:

• App navigation commands
• Quick actions
• Recent actions
• Async search
• Grouped results
• AI command launchers
• Keyboard-first workflows

More Pro Blocks Being Added

In addition to Pro versions of existing block categories, LoveUI Pro will add new block families for product teams building full applications.

Dashboard Blocks

Dashboard blocks will help teams build SaaS products, admin panels, internal tools, and analytics pages.

Planned blocks:

• Dashboard overview pages
• KPI card grids
• Revenue panels
• Usage summaries
• Activity feeds
• Notification panels
• Team overview sections
• Chart dashboards

Data Blocks

Data-heavy products need more than a basic table.

Planned blocks:

• Advanced tables
• Filter bars
• Bulk action toolbars
• Column visibility controls
• Empty and loading table states
• Export action patterns
• Detail drawers
• Audit and activity logs

Forms And Workflow Blocks

Pro will include larger form and workflow patterns for settings, onboarding, checkout, and internal tools.

Planned blocks:

• Multi-step forms
• Review steps
• Settings forms
• Billing forms
• Dynamic field groups
• Success and error states
• Confirmation screens

Team And Workspace Blocks

Modern products usually need teams, organizations, roles, and shared workspaces.

Planned blocks:

• Team member lists
• Invite flows
• Role and permission screens
• Workspace switchers
• Organization settings
• Seat and member management
• Access request states

Billing And Account Blocks

Billing and account pages should feel polished, not like an afterthought.

Planned blocks:

• Plan management
• Subscription status
• Invoice history
• Payment method cards
• Usage and limit panels
• Upgrade and downgrade flows
• Account profile screens

AI Product Blocks

AI products need recurring interface patterns that are still easy to customize.

Planned blocks:

• Chat layouts
• Conversation history
• Prompt builders
• Model selectors
• Usage and credit panels
• Generated output views
• Feedback and rating flows
• AI command interfaces

Commerce Blocks

Commerce blocks will support storefronts, digital products, subscriptions, and checkout flows.

Planned blocks:

• Product grids
• Product detail sections
• Cart drawers
• Checkout layouts
• Order summaries
• Collection pages
• Product galleries
• Account order history

Documentation Blocks

Documentation blocks will help teams build polished docs, changelogs, and developer portals.

Planned blocks:

• Docs navigation
• API reference layouts
• Changelog pages
• Version switchers
• Code example sections
• Search result layouts
• Developer onboarding sections

Complete Templates

Templates are the long-term layer above Pro blocks. A template combines components, blocks, pages, and example data into a complete starting point.

Planned templates include:

• SaaS dashboard template
• Admin dashboard template
• AI application template
• Documentation platform template
• Commerce template
• Marketing launch template

Each template should include:

• Routing structure
• Responsive layouts
• Theme support
• Auth and account screens where useful
• Example data
• Reusable page patterns
• Clear component composition
• Source code you can own and edit

Quality Standard

Every Pro block should feel closer to production than a simple example.

Pro releases should aim for:

• Responsive desktop and mobile layouts
• Dark mode support
• Accessible interaction patterns
• TypeScript-ready code
• Clean file structure
• Realistic content and data
• Loading states where they matter
• Empty states where they matter
• Error states where they matter
• Theme compatibility
• CLI installation support

The standard is not "more decorative." The standard is "more useful in a real product."

How Free And Pro Work Together

LoveUI will keep a clear split:

• Free components are the foundation.
• Free blocks are strong starting points.
• Pro blocks are deeper, more complete, and more specialized.
• Pro systems combine blocks into full product surfaces.
• Pro templates combine systems into application foundations.

The full path is:

Component → Block → Pro Block → Page System → Template

That is the direction of LoveUI Pro.

Roadmap Notes

This roadmap describes the current direction for LoveUI Pro. Scope, names, release order, and exact block counts can change as the registry grows.

The principle will stay the same: LoveUI Pro should help developers ship polished interfaces faster while keeping full ownership of the code.