[bisq-network/bisq] API Feedback And Next Development Phase (#5407)

sqrrm notifications at github.com
Tue Apr 13 10:49:43 CEST 2021


Thanks for the write up.

### UI
I think using the UI to drive API dev is a good idea, although that doesn't mean other use cases should be ignored. I would also like a web and mobile UI but at this point it's not clear how much should be done as part of the DAO and what could be just left to anyone who feels so inclined.

The benefits of being Bisq DAO sanctioned is that users feel more confident in using these UIs, and they would perhaps be more full feature. The drawback is that we would have to support them and the efforts to support multiple UIs, the current client, web and mobile, could become too much and splinter the focus, making all UIs worse in the process.

I think there is a benefit to code refactor, but that could be gained by just support the client UI as we do now and exposing the api for external devs to use and build their own.

### Bots
I don't think there should be any DAO sanctioned bot. Anyone who wants to write one can do so and reap the benefits themselves. The exception being if we find a use case for a burningman bot or some other automation of roles that has been discussed elsewhere. Proper documentation on how to use the API should be enough I think.

### Inconclusion
I'm not sure what direction is best here. I'm leaning towards starting on a simple web or mobile UI that can't trade but that could receive notifications and see the market. 

Keeping the CLI as reference sounds good.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/discussions/5407#discussioncomment-603741
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210413/920b5887/attachment.htm>


More information about the bisq-github mailing list