I'm also in favor of adding Talk links to the apps. In fact it did a very simple PoC[1] for the Android app a while ago, which I just rebased and updated comments yesterday.

It's not perfect but I think it works pretty decently with regular Talk pages. For Flow pages[2] more CSS is needed to make it look right. I've dabbled with getting some Flow CSS included into our CSS bundle but there are still a lot of issues left besides that[3]. I think for Flow pages we would really need a native presentation in the app to do anything beyond a read-only experience. There's an API for that.(TM)[4][5]
But again, even a read-only experience is better than none.

Cheers,
Bernd

[1] https://gerrit.wikimedia.org/r/#/c/197851
[2] In app (enwiki) search for "Wikipedia talk:Flow/Developer test page" or open https://en.wikipedia.org/wiki/Wikipedia_talk:Flow/Developer_test_page
[3] https://gerrit.wikimedia.org/r/#/c/226480
[4] https://www.mediawiki.org/wiki/Flow/Architecture/API
[5] https://www.mediawiki.org/w/api.php?action=help&modules=flow

On Thu, Jul 23, 2015 at 4:57 PM, Sage Ross <sage@ragesoss.com> wrote:
I agree that read-only access to talk pages from the app will be a
great improvement, even without editing. Even if I can't fully respond
while on my mobile device, I want to at least be able to see the
discussions. My current workflow frequently involves manually
searching for the talk page in the app. And most talk pages are
actually quite readable.

-Sage

On Thu, Jul 23, 2015 at 3:52 PM, Federico Leva (Nemo)
<nemowiki@gmail.com> wrote:
>> for savvy readers they offer useful commentary about what's on (or off)
>> the page and why.
>
>
> Yes. And this doesn't require any special magic: wikitext pages are equally
> ready to be read whether they are in namespace 1 or in namespace 0.
>
> Nemo
>
>
> _______________________________________________
> Mobile-l mailing list