When you login via Google/Facebook the auth flow is interrupted, you must close site and reopen to reconnect.
Unlike iOS, Android really dislikes lots of discrete notifications, instead it expects 1 notification per app that is updated, we will redesign. At the moment notifications are out of control.
Background fetch is not yet implemented, this means there is no fallback on Android for push notifications on sites we do not host. We plan to address this somehow.
The app normalizes on Chrome stable for all browsing. If you do not have Chrome stable installed you can not use the app. Chrome beta and canary are not supported. Built in browser or custom browsers are not supported. This is entirely by design and a great normalizer.
Big thanks to @joffrey_jaffeux for lots of the work on the app and you all for testing.
Please reply to the topic if you would like to beta test and I will send out an invite!
It is not simple… for one we don’t even have a page for “settings” at the moment in the app, when choosing the intent preferring “unstable beta” over “stable release” is not a correct choice, if we added a “fallback to beta” you would have to uninstall stable to have it pick that.
That would be fine with me. I don’t have stable installed at the moment, and would prefer to not need to install it. However, if it is that complicated development wise, I’ll go ahead and install stable.
I’m finding it quite difficult to tap on a discourse instance to open it. About half the time it’s trying to slide to show the delete button. I really have to woodpecker it with my finger for it to register as a ‘click’.
Been playing with the app this evening, and have received numerous notifications for this topic (that I’m watching). Can confirm that the individual notifications are overwhelming. May I suggest looking into the way Gmail rolls up its notifications into one?