Skip to main content

General UI and Components improvements


Forum|alt.badge.img

Hi everyone! đź‘‹

First of all, I really appreciate the work the RevenueCat team has put into the Paywall Editor—it’s a great tool with a lot of potential! However, after using it extensively, I’ve noticed a few areas where the UX/UI could be improved to make the experience even smoother. I wanted to share some thoughts and open the discussion for others who might have additional suggestions.

1. Editing & Usability Enhancements

  • There’s no way to undo an action (neither Ctrl + Z nor a dedicated button).
  • You can’t double-click a component to rename it.
  • The Delete or Backspace keys don’t work to remove a component.
  • There’s no option to hide/show components while editing.

2. UI Layout Improvements

  • The language selection, dark/light mode toggle, and preview settings currently overlap the phone preview window, making it harder to work on designs.
  • The same happens with the orientation and phone size options—they appear on top of the editing area.
  • A possible fix: Placing these options above the Paywall Editor, next to the save & publish buttons, would free up more space for designing.

3. Feature Suggestion: Expandable Content

  • Currently, there’s no built-in way to show/hide content dynamically within the paywall (e.g., an expandable section for additional details).
  • Adding a collapsible component could improve flexibility for paywall designs.

4. Paywall Size Flexibility

  • Right now, the paywall takes up the entire screen with no option to make it dynamic or adjust its height.
  • It would be helpful to allow for paywalls that don’t require full-screen usage, especially for apps that want a more integrated feel.

Would love to hear what others think! If you’ve also noticed areas for improvement, feel free to jump in and share your thoughts.

Thanks for reading!

This post has been closed for comments

2 replies

Dan Pannasch
RevenueCat Staff
Forum|alt.badge.img+3
  • RevenueCat Staff
  • 50 replies
  • March 20, 2025

Thanks so much for the thoughtful feedback! I just shared it with our team building Paywalls v2. I have just a few follow up questions for you:

  • Regarding the collapsible/expandable component idea, did you already have any particular use cases in mind for it that you’d want to build? Definitely a request we’ve heard elsewhere too, but want to make sure we build it in a way that’s sufficiently flexible.
  • On building paywalls that are not full-screen, how would you imagine controlling their height (and width)? Relative to the device size, a fixed height/width? No wrong answer here: just would love to hear how you were hoping the product worked when you were thinking through that.
  • Last one, could you double check if `ctrl+z` was working to undo changes? That should be enabled already, but I’m wondering if there are cases where its not.

Thanks so much!


Forum|alt.badge.img
  • Author
  • New Member
  • 1 reply
  • March 20, 2025
Dan Pannasch wrote:

Thanks so much for the thoughtful feedback! I just shared it with our team building Paywalls v2. I have just a few follow up questions for you:

  • Regarding the collapsible/expandable component idea, did you already have any particular use cases in mind for it that you’d want to build? Definitely a request we’ve heard elsewhere too, but want to make sure we build it in a way that’s sufficiently flexible.
  • On building paywalls that are not full-screen, how would you imagine controlling their height (and width)? Relative to the device size, a fixed height/width? No wrong answer here: just would love to hear how you were hoping the product worked when you were thinking through that.
  • Last one, could you double check if `ctrl+z` was working to undo changes? That should be enabled already, but I’m wondering if there are cases where its not.

Thanks so much!

Hi,

Thanks for getting back to me! I really appreciate the thoughtful follow-up questions. Here’s my feedback on each point:

  1. Collapsible/Expandable Component Use Case
    Yes! We do have a specific use case for this. I just created a quick mockup to illustrate what we’d like to achieve. On the left, you can see how our current "Package" component looks (this is just part of the paywall). On the right, you can see how it could work with an expandable approach. Our ideal setup includes six Packages in total, divided into two sections with three each, but the current paywall structure makes it way too large.
     

    Our idea is to use a button to toggle visibility between different Packages. Right now, it’s possible to create a stack inside a Package with its respective components, and we could work around the issue by setting the non-selected stack’s width and height to 0 and applying a top padding equal to the device width so it’s not visible when unselected. When selected, the stack would return to its normal size, effectively making it "appear” but because it’s inside a package you cannot select anything inside this stack.

  2. Non-Fullscreen Paywalls
    I would suggest allowing customization of just the height, rather than both height and width. There could be two approaches:

    • A relative height based on the total device size (e.g., 65% of the screen height).
    • A fixed height with a warning if the specified height exceeds the device’s screen, making it automatically fullscreen.

    Additionally, this type of paywall could include a resizable UI element (by default, a small horizontal line with fixed dimensions) to indicate that users can drag to close the paywall.

  3. Undo (Ctrl + Z) Issue
    For me, pressing Ctrl + Z does nothing, regardless of how many times I try. It might be an issue with my browser since I use Firefox, but I wanted to flag it in case others experience the same issue.

Thanks again for your time and consideration—I really appreciate that you’re taking feedback into account!


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings