Multiple client support
Hello, the "app" structure seems very rigid, is there a way to have multiple clients for the api ? What if i need a chrome plugin, a capacitor app and a web site which all want to to talk to the same api and share code ?
4 Replies
That's a great question 🙂 we would love to support all of that!
So, one great API with RPC for all the clients. But since we are still in beta, we are trying to focus on the web part first to polish it completely. Support for multiple different clients will be coming in the future, but we can't commit to any ETA since we are a small team 🐤
One thing you can do right now is use
api feature of Wasp to just expose HTTP API, that you can then consume from anywhere. But, it won't be having cool properties like Actionsa and Queries do (reactivity), and we also don't have direct support for you to do your chrome plugin or something else, those would be separate projects. But this way you could reuse the backend logic.Btw this is super exciting, I would love it if we had this, but it is just a big undertaking and we are still wokring on other stuff, but I hope we will get there at some point!
I created an issue on GH for it to, track the idea better: https://github.com/wasp-lang/wasp/issues/1475 .
GitHub
Support for multiple clients · Issue #1475 · wasp-lang/wasp
An ambitious idea: Wasp supporting multiple clients, and not only multiple web app clients, but potentially different types of clients: mobile app, chrome plugin, desktop app, ... . So for example,...
Thank you for your answer !