A bit of feedback: I’ve never seen much importance in the notification badge count. It’s certainly something I can live without. It’s worth checking out how WhatsApp does notifications (this also ties in with the concept of updating one notification instead of sending multiple), since it shows a breakdown in the bottom of the number of notifications, such as “x messages from x chats”. Something like that here would fill the badge void in my opinion.
Issues:
Emoji are not translated in the notifications.
My custom SSO site needed to be added twice. Once to log in, then again to complete the addition process.
Features:
Add a ‘latest’ count as well as unread and new.
Ability to remove sites.
Great to see android version available in short time. Nice work
Here is my quick feedback
Everytime I open a notification item, It takes lot of time to load the page (atleast the perceived performance is slow in chrome tab). While it is acceptable to wait for the first page, it provides a bad UX for every notification link to take the same time to load. It appears to me the cache is not maintained across the pages in chrome tab.
After a notification page is read, the read status / badge has not changed immediately. Actually, It did work for some notifications then stopped working after a while.
It would be nice to have a dismiss notification feature to clear the notifications (atleast those which are read). Actually this is nice to have even in the web app.
During authorisation, the name of the app was shown as “Discourse - unknown”
If there is no chrome browser installed, can we show some error message about the need of Chrome Stable browser ? To me it closed the app.
Anyway, I was trying to build the mobile app from github code. Sorry I cannot send a pull request now. These are the small changes I have made to make it work.
"react-native-fetch-blob": "^0.9.4",
The above line was missing in the package.json.
After adding the above line with npm install, it properly created an apk. I could add a discourse site. But I was not able to connect to them.
The below exception was thrown
possible unhandled promise rejection undefined is not an object(evaluationg this.props.simulator)
I think it is originating from this part of the code