It’s more or less latest. I update on weekly basis or so.
I also tested adding it to my iPhone’s home screen and it uses a proper icon.
https://discuss.tano.si
Thank you for looking into it.
A few comment about apple touch icons. Discourse app should at least have white background as apple adds black background if alpha channel is present.
Another thing is that usually apple touch icons are square as iOS crops them. They look a bit strange in app. Maybe you could just use the logo small url or crop the image as iOS does.
Last minor recommendation is to tell the app when entering URL that we want to enter URL (I think you can do that). This will add the period to keyboard so URL is typed easier. Of course these are just minor UI improvements, generally the app works well. I got the notifications for our discussion.
4 Likes
Is there a reason why the URL of a Discourse instance is the main focus rather than its title?
I think it would look better if we had
Discussion about the next-generation open source Discourse forum software
https://meta.discourse.org
new (1) unread (4)
rather than
https://meta.discourse.org
Discussion about the next-generation open source Discourse forum software
new (1) unread (4)
(excuse the poor mockup but I’m on mobile)
Yes, mainly cause it would clutter that page a lot to have lots of bold descriptions of indeterminate length
I do feel new(2) and unread(2) may be a bit under-styled
1 Like
I think you should suppress the http:// and https:// bits though, just the plain URL is all you need.
6 Likes
After opening a site, reading the notifications and returning, the counter doesn’t always drop to zero immediately. Maybe the notifier could always refresh a site’s status after the SafariViewController is closed?
2 Likes
@joffrey_jaffeux committed a bunch of fixes for issues reported here last night and I tweaked some stuff this morning.
Build #3 is out.
-
Rotation now works properly thanks @fefrei for reporting
-
Flag counts were not included in the “badge” total thanks @henrikbg for alerting me to this, though we still want to improve overall alerting here at least they are not invisible
-
We now kick off “one last update” when we kick the app to background state. This improves the cases where you quickly check notifications and then exit app. However we still have a 10 second safety net, where we never allow more than 1 bg update per 10 second window. We may lift this. Thanks @fefrei for reporting
-
We remove the
http://portion from the list, it is just visual noise. Thanks @codinghorror -
We changed it so we use a much easier
RandomBytesalgorithm that does not require special native code, to ease the android porting. (we only use random for nonce and messagebus id in both cases there is no information leak on the tiny chance there is a collision cause JavaScriptRandomis sub-optimal. -
The styling for new/unread is now blue, I prefer this color it should stand out a bit
-
The styling of the connect button is a bit more consistent
-
We use the URL style keyboard thanks @ntadej
We are also making good progress on Android should have something soon.
btw… if anyone feels like fixing up the images here https://github.com/SamSaffron/DiscourseMobile/tree/master/ios/Discourse/Images.xcassets/AppIcon.appiconset it would be awesome 
Ever since @ntadej mentioned this the black border has been bothering me so much.
7 Likes
I’d love to help beta test!
1 Like
Would love to test it out.
Is there anything we will need to do on our end as a customer to have this configured?
Nope, nothing 
it is already magically configured
Invites are in the mail
3 Likes
Here’s something I found today:
After tapping a notification, I am taken me to the main screen (I was notified for the green badge) . Whereas previously the user was taken to the exact post/topic. Was anything changing in this build, @sam?
Details
iPad mini 1
iOS 9.3.1
Build - 1(3)
Yes please to the Discourse app!
1 Like
Wish I had an iDevice to play around with 
Android is getting very close if you feel like hacking on react native you could help rush it 
Atm my big blocking bits are getting crosswalk to be a bit more consistent and stop mucking with my statusbar and turn it white
Should have push notifications going pretty soon
1 Like
Sam does crosswalk bring any benefits for people on Android 4.2+, with latest chrome as the default browser for in-app pages? Or it only get used if the embedded version is newer that the installed one?
1 Like
It appears that WebView on Android (the turbo boosted chromium based one that ships in 4.4) is stuck in the past
https://developer.chrome.com/multidevice/webview/overview
Crosswalk is a wonderful normalizer and lets us get Chrome 51 (in stable) or 53 in Canary. But… we must use 52 and up (which is beta) cause there are some debugging bugs in that make it impractical to use.
2 Likes
Nahh, it always took you to the main page, if you click the push notification it takes you to the actual post.
we are thinking of adding a native “notification list” page, in fact @joffrey_jaffeux is planning to play with this, but for now all my focus is around getting android ready.
1 Like
WebView on my phone with Android 6 has version 52.0.2743.98
Sure, but what about 4.4 all the way up to 6 ? We want to target 4.4 and up, maybe even 4.3
Oh, I was under the impression that WebView gets updates on all Android versions.