Cliff

Our #Nocode, in person hackathons are always fun and challenging. Check out photos from our last session building with @bubble 😊 As I mentor participants who are preparing for the no-code challenge to take place this weekend @JJEnglert @jameore @buildcamp @emmanuel_s

@george_nqu @bubble Nice looking, doesn't this already exist? Canvas placeholder? Or am I missing something..

Pretty nice feature for @bubble - renaming arbitrary text expressions!

The best decisions we've made at Bubble came from listening. Join me for another live AMA on April 9 at 12pm ET. RSVP link in the replies.

Use cout: =>1 or <1 and all its variations instead of 0 (zero). Every @bubble dev should know this. Thanks @brentonstrine for this demonstration.

Decided to resume work on this @bubble side project, CRM-ish Template dropping soon. #NoCode

@george_nqu Huh? 😯, how do you edit such?, i bet they refresh the editor every minute.

One of the worst positions a SaaS founder can be in is when you have to stop selling because your own product can't handle new clients. I spoke with a founder who'd worked with a large Gold tier agency and recently just landed three big accounts they'd been chasing for years. It should have been a celebration. Instead, training sessions were falling apart because the app kept breaking. Clients were frustrated before they even started using the product. They had to pause outbound entirely until the app was stable enough to not embarrass them during onboarding. This is what happens when technical debt compounds unchecked. You don't notice it when you're small, but the moment you start landing real clients, every shortcut from the early build shows up at the worst possible time. The frustrating part is most of these issues are fixable. They're not platform limitations or fundamental architecture problems. They're build quality issues that accumulated because the original team was trying to move fast and nobody was thinking about what happens at scale. (this is the most workflows I've seen on a page, by the way).

@NjenuiN30786 @graphics86821n What is it built on?

It's been a pleasure working on this amazing project for Saint John Academy of Excellence with @graphics86821n ✌️🤩 stjohnacademyofexcellence.com/gallery/

@MTNCameroon was able to get a card & use within 2 minutes (As it should be) But see me on queue at @UBAGroup this past week. Till date, card doesn't work. Even reached out to their support to no avail. I regret the money i paid to get a card that doesn't work. I want a refund.

@donald_ndim These designs look good.

Everything is looking great so far for our Property Listing Bubble Mobile Template. This will help creators and founders launch Real Estate apps faster! 🚀 Bookmark the post and keep an eye so you won't missout when it's released! 🏆

A dedicated API menu? 😊 Thank you @bubble the year's definitely off to a good start @ClausISaidSo you seeing this? #NoCode

@george_nqu @bubble Maybe do one for us here, so we stay up to date..

Security on @bubble shouldn’t be a black box. The smartest teams we work with don’t just want a patch - they want to understand the vulnerabilities. That’s why we run internal workshops with their developers. We teach in-house devs how to build securely on Bubble - not just patch issues, but prevent them. Fixing a leak helps once. Understanding why it leaked helps forever.

@brentonstrine @george_nqu @bubble For me it's settings defaults without using workflows. Now I blend RE properties and ground vars

@george_nqu @bubble So many reasons to use group vaes over states. The power of being able to use conditions alone settles it for me.

We stopped using custom states in @bubble. They’re hidden, clunky, and can’t be set dynamically in a clean way. Group variables do everything better: visible, dynamic, and searchable. If you’re still using custom states everywhere, you’re building blind. They make your logic transparent and reduce the "where the hell is this stored?" problems when working on a large app.

@george_nqu @bubble I feel so guilty, I've done it for so long that it's now a reflex.

Most devs waste time renaming every element in their @bubble app. We don’t. If it’s not part of a workflow or key UI logic, it doesn’t need a name. “Group X” is fine. Over-naming slows development, ruins element search (Bubble's default is an implicit convention), and adds zero value to the client. Name what matters. Ignore the rest.

@george_nqu @bubble @ClausISaidSo Very important, especially when you need high priority properties at the top, and optional ones at the bottom.

Looks like @bubble just made properties reorderable. This is awesome! @ClausISaidSo what's your verdict?!

@PrashantAbbi @george_nqu @bubble I don't think you've understood the question. That is an action on a DB trigger that updates a products searchContent field. On the frontend when he searches for products, he'll use "contains" and convert the users search term to lowercase as well. Hope its clear.

@george_nqu @bubble If it's a search across multiple fields, it should use contains instead of eq?

What's wrong with this expression in @bubble? Can you improve it?

@george_nqu @bubble @brentonstrine Really? I didn't know that. Example: Current users things "contains" x Or X "is in" currently users things You saying this wouldn't consume WUs?

@cliff_fuhche @bubble @brentonstrine Constraints don't use WU.

Which @bubble expression consumes less WUs? "Is in" or "contains" @brentonstrine @george_nqu

Sometimes I feel so guilty about the workarounds I do in my @bubble apps.

It always warms my heart when i see one of my protégé making strides in the @bubble space. Keep up...

@donald_ndim @bubble @fede_bubble @ayfolut @theo_goldberg @pseudonimoYuri Congratulations 🎉.

Excited to have been onboarded to the Cohort 3 of the @bubble AMBASSADORS PROGRAM! 🎉 Being the First Cameroonian 🇨🇲, it's with great honour that i take on this spirit of servitude towards our community of career builders, Startup founders and public institutions. 🚀

@george_nqu @bubble I immediately thought of at least three instances where I have made this mistake, rushing to fix them 😉

PSA for @bubble devs: more search constraints ≠ faster performance. If Project = X already implies Company = Y, adding Company = Y just gives the DB extra work.