Good ideas begin
with a little looking.

Different beginnings for different jobs.

Wix, Webflow, Squarespace and Elementor organize website starts around businesses and visual styles. Bubble, Softr and Glide focus on records, workflows and operational applications. Shopify organizes around merchandise and selling needs. FlutterFlow and Adalo distinguish app foundations and connected functionality. Make, n8n and Retool start with a task or process.

These are different promises. A business website needs a compelling story and a clear enquiry path. A web app needs useful actions and understandable state. A store needs exact product choices and a trustworthy finish. A mobile experience needs to make the same work comfortable in a smaller space.

Popular is not one number.

There is no comparable global ranking across these marketplaces. Sales, installs, views, uses and “featured” placements describe different things. We keep those signals separate.

Glide’s own popular group includes customer portals, project management, inventory, operations, sales and mobile events. Shopify highlights clothing, beauty, accessories and home. These are useful category signals; the platforms do not disclose comparable adoption totals for all of them. Glide ↗ · Shopify ↗

For Amelia, the next useful evidence is our own: searches without a match, templates started, customization completed and sites successfully published. Until that exists, the collection is curated—not labeled with invented bestseller badges.

Thirty concepts. Five useful categories.

Each group has six templates with distinct subject matter and a meaningful sample journey. The four original editions remain part of the collection.

A shared page. Two useful ways to change it.

Keep AI editing for broad changes and complex requests. Add direct text editing, media replacement, section movement and quick insertion for precise changes. Both should operate on the same structured content with stable element IDs, validated operations and a shared undo history.

The page studio in this collection demonstrates the interaction: a landing page composition, text/image/video/enquiry sections, drag handles, move buttons, local drafts and real exports. Continue in Amelia attaches the edited HTML and JSON draft to a new AI build. The studio does not directly modify every app screen.

Dragging is an option.
Control is the requirement.

A phone should not require someone to hit a tiny handle while the page fights their scroll. Provide tap-to-edit, move up/down, a clear selected state, a bottom sheet and generous touch targets. Pointer dragging is a second route to the same operation.

This is also an accessibility requirement: W3C guidance calls for a single-pointer alternative to interactions that depend on dragging. Our move buttons serve that purpose. W3C guidance ↗

The current implementation is responsive web. A native editor needs explicit WebView or native gesture, keyboard, file-picker, safe-area, offline and synchronization testing. The source does not include native binaries or app-store delivery.

Build the next thing people need.

High-value extensions include marketplaces, customer and member portals, appointment scheduling, nonprofits and donations, real estate, publishing, specialist local services, subscriptions and wholesale, recruiting, support and approval workflows.

Each addition should introduce a useful journey and an appropriate visual identity. Prefer a strong narrow product over a long list of surface variations. The complete report describes these opportunity families and the integration depth each needs.

Amelia imports each complete starter at a pinned version into a new project. Authentication, payments and external services are configured for each customer’s needs during their build. The independent source archives remain available for download.