Add the feature. Understand the commitment.
Find app marketplaces for hosted website builders and commerce platforms. Compare the exact platform requirements, subscriptions, data flows, support responsibilities, and removal steps.
Follow the official destination, then investigate the individual listing.
Explore app integrations for Webflow projects.
Explore apps available through the Wix marketplace.
Browse apps for Shopify commerce workflows.
Browse plugin listings in the Framer Marketplace.
Directory names and resource descriptions are grounded in the official destinations linked above. A listing is not a compatibility guarantee, a security endorsement, or a partnership claim. Requirements and availability can change; check the provider before acting. Read our editorial approach.
Use the directory as a starting point. Evaluate the complete workflow and the responsibility that comes with it.
Use the marketplace linked for your actual platform. Compare the current requirements for the relevant editor, plan, and app edition before treating two listings as alternatives. The platform catalog is the source for discovery; the individual app’s documentation is the next step for a decision.
Describe the missing visitor and staff workflows. Check whether existing features already meet the requirement. Installing an app is only the first test; complete the task and inspect what happens to the information afterward.
Keep a dated record of platform plans, app subscriptions, usage arrangements, external services, and setup work where applicable. Do not treat a trial or the lowest advertised tier as the price of the configuration you need.
Include the future maintainer in the pilot. Ask them to correct a record, change a setting, and find the support route. Follow data to every connected service and test export with representative synthetic records. An export button is not the same as a successful migration.
Read the removal instructions for the specific platform and app. Identify whether theme cleanup, data export, disconnected services, or separate cancellation steps are involved. Do not assume uninstalling, deleting data, and stopping billing are one operation.
Run a controlled removal test and inspect public pages, editing tasks, and links. Keep a recoverable starting state. Record the reason for approval, known limits, responsibilities, and review triggers so that a small feature does not become an unexplained dependency.
Keep the scope of your project visible while comparing options.
Not necessarily. Check the exact configuration for platform plans, app subscriptions, usage arrangements, external services, and the work required to manage it. Keep those assumptions dated.
Read the specific product’s instructions. App removal, data deletion, external account management, and cancellation may require different steps. The guide below includes a sourced platform example.
Complete the visitor and staff workflows, inspect mobile and keyboard behavior, test sample exports, and rehearse removal in a safe environment with a recoverable starting state.
Look beyond the install button to understand subscriptions, platform requirements, content ownership, and removal work.
Use repeatable before-and-after tests to understand scripts, layout shifts, real user journeys, and whether a plugin earns its place.
Evaluate generated navigation, page structure, focus states, and responsive behavior before a design plugin enters your workflow.
