Skip to main content

App Settings: POWr vs. Wix

There are several settings that are intended to behave differently in Wix compared to POWr, or don't exist at all on Wix. Please add to this list whenever you find things that are intentionally different!

General:

Import panel: We do not have an Import panel on Wix (for various complex reasons). Wix users cannot import a saved plugin. Instead, they can use the Copy/Duplicate/Paste controls in the Wix Editor to re-use the same plugin multiple times (or on different pages). This also means that Wix users are currently excluded from template A/Bs and do not see templates to choose from.

Design > "Plugin Width": This setting should always be hidden in Wix. By default, we want to set the plugin width to 100% in Wix so that the user can make use of the resizing options in the Wix drag & drop editor. Exceptions are width controls for individual entries, e.g. Social Feed max width per entry, Countdown Timer counter size, etc.

Pricing A/Bs: Assume that any pricing A/Bs that are active on POWr (this includes, testing different prices per plan, credits and discount tests, and feature limits in plugins) are not also running on Wix. Because we don't handle the billing for Wix upgrades, we cannot test those things with Wix users. Similarly, if we are implementing new feature limits in Wix, assume that the ones on POWr are not also updating. We can tweak them on our side more frequently and optimize for an audience outside of Wix, so features per plan look quite different for Wix vs. POWr.

Image Manager: When working on media features, please be conscious of the fact that in Wix, we use their built-in Media Manager for adding images. Our File Manager should not be shown to Wix users. Exception: if a user toggles on "Digital Download" in eCommerce, they should see the POWr File Manager for uploading the file they want to sell.

Upgrade Tooltips: In Wix, the upgrade tooltips and Upgrade buttons in the settings should always open the Wix upgrade modal and never redirect to powr.io

Color Pickers: Many of our UI components look different in Wix but work the same. The big exception is the color picker. Wix gives us the color swatches for each theme and we display the appropriate colors as the main swatch (the user can still choose to customize the colors, but that option is de-emphasized). Make sure to work with our chameleon system for automatically applying the site colors to the app default on first load.

Save / Publish Behavior: Making changes to an app in Wix creates backup_content only. The user can save the backup_content by clicking Save in the Wix Editor (not the POWr Editor). To publish those changes to their live site, the user needs to click Publish in their Wix editor. That is when the app settings are also being stored as content (and not just backup_content). If the content in the editor doesn't match what you are seeing on the live site, hit Publish again until they do match 👾

Delete Behavior: More weirdness: a Wix user can use the trash can icon in their Wix Editor (or simply press Delete on their keyboard after selecting our app in the Editor) to delete their app. Until they hit Save or Publish in the Editor, they can simply refresh the page and still edit that deleted app in the Wix Editor. 💥

App Specific Features:

Design > "Positioning" (Form Builder, Countdown Timer, Social Media Icons): We have not yet figured out how to make fixed position work on Wix website, so we do not want to show the settings for those controls.

Account / User Things:

When building new features, be mindful of the fact that Wix does not share user data with us. We get a site ID, but no email or anything else that helps us easily identify a user.

Here's what we do instead:

  1. When a user first creates an app and we don't recognize the user, we automatically create an account with an ID on powr.io.
  2. If the user enters their email somewhere in the app settings (in Form Builder: admin email notifications or PayPal account, in PayPal Button & eCommerce: PayPal account), we want to capture that and use that email address for the account we created for them.
  3. For apps where the user does not enter an email address anywhere in the settings (such as Social Feed, Gallery, Slider, etc.), we are unlikely to ever have an email address on that user's account. The user would need to be logged in via Wix and go to powr.io, then manually add their address under "Account Info" (rare).

Please note: Users can access their Form Response Dashboard from their main Apps dashboard (without going into the Form Builder app settings first). We still need to be able to identify the user in that case and show them the correct dashboard(s). Puru and Ben can explain how the authentication works there.