I made it so chrome tab is a tiny bit faster by keeping a session around
app does not quit so often (at least in dev)
There are some glitches I know about that we will sort out next week.
Regarding @mcwumbly “I want it to load faster”, I hear you loud and clear. I saw this in action when @tgxworld was demoing the issue to me. I am unsure if chrome tabs will ever be able to cache to the degree a leaving a tab open in chrome does.
I will look at splitting up the notifications and grouping next week.
Introduces new user api, this API defines the concept of scopes, you no longer have to grant full write access to the app.
Upgrades internal components
Fixes a case where the search field would clear after submit
note the change to the app is breaking, it will only work on the absolute latest releases of Discourse. I am deploying stuff internally now.
Overall, I feel the app is in a good enough shape to go in the app store now, our internal APIs are all good and the app is feature complete enough for a v1.
On the android front I would like to get around to notification grouping, so you can expand the group of notifications and click on each, however I don’t feel this feature is blocking.
If the target forum contains ads, does the app render them too? If not and this app is released for the general public, that is a potential monetization leak.
The app doesn’t render the site, Chrome does. So if you ads appear in Chrome on Android, the app doesn’t change that. The app simply provides a clean notification system for mobile, with easy direct access to the mobile version of your Discourse instance.
. Any more beta invites going spare? 
