I am going to keep a list of known issues updated in this post, so be sure to check the first post in this topic prior to reporting stuff.
How it works and what it does.
The Android app is an open source react native application. The vast majority of the code is shared between our iOS app and it. Source code lives at: https://github.com/discourse/discoursemobile
The app takes care of keeping track of unread/new counts and notifications counts across multiple Discourse sites.
For sites we host you also get āpush notificationsā for every notification you get.
For the Android port we needed to implement a native library for public/private encryption, custom internal implementation of push notifications and a native library for chrome custom tab
Known issues
Android has no concept of application badge it is a shame to miss out on this feature but unclear on how we can implement it, feedback on how welcome
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!
I would encourage working with 3rd party launchers. A current popular one is Nova Launcher with Tesla Unread. You can review the API here.
I will share that (personally) this is a big disappointment. I fully understand not supporting canary, which updates insanely frequently, but beta has a much more reasonable pace of updates.
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?
(ping 
