Everything from

Airdev

2 resources from Airdev we point founders to, and the questions each answers.

📄 Article
✓ Link checked Free Intermediate

Why we picked it This is the most-cited real example of a company that shipped its MVP on no-code (Bubble) and then moved to code, told by the team that actually built it. What makes it useful is the ending: Dividend Finance did not throw Bubble out, it re-engineered the app so the no-code front end calls a new code-based backend through APIs as it scaled to over a billion dollars in loans. That is the shape most healthy migrations take, and it is a good counter to the "rewrite everything now" instinct.

Dividend Finance Scales Its No-Code Loan Platform

From Airdev by Airdev

  • The switch was driven by scale and business logic, not developer preference: they added custom code where Bubble genuinely could not carry the load, and left the rest.
  • The path was hybrid, not a full rewrite. Bubble kept serving what it was good at while heavier logic moved into code behind APIs.
  • Note the source is the agency that built it, so read it as a real case study but not a neutral one; the underlying facts (funding raised, loan volume, timeline) are corroborated elsewhere.
Open airdev.co
📄 Article
✓ Link checked Free Intermediate

Why we picked it Airdev is one of the largest Bubble agencies, and this is their production checklist for keeping apps fast. It reads like a team standard rather than a blog post, covering searches, page structure, and loading order in one place. Useful when you want an opinionated list to audit against.

Optimize for speed (Bubble Development Best Practices)

From Airdev by Airdev 15 min read

  • Load only the data a page actually shows
  • Prefer server side constraints over client side filtering
  • Treat speed as a build habit, not a late cleanup
Open docs.airdev.co
eChai Partner Brands