@vincent56 and I have already discussed this a bit privately, but I’ll add my five cents here to in case it’s useful for someone else.
I made our entire app in Bubble, but the landing page in Wordpress, and here’s why:
Wordpress worked out of the box
For the features I needed for the landing page, Wordpress (with the Divi page builder that I use) offered it pretty much out of the box, whereas in Bubble I would have to build it. For the app of course, it was the other way around – Wordpress couldn’t possible match Bubble’s flexibility. Wordpress was just a lot quicker, and would be 100% responsive instantly.
I didn’t want traffic on the landing page to affect the app
They could of course be separated, but it would cost more. At our current traffic level and Bubble package, a spike in traffic on the landing page would noticeably affect the app.
Bubble is not yet fast enough
As much as I love Bubble, it’s just a fact of life for now that it’s slow compared to other platforms. For a while, I did a hybrid, with Wordpress as the main site, and a registration form powered by Bubble in an iFrame. Without Bubble, the page loaded fully in about 4 seconds (I can’t remember the exact time). Adding a Bubble form with two text fields and a button, it took nearly 20-25 seconds to load the same page, which hurts conversion rate and SEO significantly. I just couldn’t defend keeping the form vs. loading time.
I don’t know how Bubble performs SEO-wise
Bubble might be SEO friendly – and it might not be. I just don’t know. What I do know is that Wordpress is extremely SEO friendly, so it felt safer to go with. The loading time is of course not helpful to SEO either.
There are many perfectly good reasons to build a landing page in Bubble, of course. But with the tradeoffs described above, it just wasn’t right for us at this time. It might change in the future. Optimally, I’d like to have everything “speak the same language”, but not at any price.