Basically we need to introduce a concept of scopes, this is how I would lay it out:
id name description (localizable)
-- --------- -----------
1 notification_edit Read / clear notifications
2 user_info Read private user info
3 message_bus Recieve updates from site
permissions
id controller action type
-- ------- ----- ----
1 notifications get :get
etc...
One minor inconvenience with the app: when app goes in background (double tap Home button, go to another app and then return) it immediately refreshes the site if user is in a site.
Yeah this is out of the apps control, happens when safari decides it is low on memory, does not happen on iPhone 7 that much, not that it is much of a consultation
@Overgrow we are blocked at the moment on getting a D-U-N-S so we can create a team account on iTunes. We will have the app released publicly in anywhere between 2 weeks and 2 months.
I just did a new release today:
Fixes occasional blank screen on launch
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.
I have a little problem with notifications. Is it possible that the notification wouldn’t include the spoiler? It would look nicer in my opinion. Notification on iOS: