[bisq-network/proposals] Bisq remote (#25)

[Joachim Neumann]

I would propose that I start out with a very lean Bisq notification server that is not a Bisq node.

Later, we can decide between
* Option 1: The user keeps Bisq running on his computer, in which case a Bisq Notification Server could route bidirectional encrypted message between the phone and Bisq on the computer. In this case, the Bisq Notification Server would not need to be a Bisq node.
* Option 2: The user can opt for a cloud-based Bisq node and does not need to keep Bisq running on his computer. He might even not need to run Bisq on his computer at all, the cloud node and the phone could suffice.

I think that Option 1 makes more sense, because 

1. The use cases for the mobile app can be limited to the functionalities that are most useful while being on the move. This makes the App clean and easy to use.
1. A cloud-based Bisq node would require the mobile apps to support the complete set of functionalities - including all settings and the wallet. This is a lot of work to implement and would be beyond what I plan to contribute. 
1. Option 2 would add additional burden for new Bisq features, because each new feature would need to be supported on the desktop and in the all mobile apps. Otherwise the mobile Apps would render the could based Bisq node incomplete. I am not sure that the mobile development resources would be available for each new Bisq feature.
1. In Option 2 complications might arise for users that have a Bisq node on their computer and a could-based Bisq node 

-- 
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/proposals/issues/25#issuecomment-394168947
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180603/f3d39c19/attachment.html>