We are absolutely thrilled to announce @mneary0 rejoining the team as a Product Director 🎉. He is a @bubble legend, an expert in building top quality products, and just a really great, thoughtful guy to work with. Welcome back Matt, we're really lucky to have you!.

Applications to the next cohorts of our professional @bubble bootcamp are due this Friday - learn more and apply below!.

Pro tip for @bubble devs: Debug complex logic in 4 steps:. 1. Create a “debug” group.2. Add your key var/data in a text inside it.3. Make it visible only when debug_mode=true.4. Use this on-demand group to track values & spot errors faster

You definitely can’t build Calendly with 15 hours of prompting. But with dedication and @bubble you can build something better. Follow along as we launch Aircal: a smarter, faster scheduling tool optimized for having a streamlined calendar.

The idea we’re building?. A smarter, faster Calendly alternative, powered by AI and built 100% on @Bubble. We're calling it Aircal, and we're focused on making the scheduling experience actually delightful. Learn more:

RT @bubble: It’s time! We’re opening native mobile up to public beta. Check us out on Product Hunt, grab a 1-month Starter promo, and drop….

We’re trying something new. After years of building for clients, we’re using what we’ve learned to launch our own SaaS product on @bubble. And we’re documenting the full journey: ideation, build, launch, and (hopefully) growth 😅. Follow along at

When creating or editing an object in your @bubble app, start by creating the object if it doesn't exist. Then, in a 'Make changes to. ' action, pass a list containing both objects, and use the :first item—since only 1 will exist. You'd only need to input the field values once!

Files in @bubble are public by default. To make them private, check the 'Make this file private' checkbox when uploading to avoid accidental exposure. If someone knows the URL of a public file, they can access it even if they are logged out. #nocode

Essential #UIDesign checklist for your @bubble app. #5 Use dividers and borders to better group information. When dealing with a lot of fields and data, cohesive display is key. Dividers & borders can create clarity—don’t hesitate to add a divide.

Essential #UIDesign checklist for your @bubble app. #4 Use the same patterns for similar functions. Maintaining consistent design patterns across your app significantly improves usability. When users know where to find similar functions, they navigate more efficiently, reducing

Essential #UIDesign checklist for your @bubble app. #3 Use color only to signal clickability, selection, or status. Reserving vibrant color for interactive elements lets users scan the page quickly and grasp the available actions

Keep your @bubble app light to improve performance and simplify maintenance by using the Optimize application feature often. Read our article for two handy code snippets that make this process easier.

Continuing our essential #UIdesign checklist: 10 key elements for your @bubble app designs!. #2 Use consistent padding and spacing. Creates clarity, helping users quickly identify related elements. Improves visual hierarchy and reduces confusion.

Applications for the next cohorts of our guided @bubble bootcamp are due this coming Monday!. Learn more and apply at the link below.

Starting a tweet series on #UIdesign with an essential checklist: 10 high-value elements to check in your @bubble app designs!. #1 Use consistent alignment. It improves predictability and makes the page easier to scan. #nocode

Starting tomorrow we’re sharing tips to improve your designs!. You don’t have to be Picasso to create great User Interfaces in your @bubble app. Stay tuned for our checklist of actionable items to enhance your designs based on a process, not on design intuition #nocode #UIdesign

Use the :formatted as JSON-safe operator in @bubble to ensure clean API calls. It wraps texts in quotes, converts yes/no to true/false, formats dates to ISO UTC, and escapes breaking characters. For lists, it quotes each entry individually to maintain proper JSON formatting.

Do not use the @bubble built-in "Created by" field for object ownership, as it's immutable. This field indicates the object creator but not its "ownership.". Best practice: add an "Owner" field of type User to allow ownership changes or to assign object ownership after creation.

Privacy rules & @bubble:.1 Create them before adding logic.2 Start by restricting access to all data and then gradually add rules to unlock access as needed. Ensures:.1 Your logic works with them in place.2 No data is unintentionally exposed. Do you follow a different approach?