Forum Academy Marketplace Showcase Pricing Features

Bubble Editor Ideas and Suggestions

Hi everyone! :slight_smile: :wave: I’ve been keeping a list of things that I think would really speed up my Bubble workflow. I know that some of these have already been suggested by multiple Bubblers before, but I wanted to make this list that included those ideas as well, just in case they’ve gotten lost in the forum. If anyone would like to make suggestions to these, please feel free to reply below!

@allenyang First of all, Welcome! :slight_smile: I saw your other thread and thought of including these ideas in there, but they aren’t related to third-party services. Absolutely no pressure to read through these of course if you’re focusing only on third-party services right now. Thank you so much!

Bubble Editor Ideas

  1. The ability to filter elements when selecting the value of a number field (this is currently only possible with all fields except for number fields). This isn’t usually an issue with simple pages, but it can be very difficult to find the number input that you need when the page has hundreds of elements.
    This was implemented by the Bubble team on 12/02/19!! :relaxed: :partying_face: :sparkles: :confetti_ball: :raised_hands:

  2. The ability to change a “Make Changes to a Thing” action into a “Create a New Thing” action. This would save a lot of time since both are usually using the same inputs to modify the same fields. This was implemented by the Bubble team! :slight_smile: :raised_hands: :tada:

  3. The ability to ungroup a single element from a group. Right now, the only workaround is to add a second, ‘dummy’ element, select that element and the single element that you’d like to ungroup, ungroup them, and then delete the ‘dummy’ element. In the example below, the option to “ungroup” doesn’t appear until two elements are selected. This was implemented by the Bubble team! :relaxed::sparkles::+1:

  4. The ability to re-order fields by drag and drop; this would help keep things organized when there are many fields being modified:

  5. A one-click “Add All” button that prepopulates all of a Thing’s fields in the “Make Changes to a Thing” and “Create a New Thing” actions (so we don’t have to individually select all of the fields). If an action already has “fields to modify” selected, then clicking the “Add All” button would add the rest of the data type’s fields that haven’t been selected by the developer yet.
    This was implemented by the Bubble team on their Pebble Day! :partying_face: :slightly_smiling_face: :tada: :sparkles:

  6. A one-click “Suggest values” button that sets the value of each of those fields to be the inputs on the page that utilize those field values as the elements’ default values. For inputs that don’t have a dynamic default value, the inputs’ placeholder texts would be used to suggest the values for the modified fields.
    For example, clicking the “Suggest all values”:


    Would set the field’s values based on either the input’s name or the default value that the input utilizes, or the placeholder text of the input

  7. The ability to change a field name or a constraint field without deleting it first and then creating it. This was implemented by the Bubble team!! :blush: :confetti_ball: :sparkles:

  8. The ability to select elements that are in different groups and modify them at once (e.g., applying a style to multiple buttons that are in different groups). Right now, when selecting buttons (or other types of elements) that are in different groups, all of the buttons’ container groups become selected as well, which doesn’t allow you to modify all of the buttons’ styles at once. This was implemented by the Bubble team! :partying_face::raised_hands::confetti_ball:

  9. The ability to select multiple elements in the left-side panel by clicking “shift” and then being able to copy only those specific, selected elements:

  10. The ability to “copy without data” and “paste without data” (i.e., only copy or paste the UI without data or workflows). This would save time if this action also automatically reset all of the just-pasted element names.

  11. “Smart” element names - I’m not sure if this is possible, but all of my element names are usually in the format of “[Element Type] [Field it modifies] [(Thing being modified]”, so an example would be “Input First name (User)”. Often times those inputs have a default value, such as “Parent group User’s First name”, or a placeholder that is the same as the field’s name. It would speed things up if I could click a button for input elements that have a default value or placeholder value to rename them in that format:
    For example, clicking this button:


    Would automatically change the input name to:

  12. The ability to view a single Thing’s data in the responsive editor (i.e., if the page has a type of content, we could enter a unique ID for that type in the responsive editor. This would then display that Thing’s data, instead of all of the long dynamic data expressions. This would save a lot of time from having to jump back and forth between the responsive editor and preview mode).


  13. Suggested by @tim12333: “A :formatted as function for geographic locations and allow us to define what gets extracted similar to the date :formatted as. For example you would be able to get street address, street, city, state by typing in sa, s, c, st under custom formatting for a geographic location. Right now you have to copy and paste the dynamic data in a text box for each individual field you want to extract.”

  14. Suggested by @tim12333: “Allow us to see responsive settings inside the UI builder tab. Sometimes I know what responsive settings I need without having to see a preview, and it takes time to navigate to where I was inside the responsive tab just to change a few settings.”

  15. Suggested by @louisadekoya: “Some sort of smart select tool that would allow us to select all children of a parent for example, or all siblings, or all elements of the same type etc.”

  16. Suggested by @louisadekoya: “The ability to swap the positions of two selected elements.” This was added by the Bubble team on their Pebble Day! :relaxed: :partying_face: :sparkles: (Note: To use this feature, click on two elements and then click “Arrange --> Swap element positions”)

  17. Suggested by @louisadekoya: “A way to set a group’s type and in one click, have the type and value cascade (as parent group’s thing) down to all/selected sub groups within it.”

  18. Suggested by @louisadekoya: “A sweeper tool to sweep all elements up or down from a certain point, like this https://youtu.be/xWurQ7-KTFU?t=40 or just the ability to move all selected elements up or down by a specified value in any direction.”

  19. Suggested by @eli and @yusaney1 :
    A. “Preferred currency settings per app so we don’t have to set the currency format manually every time we need to use the :format as currency.”
    B. The option to enter a custom currency symbol in the Currency dropdown
    C. The option to choose whether the currency symbol will be at the beginning or end of the string


    A. After selecting “Currency” from the dropdown, the “use app-level currency settings” box would be checked by default (if the app-level currency settings were not empty), and the currency formatting dropdowns’ default values would be populated with the app’s currency formatting settings. Unchecking the “use app-level currency settings checkbox” would allow the developer to change the values of the currency formatting dropdowns

  20. Suggested by @edd: The ability to highlight and copy part of a long, dynamic expression, and paste it somewhere else in your app.
    HighlightFeature
    “Use case: Suppose you’ve been using the above expression but no longer care about the Current User’s favorite color. You either need to rewrite the expression from scratch with only the last three clauses, or convert the first one into something sure to pass the condition like Current User’s email is not “[email protected]” (or equivalent nonsense).”

  21. Suggested by @robert: The ability to edit a part of a long expression without having to rebuild from scratch.
    This was implemented by the Bubble team on their Pebble Day! :blush: :partying_face: :confetti_ball: :sparkles: :raised_hands:

  22. Suggested by @luke2: Real-time pixel distances displayed when moving element & using ‘Show distance on hover
    In the GIF below, the distances between the selected element and the other elements only displayed on hover, but it would be helpful to have the option to see those distances as the element is being moved
    ShowDistancesAsElementIsBeingMoved

  23. Suggested by @luke2 and @robbertmastebroek : Allow conditional properties on a repeating group to change its “layout style”, “Rows”, “Columns”, “Separator”, “Width”, and “Color”:

  24. Suggested by @robbertmastebroek: “The ability to pin elements to corners more easily, with controls similar to Sketch. Some of this is definitely possible in Bubble, but its a bit finicky to get it working right.”


    (video credit: Sketch)

  25. Suggested by @robbertmastebroek: “The above resizing options available in Sketch also allow to create (Reusable) Elements with dynamic widths, enabling elements (like buttons, tags) to have dynamic widths, or even align vertically. This really is a must-have in UI design, especially in more complicated app/software UI we often design in Bubble.”


    (video credit: Nando Rossi)

  26. Suggested by @edd: “The ability to copy workflow actions from a page/reusable event and paste to an API workflow event, and vice versa (more the former) A lot of times I’ll start by building a workflow on page, but then I’ll see an opportunity to optimize by using an API workflow, but as far as I know I cannot copy/paste an action from a page/reusable to an API workflow, thus requiring me to rebuild the flow in the other place. I realize that not all actions are compatible between the two, but many are! (e.g., Make changes to thing, send email).”
    This was implemented by the Bubble Team on their Pebble day!! :partying_face: :relaxed: :sparkles: :confetti_ball: :tada:

  27. Suggested by @edd and @gf_wolfer: (UX Change) A larger input box to enter deployment notes:
    LargerInput

  28. Suggested by @ryan16: “It would be really useful during development if when you select ‘disable workflow’ if a big X was drawn over the workflow trigger. Then you could see at a glance it was not enabled instead of having to click into it. Just making it a different color isn’t nearly as helpful to keeping your flow.” This was implemented by the Bubble team on 11/15/19! :relaxed::+1::sparkles:

  29. Suggested by @robert: A “lightweight” mode for the editor, or the option to run the app in “lightweight” mode to conserve RAM. “I’m running with 16GB of RAM, but it’s not enough. Frequent reloads of the page, and generally slow performance on pages with lots of elements.”

  30. Suggested by @yusaney1: In the App Text’s “Text ID” dropdown, when you type a new app text title, and then click to “Define another App Text”, the just-typed text should be the default value of the New Application Text’s Text ID input so the user doesn’t have to re-type it. (This is currently what happens when you create a new “Field” or “Thing” in the editor, but it doesn’t happen when creating new app texts).
    The default value of the “Text ID” input is empty when it should be the value that was just typed

  31. Suggested by @yusaney1 and @robert: It would be helpful to have all “Create a new…” options in editor dropdowns (e.g., Create a new field, and Create a new App Text) as the first options in their dropdowns, instead of the last option of the dropdown (to save time from having to scroll to the bottom each time).
    The “Create a new field…” option moved to the top of the dropdown


    The “Define another text…” option moved to the top of the dropdown

  32. Suggested by @boston85719: An “overflow: auto” checkbox that allows you to add a scrollbar when needed to text elements and group elements (especially group focus elements). This option would allow users to easily create custom search boxes without needing to add custom code.

  33. Suggested by @ryan16: Adjust the editor’s page organized so that pages are ordered alphabetically in the first column and then across, instead of what it currently is, across then down.

  34. Suggested by @JohnMark: The ability to define a secondary and tertiary language in the editor’s Languages section, and the ability to edit the app text values for all three languages in a single view (as shown below)

  35. Suggested by @petter: The ability to add multi-level path options to a Go to Page action. Currently, we have to use a link and reload the page to maintain the page’s parameters. Adding a multi-level path to the Go To Page action would solve this. “Using plugins is an option, but Bubble doesn’t recognize that the path has changed in those cases, so you can’t use it for SEO purposes such as Meta Title/Description”.

  36. Suggested by @petter: A “maintain parameters” checkbox within the Go to Page action. The Go To Page action resets all parameters unless you specify that they should change. A Maintain parameters checkbox that simply kept all parameters in the URL at their current value would be handy. This was implemented by the Bubble team!! :relaxed: :tada: :raised_hands: :partying_face:

  37. Suggested by @petter: A “pause” icon on all breakpoint workflows in development mode. This would make it easier to find workflows with breakpoints:
    image a.

  38. Suggested by @ryan16: The ability to select two elements and enter a number to alter vertical and horizontal distances between them. For example, if two elements are 40 pixels apart, the user could select both elements, and quickly enter “20” in order to make sure the elements are only separated by 20 pixels. You can currently subtract this amount by adjusting the X or Y coordinates of an element, but the ability to enter the distance in pixels would speed things up.

  39. Suggested by @gf_wolfer and @w.fly: Adjust the UI for long conditionals and “only when” statements so that they are vertically stacked on top of each other, instead of a long paragraph. This would allow you to simply read the conditions, re-order the statements by drag and drop, and copy and paste single statements (the entire paragraph can only be copied at the moment), and very clearly switch and/or statements with a dropdown.

  40. Suggested by @ryan16 and @ben7: The ability to move and reposition elements by drag and drop through the element sidebar, similar to how it’s done in design software like Adobe and Sketch:

  41. A :possessive option for text expressions. Often times, I’ll need to include something along the lines of “[Current User’s Full Name]'s Orders”.
    Right now, in order to have the correct grammar, I need to use the expression “Current User’s Full Name truncated from end to 1 is “s”:formatted as text” -->
    If true, the value should be Current User’s Full Name’ Orders
    If false, the value should be Current User’s Full Name’s Orders

  42. Suggested by @petter: The ability to lock an element inside of a group. Sometimes when you drag an element, it is virtually impossible to not “lose it” outside of the group it belongs to, especially if it’s big. An option that keeps the element inside the group it belongs to would be handy.
    image

  43. Suggested by @klaas.vanhoeck1: An easier option to filter by a certain day. Currently, you need to use the expression “[Date value] change minutes to 0, change hours to 0, change seconds to 0” (shown in the screenshot below)
    image
    It would be much easier to have a statement such as: Date field is in [Date value] (or Date field is [Date value]'s Day)

  44. Suggested by @melon: A color or copy change to the “ON” and “OFF” buttons for conditionals in the editor to add more meaning (e.g., Disable/Enable or Preview/Hide Preview)
    image

  45. Suggested by @melon: Adjust plugin filters so that one-time payment plugins aren’t shown when the “Free” filter is selected:

  46. Suggested by @melon: The option to disable a plugin instead of uninstalling and removing all plugin elements from an app:

  47. Suggested by @petter: The option to deactivate the performance warning from the debugger, and to move this to the Capacity tab instead:

  48. Suggested by @petter: A :negate operator for numbers that would turn a value negative (e.g., turning 5 into -5). The +hours, +seconds etc. for date fields is very cumbersome to use if you want to subtract something, and instead of adding a minus operator to all of those fields, a negate value operator could let us subtract hours etc. without going through custom fields.
    A +minutes operator would also be helpful.

  49. Suggested by @zelus_pudding: Ability to set the height of a group/repeating group to be equal to the height of the viewport. Here is a similar example of this design in Evernote:

  50. Suggested by @petter: The option to quickly identify elements that are overlapping by showing their borders in red when a button is held down (or a setting is activated). “On big SPA’s, two out of 100 groups overlapping by a single pixel can wreak havoc. Would be a timesaver to be able to spot them quickly”.

  51. Suggested by @klaas.vanhoeck1: The ability to edit the responsive settings (e.g., fixed-width, minimum width) of multiple elements at once. This option would save time when trying to make an entire page responsive.

  52. Suggested by @petter: Make “clear all” reset to empty field instead of …edit me…:
    image

  53. Suggested by @luke2: The ability to add editor comments for individual conditionals to help keep things organized.

  54. Suggested by @aloecf : Bubble based editor zoom hotkeys with a scroller (similar to Figma). This approach would be easier than using the zoom percentage input.

  55. Suggested by @w.fly : The ability to “show” elements that are hidden on page load, in the editor by default. One way to do this would be to add an “Outline hidden elements” option (similar to the “Show element borders” option but for hidden elements). "We all know that hiding an element then showing when you need to is a great performance gain for your Bubble app - But it makes things clunky when you’re using the editor. Each time you load a page to edit that has hidden elements on page load, the element is invisible - Leading to large blank spaces on your editor page - Requiring you to manually un-hide each time. For SPA apps, it’s a killer if you have 25 hidden groups on a page. This is how hidden elements are currently displayed in the editor on load:


    AFTER (put an overlay on top of hidden elements, so when you open up a new page, you can SEE what all hidden elements you have without having to click into each one):

    The option in the editor could look like this:

    (Notes: This would not apply to popups/floating groups. The recommendation is to start with groups/repeating groups first. And, clicking on the eye icon at the top left of the outline would unhide it so you can rapidly edit right there.

  56. Suggested by @julienallard1: Similar to 56., add an option to use the “last visibility state” in the editor so when the editor page refreshes, we would find the displaying elements in the same state as they were before.

  57. Suggested by @yusaney1: The option to duplicate a single data entry in the App Data tab.

  58. Suggested by @aloecf: The ability to set up grids, gutters, and margins. “Right now Margins are not able to be set so the left one is always 12px. Can we implement something to change the default margin for that left column?”:

  59. Suggested by @duke.severn: The option to use “:defaulting to” for any type of empty values (the current option is text-only).

  60. Suggested by @julian_digitalsilva: The ability to group workflows by workflow folder when viewing all workflows.

  61. Suggested by @gsantoro: The ability to choose the position of a popup element.

  62. Suggested by @duke.severn: Suggested by duke.severn Preload the :formatted as currency initial content values with the most recently used values:
    image

  63. Suggested by @paul.dalpozzo: Have the undo button display a short history of past edits (similar to Adobe or Microsoft Office products). It would also be a nice feature have the option to select multiple items in the history to remove.

  64. Suggested by @paul.dalpozzo: A “workflow tree” view so you can trace precedents and dependents (like in Excel) so you can quickly see a map of how workflows work together in complex combinations - like for instance a page workflow that schedules a backend workflow that then calls another backend workflow recursively, or allows easily viewing a user flow through workflows and pages.

  65. Suggested by @paul.dalpozzo: Functionality to auto-create inputs or outputs on a page from a thing’s fields. The flow would be something like: “Click to add a thing to this page” -> select inputs or output types (similar to the API “initialize calls” popup window layout) -> click ok -> the editor creates all the selected elements on the page already connected to the thing in the DB.

  66. Suggested by @paul.dalpozzo: Ability to add “columns” to a text element that will automatically reflow content in 2 or more columns.

  67. Have the group element’s “Collapse this element’s height when hidden” setting checked by default since this is usually checked.

  68. Add the ability to set a standard group element to become a floating group through a conditional. For example, in most messaging apps, there in group on the page which contains a multiline input for the user to write a new message. At mobile page widths, this group needs to float to the bottom of the user’s phone for a better UX. If we could set a group to float through a conditional/property change that would save time and eliminate the need to create different UIs for desktop and mobile.

  69. The option to temporarily turn off the “please refresh this page” option in development mode, and allow each Bubble developer to test just the page that they’re working on (e…g, ?refreshoff=true). When two collaborators are working on different pages in the same development version, this would allow each collaborator to preview their page’s changes without needing to reload the page each second, due to the other developer’s changes.

  70. The ability to move two elements that are within different groups at the same time.

  71. The ability to import/export a single page (with all of its elements, workflows, and data types). This would save a lot of time from having to fix many errors when copying and pasting with workflows.

  72. The ability to auto-generate a single-page for mobile apps, after selecting multiple pages. Each page would be copied into the new single-page with all of its workflows, stacked vertically. There may be a few errors to fix but this would save time from having to manually copy each page and its workflows into the single page.

  73. Suggested by @klaas.vanhoeck1: Every time you select a certain input in the workflow ‘make changes to a thing’ or ‘create a thing’, you have to click 2 times. Once for selecting the input (i.e. input Name) and the second time " 's value ". Instead, the editor could always take " ‘s value’ as the standard, because 99% of the time this is the case.

41 Likes

@fayewatson I like every one of them. Great ideas to speed up development!

4 Likes

Great idea and appreciate the time spend behind each section to keep it simple. Hope @emmanuel will see this

2 Likes

Great point @fayewatson! Cloning element conditions would be nice add on too to speed up things.

1 Like

Thank you so much, @boostsalesgroup! :slight_smile: Are you referring to copying an element’s conditionals? If so, this is possible by right-clicking the element, and selecting “copy conditional formatting”, and then right-clicking the second element and select “paste conditional formatting”; or are you referring to something else?

Thanks! I didn’t know the functionality was already there. Pretty sure I have tried it before. Anyways this speeds up things a bit more for me.

Hopefully we will get your other improvements too!

1 Like

These are great ideas, some which I haven’t thought of that would definitely improve development speed.

Also have some suggestions of my own.

  1. Add a :formatted as function for geographic locations and allow us to define what gets extracted similar to the date :formatted as. For example you would be able to get street address, street, city, state by typing in sa, s, c, st under custom formatting for a geographic location. Right now you have to copy and paste the dynamic data in a text box for each individual field you want to extract.

  2. Allow us to see responsive settings inside the UI builder tab. Sometimes I know what responsive settings I need without having to see a preview, and it takes time to navigate to where I was inside the responsive tab just to change a few settings.

  3. I know you said this one already, but the ability to search for elements when trying to populate a number field. This is a big one, as I have a huge single page app, and it’s very tedious trying to track down the input I need to use. A work around is to search for the input in the workflows’ conditional, then copying the element you just searched for and pasting it in the number field.

1 Like

Great list, @fayewatson. I’d also like to see an inline element search function, similar to the “Search for new elements…” search, but for the actual elements on page. Right now you have to either 1) remember where the element is and dig through the tree manually, or 2) use the page search function, set search type = element type, set element type = whatever, click the this page only box, and then click enter, like this:


… and then have to click on the element from that list, find it on page, click into its properties, click reveal in element tree, etc.

… As opposed to a simple type-ahead search similar to this (but instead of just pulling up “Map” as in this example it pulls up a list of Map A, Map B, Map C just as the page search does in my above example):

(I would love for someone to tell me this already exists and I just didn’t know it!)

1 Like

Great list @fayewatson - thanks for posting it. I have long felt that creating tools and features to make programming quicker and friendlier with Bubble should be a priority for the Bubble team, along with performance improvements and all those other wonderful things they must be working on.

In addition to this already great list, I would also like to see:
A) some sort of smart select tool that would allow us to select all children of a parent for example, or all siblings, or all elements of the same type etc.
B) the ability to swap the positions of two selected elements
C) a way to set a group’s type and in one click, have the type and value cascade (as parent group’s thing) down to all/selected sub groups within it.
D) as I’ve asked previously, a sweeper tool to sweep all elements up or down from a certain point, like this https://youtu.be/xWurQ7-KTFU?t=40 or just the ability to move all selected elements up or down by a specified value in any direction.

1 Like

Thanks, @tim12333! :slight_smile: I 100% agree with your suggestions. A custom :formattedas function for geographic locations would save so much time, and I agree – sometimes I want to tweak a responsive setting (e.g., the fixed-margin of an element) without wanting to go to the responsive editor, making it visible there, and then adjusting that. Great ideas!

Thanks, @edd! :slight_smile: I think that this is not obvious since the search looks like a dropdown, but is this element search what you are looking for?


(I also have a difficult time finding elements on the page sometimes. I believe that there might be a bug with the issue checker in that when clicking on an issue, it doesn’t always bring you to the element that the issue is referring to.)

Thanks, @louisadekoya! :slight_smile: I completely agree with all of your suggestions! Every single one of those would be huge timesavers!

2 Likes

Thanks @fayewatson for taking the time to illustrate the other suggested ideas and for adding them to your original post. Great to see.

Let’s hope the Bubble team implements at least some of them.

1 Like

Brilliant Post @fayewatson! I hope the Bubble Gods are looking down at you.

:raised_hands::pray:

1 Like

I’m in favor of all these changes :grinning: I will add one more:

  • Preferred currency settings per app so we don’t have to set the currency format manually every time we need to use the :format as currency.
2 Likes

@fayewatson I have been using Bubble for 4 years and I don’t know that I’ve ever clicked on that “dropdown”. Always nice to learn something new …

1 Like

@Eli Great idea Eli! :slight_smile: I’ve definitely had a need for that one too; I’ll add that to the original post!

@edd Ah! I know that feeling too; I only very recently found out that you can copy an entire text value that contains a combination of static and dynamic expressions (I was previously re-creating them each time). Glad to know it now but I couldn’t believe I never saw that option for years…:see_no_evil:

CopyExpressions

1 Like

Oh my! That one I knew! :slight_smile: Now if only Bubble would let you copy and/or paste just part of a single (long) dynamic expression …

(I eagerly await someone’s reply telling me that that is also currently possible.)

@edd This one? :smiley:

No, that overwrites the entire single expression. I mean a feature that might be called “Copy selection” where if you had a long conditional expression like:

Current User's favorite color is "blue" and Current page width <= 1040 and xyz custom state is "yes" and Current Page Thing's flavor is "bitter"

you could just highlight and copy the Current page width <= 1040 and xyz custom state is "yes" part and add it to another dynamic expression somewhere else in your app, or just cut the selected section.

Use case: Suppose you’ve been using the above expression but no longer care about the Current User’s favorite color. You either need to rewrite the expression from scratch with only the last three clauses, or convert the first one into something sure to pass the condition like Current User’s email is not "[email protected]" (or equivalent nonsense).

2 Likes

@edd Ohh, right! Got it! :slight_smile: I totally agree! That would be a huge timesaver; I’ll add that to the original post!

@fayewatson :clap: some great ideas here, thanks for sharing these, I can appreciate the time and effort put into these.

Each point is all so useful. But just thought I’d my 2 cents.

1 - Building expressions where numbers or geographical addresses are the expected results and not being able to search is quite a time killer, especially with big pages. It would certainly speed up development, make things more fluid then having to scroll through lists of elements to find.

4 - Its quite a small thing, but very handy and just adds the extra layer of organisation.

5 - Quickly adding all fields of a thing into a workflow action e.g. create, make changes…would be another nice speed booster for development.

9 - Being able to multi-select elements from the elements tree would make things so much easier.

12 - This is quite essential, as is the responsive preview is pretty cumbersome, but having the data type render actually data would be oh so nice.

13 - Map extraction data like the custom dates composer is a great idea, will save having 4, 5+ expressions, consolidated into 1.

17 - Another useful time saver.

18 - This can get very tiresome having to create new gaps/spaces in between groups and elements. It would save having to use the empty hidden collapsing group trick and then fiddling around with getting the margins just how they were.


Just to sneakily add in a quick couple of ideas of my own into the mix :wink:

3 Likes