So this is for my app with currently about 200 users where I’ve already gotten complaints of things being slow. Unfortunately bubble doesn’t support dynamic font styles so I have to do a massive workaround. I work alone so I’d appreciate your guys’ thoughts. Not sure how to handle this…
Essentially, my app allows users to choose fonts dynamically for a design they send me to print.
So to do this, I save the name of the font into my database and set a conditional on the text element to change its font to xyz based on whatever it was saved to be. So "When current text’s font_style(text field) is “Open sans”… then I change the font to Open sans. That’s it, same for font size. So total about 50 conditionals currently with font choices and font sizes.
However… when they’re trying different styles, they need to see how it’s gonna look before actually saving it. So I also have to allow the font and font size to change based on what they’re trying at the time WITHOUT actually saving it into the database. This means I have to double every single conditional. I think it’s impossible to have both cases work within a single conditional. I tried so hard.
Everything works fine but I’m worried about performance as this would mean 120-170 conditionals on a single element. So ultimately this comes to the question for you folks… would it be fine to have all these conditionals on a single element? Or, is it preferable having a separate elements show for each case?
TLDWR/SUMMARY: If you HAVE to have 100+ conditionals to display custom states and database based stuff on an element, is it better to have it on the same element, split it into 2 elements (one shows when something is being edited, the other one shows when it’s not), or it makes no difference? In such case, it’s easier to do it on the same element.
I will be ultimately filling out about 220 conditions manually or more so this means a lot. But beyond the manual work, performance is my biggest concern. Kindly cast your vote!