# Amelia templates: the market, the thirty-template collection, and what comes next

Research conducted September 8–9, 2026 using official galleries, marketplace listings and product documentation. Marketplace counters are dated observations, not live totals. The current Amelia collection contains **thirty reusable starters: six websites, six web apps, six mobile-web experiences, six ecommerce stores and six tools/automation experiences**. This report explains the selection and product direction. Release verification is recorded separately; this report does not certify native apps, live payments, external integrations or deployment into Amelia’s production catalog.

Amelia’s opportunity is to make a strong first impression that survives the next click. The homepage should be memorable, the inner pages should feel equally considered, and the main action should end in a useful, understandable result. Competitors already have extensive catalogs. A collection earns preference when people can recognize their business in it, try the full journey and see how they will make it their own.

## What competitors actually provide

The market has several different products under the word “template.” Comparing them accurately helps Amelia set the right expectations.

| Product family | What customers are buying or starting from | Relevant competitors and evidence |
|---|---|---|
| **Complete websites** | A visual identity, navigation, connected pages, reusable sections, content examples and a path to an inquiry, booking or purchase. | Wix separates website type from industry. Webflow describes multi-page and multi-layout systems with reusable components. Squarespace combines sites with commerce, scheduling and memberships. Elementor offers complete website kits and reusable page parts. [Wix](https://www.wix.com/website/templates), [Webflow](https://webflow.com/templates), [Squarespace](https://www.squarespace.com/templates/), [Elementor](https://elementor.com/resources/website-templates/) |
| **App foundations and workspaces** | Screens, records, filters, forms, permissions, workflow states and actions. A polished dashboard alone is only part of the product. | Bubble organizes templates around CRM, booking, dashboards, directories, marketplaces, SaaS and other applications. Softr uses workflow and industry filters; its creation documentation describes copying both interface and database. [Bubble](https://bubble.io/templates), [Softr gallery](https://www.softr.io/templates), [Softr template creation](https://docs.softr.io/start-here/create-an-app-from-a-template) |
| **Mobile apps and mobile workflows** | Focused journeys for small screens, navigation, device behavior and sometimes a connected backend or native source. | FlutterFlow distinguishes full apps from design-only UI kits. Adalo feature templates include linked screens, data and actions. Glide highlights mobile event and field/operations use cases. Developer foundations such as Expo supply routing and platform structure rather than an industry brand. [FlutterFlow submission types](https://docs.flutterflow.io/marketplace/creators-hub/submit-item-for-review/), [Adalo](https://help.adalo.com/feature-templates), [Glide](https://www.glideapps.com/templates), [Expo](https://docs.expo.dev/more/create-expo/) |
| **Commerce themes** | Merchandise presentation, product discovery, exact variants, cart behavior, policy access and a checkout ecosystem. | Shopify filters by industry, catalog size, features and style. Its theme guidance emphasizes the features useful to the intended merchant segment. WordPress marketplaces also have substantial WooCommerce offerings. [Shopify Theme Store](https://themes.shopify.com/), [Shopify theme guidance](https://shopify.dev/docs/storefronts/themes/store/review-process/listings), [ThemeForest chart](https://themeforest.net/popular_item/by_category?category=wordpress) |
| **Tools and automations** | A specific input-to-result workflow: clean data, prepare a proposal, calculate a scenario, collect a brief, review an approval or connect services. | Retool and Airtable cover business operations; Typeform covers forms and quizzes; Make and n8n organize executable workflows. Replit’s gallery spans remixable applications and utilities. [Retool](https://retool.com/templates?tags=Dashboard), [Airtable](https://www.airtable.com/templates), [Typeform](https://www.typeform.com/templates), [Make](https://www.make.com/en/templates), [n8n](https://n8n.io/workflows/), [Replit](https://replit.com/gallery) |

Design-oriented marketplaces such as Framer make visual style and motion part of the selection experience. AI builders such as Lovable broaden the field to websites, dashboards, business tools and niche interactive experiences. Their galleries reinforce the need for both visual appeal and useful functionality; vendor labels such as “production-ready” still require project-specific verification. [Framer](https://www.framer.com/marketplace/templates/), [Lovable](https://lovable.dev/templates/).

## Which are most popular?

There is **no defensible single popularity ranking across these competitors**. They publish different measurements, and many publish only editorial selections.

| Public signal | What it tells us | What it does not establish |
|---|---|---|
| Product sales | Recorded purchases of that marketplace item | Active websites, individual demo usage or current revenue |
| Installs / Used | A template was copied or started in that platform | A paying customer, successful launch or continued use |
| Views | Attention to a listing | Intent to use, quality or commercial results |
| Popular / Trending / Featured | The platform is promoting or sorting examples | An independent rank unless the methodology is disclosed |
| Category inventory | Breadth of supply and competition | Demand, market share or profitability |

The strongest quantitative observations in the September 8 research were:

- **Websites:** Avada’s item page displayed **1,070,848 cumulative sales**. This is a multipurpose WordPress builder/theme containing many designs, so it is not a million uses of one visual template. A separate weekly-updated chart displayed Avada 527, WoodMart 250, Flatsome 135, Uncode 118 and Salient 105 sales; exact interval boundaries were not available in the extracted chart. [Avada listing](https://themeforest.net/item/avada-responsive-multipurpose-theme/2833226), [ThemeForest chart](https://themeforest.net/popular_item/by_category?category=wordpress).
- **Web apps:** Bubble’s Welcome template showed **13.9K installs**, its travel marketplace example **13.7K**, and the paid Bullet Launch SaaS starter **321**. These examples differ in price, age and purpose; they support interest in starting foundations and marketplace workflows without proving a category-wide rank. [Welcome](https://bubble.io/template/welcome-to-bubble-1704488058143x222204452298031100), [Travel marketplace](https://bubble.io/template/travel-marketplace-like-airbnb-1631272543074x614536129996390400), [Bullet Launch](https://bubble.io/template/1707392233950x905301177766772700).
- **Working app examples:** Replit showed Journey Mapper at **20,771 views / 79 uses**, Product Manager CRM at **14,659 / 36**, and CRM at **8,833 / 176**. Within this small visible sample, the most-viewed example was not the most-used one. [Replit Gallery](https://replit.com/gallery).
- **Mobile starters:** Fluxstore WooCommerce’s commercial Flutter starter displayed **7,275 sales**. This is evidence of paid demand for a mobile commerce starter, not proof that mobile commerce is the largest category. [Fluxstore listing](https://codecanyon.net/item/fluxstore-woocommerce-flutter-ecommerce-full-app/24050041).

The September 9 gallery checks add useful qualitative evidence. Glide’s own “Most popular” group includes Customer Portal, Project Management, Inventory Manager, Operations Dashboard, Sales Dashboard and Mobile Event. Shopify highlights clothing, beauty, jewelry/accessories and home as top industries and offers a separate trending collection. Webflow highlights portfolio/agency, technology, editorial, professional services, property and retail. These are sensible places to investigate demand, but their labels do not reveal comparable adoption totals. [Glide](https://www.glideapps.com/templates), [Shopify](https://themes.shopify.com/), [Webflow](https://webflow.com/templates).

The practical conclusion is to prioritize familiar, valuable customer jobs: present a business, sell products, manage clients and work, schedule something, discover something, or finish a useful task. Amelia should collect its own template-start and successful-publish evidence before calling a design a bestseller.

## Organize the collection around the customer’s goal

Use five clear top-level categories, then filter by industry, goal, style, capability and readiness. This avoids forcing a salon’s marketing website, booking app, staff scheduler and reminder workflow into one ambiguous category.

| Main category | Useful industry / goal filters | What a complete experience should answer |
|---|---|---|
| **Websites** | Professional services, local trades, creative work, wellness, restaurants, events, property, education, nonprofit, publishing | What do you offer? Why choose you? What happens next? |
| **Web apps** | Client portals, CRM, projects, analytics, inventory, directories, learning, support, recruiting, marketplaces | What can I accomplish, what changed, and what is the next action? |
| **Mobile experiences** | Discovery, booking, habits, field work, events, food, expenses, loyalty, community | Can I complete the task comfortably with one hand and resume where I left off? |
| **Ecommerce** | Apparel, beauty, home, food, outdoor, digital goods, subscriptions, wholesale | Is this the right product and option? What will it cost? What happens after checkout? |
| **Tools & automations** | Intake, quotes, calculators, planning, cleanup, approvals, document workflows, service connections | What goes in, what comes out, and can I inspect or correct the result? |

This structure is our recommendation, informed by Wix’s type/industry separation, Softr’s workflow/industry organization and Shopify’s capability/catalog-size approach. The same business may use several templates together. [Wix](https://www.wix.com/website/templates), [Softr](https://www.softr.io/templates), [Shopify](https://themes.shopify.com/).

## Why these thirty

The slate covers five product surfaces and thirty recognizable purposes while preserving room for distinct art direction. Forma, Kin, Elsewhere and Morrow are the original four editions; the expansion adds twenty-six. These are reusable starter projects with working sample journeys. Their presence does not mean that thirty live businesses, production backends or native apps have been launched. The descriptions below identify each concept’s purpose rather than promising every future integration.

| Category | Six concepts | Why this group belongs together |
|---|---|---|
| **Websites** | **Forma** — architecture/interiors; **Plume** — creative studio; **Solace** — movement/wellness; **Ember** — restaurant; **Rally** — conference; **Verdant** — garden/local services | Demonstrates service explanation, portfolio proof, class discovery, menu exploration, event planning and project inquiries. These customers need different content structures and moods. |
| **Web apps** | **Kin** — projects/client collaboration; **Relay** — CRM; **Signal** — analytics; **Ledger** — inventory; **Atlas** — directory; **Academy** — learning | Covers six common ways people organize work and information. The visual interface must support records, actions and clear results. |
| **Mobile experiences** | **Elsewhere** — stays/discovery; **Tempo** — routines; **Fieldwork** — inspections; **Gather** — event companion; **Savor** — food pickup; **Pocket** — expenses | Tests distinct small-screen tasks, including browsing, timed focus, checklists, agendas, cart decisions and fast data entry. These are mobile-web source starters; native delivery is separate. |
| **Ecommerce** | **Morrow** — home objects; **Atelier** — apparel; **Dew** — personal care; **Ritual** — coffee; **Roam** — outdoor goods; **Edition** — digital products | Buying decisions differ: materials/dimensions, size/fit, routine preferences, weight/grind, technical comparisons and file/license details. The storefront should reflect those decisions. |
| **Tools & automations** | **Scope** — proposals; **Briefly** — intake; **Tally** — time/cost scenarios; **Dispatch** — content planning; **Cleanroom** — CSV cleanup; **Flowline** — automation simulation | Each has a useful input-to-output purpose. Local exports and inspectable transformations make these valuable even before service connections. |

The art direction should help a visitor distinguish the concepts before reading their names: architectural editorial, bold studio typography, quiet wellness imagery, restaurant atmosphere, event poster graphics, operational tables, mobile task cards, product merchandising and document workspaces. Shared components should preserve reliable behavior while allowing different compositions, typography, spacing, image treatment and navigation.

The catalog should show a real preview, included page/screen map, main workflow, available source and readiness statement. A visitor needs to understand both the design and the work it helps them do. Search should understand terms such as “salon,” “client portal,” “sell downloads,” “booking,” “quote” and “mobile,” even when the template has a brand name such as Solace or Edition.

## What to add after this collection

Thirty concepts are a broad first library, not every possible business. Additional work should be chosen using unmet searches, template starts, completed customization and successful launches. The next families should add distinct workflows rather than repaint existing layouts.

| Opportunity | Useful variants | Additional depth required |
|---|---|---|
| **Marketplaces** | Services, rentals, local goods, professional talent | Buyer/seller onboarding, listing management, availability, transactions, disputes and moderation. Start with a narrow transaction model. |
| **Directories** | Specialists, venues, jobs, resources, properties | Rich filters, comparison, verified profiles, claim/submit listing and review queue. Atlas is a useful design foundation. |
| **Portals** | Client, supplier, member, partner, investor | Identity, tenant/role access, documents, requests, status and useful communication. Kin’s design can inform several variants, with real permission boundaries. |
| **Booking and scheduling** | Salon, fitness, coaching, consultations, equipment hire | Availability, staff/resources, time zones, capacity, confirmation, cancellation and rescheduling. Add both customer and operator journeys. |
| **Fundraising and nonprofit** | Donations, volunteer programs, community campaigns | Mission, evidence of impact, campaign pages, recurring/one-time giving, volunteer intake and transparent receipts. Payment and claim verification are separate release work. |
| **Property and hospitality** | Agents, developments, boutique stays, rentals | Search, galleries, floor plans, amenities, viewing/availability and property-specific inquiries. |
| **Education and membership** | Courses, schools, tutors, paid communities | Curriculum, meaningful lessons, progress, access tiers, learner support and administration. |
| **Publishing and creators** | Magazine, newsletter, podcast, author, portfolio | Searchable content, editorial navigation, articles/episodes, subscriptions and accessible media. |
| **Specialist/local businesses** | Home repair, cleaning, accounting, legal, logistics | Service area, relevant credentials supplied by the owner, detailed scope, estimate/intake and expected next steps. |
| **Commerce extensions** | Large catalogs, subscriptions, wholesale, jewelry, groceries | Appropriate discovery, repeat purchase, subscription management, volume pricing or product-specific options. Use verified catalog and fulfillment rules. |
| **Operations** | Support, recruiting, facilities, approvals, procurement | Real lifecycle states, assignment, audit history, attachments, notifications and recovery. |
| **Document and AI workflows** | Proposal generation, extraction, knowledge search, content review | Source retention, inspectable drafts, permissions, evaluation and human review where the output has consequences. |

These opportunities are supported by the breadth of official categories and workflows in Bubble, Softr, Adalo, Squarespace, Retool and Make. Their order above is a product judgment, not a measured market-share table. [Bubble](https://bubble.io/templates), [Softr](https://www.softr.io/templates), [Adalo booking](https://help.adalo.com/feature-templates/appointment-booking/overview-screens-database-layout-settings-use-cases), [Squarespace](https://www.squarespace.com/templates/), [Retool](https://retool.com/templates?tags=Dashboard), [Make](https://www.make.com/en/templates).

## Direct editing should complement AI—and work from a phone

The recommendation is **yes: add quick direct editing, section movement and a curated element library**, with AI available from the same selected element. People should be able to fix a sentence immediately, replace a photo, insert a form or move a section without explaining every small change in chat.

Competitors support this mixed approach. Wix documents both click and drag insertion and theme-matched elements. Elementor provides visual element placement and layout controls. Lovable’s current preview toolbar includes inline text editing, element selection, annotations and comments. These sources establish useful interaction patterns; they do not prove identical mobile capabilities across all products. [Wix elements](https://support.wix.com/en/article/wix-editor-adding-and-deleting-elements), [Elementor elements](https://elementor.com/help/add-elements-to-a-page/), [Lovable preview toolbar](https://docs.lovable.dev/features/preview-toolbar).

The product can stay approachable by showing a short contextual toolbar for the selected item and keeping uncommon controls behind an advanced option. Use a clear Browse/Edit switch so tapping a link in the preview does not unexpectedly edit it.

| Phase | Customer controls | Release condition |
|---|---|---|
| **1. Quick changes** | Edit text; replace image; change button label/link; choose approved colors/fonts; undo/redo | Changes survive save/reload and subsequent AI work. Long text reflows correctly. |
| **2. Sections** | Drag or tap to reorder; duplicate, hide, delete; add a complete section before/after another | The same operation works with mouse, touch and keyboard; semantic reading order and responsive layout remain coherent. |
| **3. Elements** | Insert text, image, video, button, form, gallery, FAQ or feature blocks in supported slots | New elements inherit the design; invalid placements are prevented; forms/media show real setup state. |
| **4. Layout refinement** | Column/grid presets, spacing, alignment and supported responsive overrides | Users can understand the effect and undo it. Phone/desktop previews stay consistent. |
| **Later, when justified** | Advanced canvas positioning or editing native output | Separate renderer and quality tests demonstrate the need and behavior. |

Mobile editing should be a core surface, with intentional phone controls. Tap a section to select it; expose a move handle and **Move up / Move down / Place before / Place after**. A compact outline makes long pages easier to rearrange. A reachable Add button opens a bottom sheet of sections and elements; users can tap an insertion point, with dragging available as a shortcut. Text can be edited inline or in a focused sheet above the keyboard. Save status, Done, Undo and Cancel must remain reachable.

Every drag operation needs a tap-only alternative as well as keyboard support. W3C’s dragging criterion explicitly distinguishes the non-drag pointer alternative from keyboard access and gives move buttons and destination menus as examples. These are particularly useful on small touchscreens. Amelia’s recommended design target is generous 44px controls with clear spacing, labels, focus and move announcements. [W3C dragging guidance](https://www.w3.org/WAI/WCAG22/Understanding/dragging-movements.html).

Editing **from** the Amelia mobile app and creating **a native mobile app** are different capabilities. A controlled in-app host may reuse the managed web editor, while native navigation, media selection, keyboard behavior and lifecycle recovery need their own integration and device testing. Generating editable native output needs a native component model and platform build validation. A phone-shaped web preview does not establish either capability.

The most important engineering decision is one shared content model for visual and AI edits. Give pages, sections and editable fields stable identities. Both AI and direct controls should make typed changes to that same document, with the renderer producing the preview and published output. Manual edits must not live only in browser DOM changes that disappear at the next generation.

Saving needs a revision-aware coordinator across visual edits, AI, imports and restores. If two edits affect different fields they can be reconciled after validation; if both change the same text or one deletes the selected section, retain both candidates and show the conflict. “Saved” should mean an acknowledged source revision. Local drafts, saving, saved, offline and conflict states should look different. Publishing should use a specific validated revision; typing or autosaving is not publication.

For ecommerce and apps, edit display content through this model while keeping protected business data in its proper interface. Product price, inventory, permissions, payment configuration and order state should not become arbitrary text edits on a preview. Custom code can remain AI-editable until a direct-edit adapter supports it.

## The quality standard that makes the collection professional

Each public-facing template needs meaningful navigation, substantive inner pages, a clear next action and a useful footer. A services page should explain scope, process, fit and common questions. A product detail should answer the buying questions for that product. An app should show loading, empty, invalid, success and recovery states relevant to its workflow. Every claimed feature should have an observable result.

Motion should clarify selection, movement and state changes. Content should be usable immediately; an impressive loading experience does not require delaying a usable page. Honor reduced-motion preferences and provide appropriate control over continuing decorative movement. [W3C interaction motion](https://www.w3.org/WAI/WCAG21/Understanding/animation-from-interactions.html), [W3C pause/stop/hide](https://www.w3.org/WAI/WCAG21/Understanding/pause-stop-hide.html).

For public websites, provide unique titles/descriptions, useful headings, crawlable navigation, appropriate image descriptions and a deliberate canonical/sitemap strategy. Keep private demos and private app data out of search. Search-friendly structure cannot guarantee rankings. Performance targets should be measured, not asserted: Google’s field thresholds for a good experience are LCP at most 2.5 seconds, INP at most 200 milliseconds and CLS at most 0.1 at the 75th percentile. [Google SEO guidance](https://developers.google.com/search/docs/fundamentals/seo-starter-guide), [Web Vitals](https://web.dev/articles/vitals).

For stores, preserve exact variant identity from product to cart to receipt, derive totals from the catalog, keep policy links accessible and show clear unavailable states. Shipping, tax and payment behavior require real providers before a merchant launch. A local sample checkout should remain visibly a sample and should not collect real payment credentials. [Shopify variants](https://help.shopify.com/en/manual/products/variants), [Shopify checkout](https://help.shopify.com/en/manual/checkout-settings), [Shopify policies](https://help.shopify.com/en/manual/checkout-settings/refund-privacy-tos), [Stripe testing](https://docs.stripe.com/testing).

Use clear readiness labels throughout the collection:

| Label | Meaning |
|---|---|
| **Private prototype** | Design and local interactions for private review, using sample content/data. This was the collection’s initial review stage. |
| **Source starter** | The current thirty-template collection: exportable source and setup documentation, with working sample journeys. Required services and owner content are identified. |
| **Connected template** | The advertised backend and integrations are implemented and tested under stated conditions. |
| **Production verified** | A specific release has passed the product’s applicable deployment, functional, accessibility, security and device checks. A future owner’s changes still need verification. |

The next popularity evidence should come from Amelia itself: impressions → detailed previews → template starts → first successful customization → publish → continued use. Compare within product type and account for placement in the gallery. Track empty searches and abandonment points to choose the next six, then improve the templates that help people finish. A beautiful screenshot gets attention; a coherent, editable experience gives people a reason to keep building.