There are two ways you can integrate the Xano API in Bubble. One with the “API connector” plugin and another way is with the “Xano Connector” plugin. Let’s understand the pros/cons of using the Xano connector plugin:
Pros of choosing Xano Connector -
All the API calls happen at the client side, so there’s no Workload Unit consumption for making the API call.
The connector plugin has a Xano auth element that handles all the authentication process. You won’t need to handle much.
All authenticated APIs automatically pick the headers; you won’t need to pass them manually.
Since these API calls happen at the client side, Bubble doesn’t cache the API result.
Cons of using Xano Connector -
You can’t upload files via the Xano Connector.
Since API calls happen at the client side, anyone can see the API URL and headers.
Item 2 applies to all apps with front end + backend setup. You will see the urls and headers to the backend for any such app. The backend just happnes to be Xano instead of Bubble, NextJS, Express, etc.
Perhaps though it would be acceptable for public data, and help those folks who are worried about WU usage on public pages. The guy for example recently with spike WU on a home page.
Just a thought. Well made me think. Marketplaces, SEO indexed stuff, large amounts of public stuff coming from a database.