WeWeb + Xano build strategy for API-driven tool

Hello everyone. I was hoping someone could provide some insights into my approach to building with WeWeb + Xano.

I am building a web application that uses data from multiple APIs to create a narrative for users. I want to know the best approach for building this. Which of the following do you think makes the most sense?

  1. Use WeWeb to pull API data, send that data directly to Xano, then retrieve the augmented Xano data into WeWeb and display it in charts and tables.

  2. Use WeWeb to pull API data and then immediately create variables in WeWeb and use those to display data prior to sending it to Xano for storage

  3. Use WeWeb to take basic inputs and send them to Xano to perform API calls before retrieving them from Xano and displaying them in WeWeb

  4. Something else?

I realize the answer could be that it depends, but for the majority of use cases, what would everyone recommend? What is the approach you would take when building a similar app?

Thanks in advance.

I would be in favor of option #3. I prefer to have Xano do as much of the API calls and business logic as possible. That keeps the weweb code focused on the needs of the UI. It also makes it easier to reuse the Xano logic/APIs for other front-ends if needed. If you create a mobile app someday, you wouldn’t want to have logic and API calls in your weweb UI that you could have done in Xano that would then have to be recreated in the other app…just my two cents worth :slight_smile:

5 Likes

#3 for sure! Have Xano make the calls. There is a LOT of things you can do in Xano with the response from those calls to further optimize and/or aggregate, sort, etc data before it’s even pulled from front end. Do all your heavy data lifting and manipulation in Xano and focus WeWeb on user experience.

4 Likes

Thanks both! I wasn’t going down this path. I will change my approach and pull only user input data in WeWeb and send those requests to Xano to do all the data manipulation, then retrieve it back into WeWeb formatted nicely. This is a big help. Thanks!

1 Like

It can also be your only option if your APIs need to be called in a secure way, you will not be able to use them directly inside WeWeb it would mean make secret api key public!

So yes, making theses call inside Xano is probably the best approach :slight_smile:

4 Likes

Surely #3. I’m producing a coaching program regarding Xano and WeWeb. Would you like me to add you?

hi Profound

Can u please share some more details on this coaching program?

Yes I’m offering WeWeb and Xano coaching and development services starting at $60/hr. No task is too small. Happy to chat more of needed.