[bisq-network/bisq] bisq mobile notifications should NOT rely on "google play services" (#2441)

[21m]

A suggestion: why not take a step back in the process and instead of providing people the whole mobile app, relying on Google Play Services make the Bisq App simply make an HTTP request configurable in it?

This way anyone can set up a webhook to listen to this HTTP request and use whichever methods they deem relevant for delivering the notification instead of a) relying on a mobile app with Google Play Services and plus b) Bisq does not need to endorse nor develop/keep up to date, the mobile apps themselves.

Even users that aren' t technical can set up a webhook with zapier and such no-code tools.

I use Graphene OS and find it quite annoying that the Bisq UX is so poor in the notifications regard. Some notes on how the experience could be:

* user goes to Account > Notifications tab
* the Setup Section has a couple of simple fieds to configure the HTTP request (endpoint URL & auth token if any)
* Save button & Send Test notification button

And that's it, Bisq's development responsibility ends here and in providing some documentation as to how to set this up. I as the user can now get bisq notifications in the form of a Telegram bot, Matrix bot, even a postcard if I want. 

I do wonder (and I'm ignorant about it) if clearnet http requests can be made from within the bisq client directly or if they need to be sent to seed nodes in order to move from onion to clearnet

Thanks everyone, 

I'd really love to see bisq notifications again in my Graphene phone :) and I'm confident I'm not the only one


-------

On a Different note: the workaround I'm using now is that I set up a dumb Android phone with bisq that stays near my PC and put IFTTT on it. Whenever a notification from bisq arrives it sends me a private message over  to a private telegram group I have with just myself and the IFTTT bot






-- 
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/issues/2441#issuecomment-945542775
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20211018/05d76f5c/attachment.htm>