Already fixed in the lates alpha (50611).

Each topic area should include a unique illustration to represent it

@HNordeenWMF Are these illustrations somewhere?

We're consuming from LAC at the service (PCS) level, not client-side, and afaict it doesn't explicitly care about Last-Modified, so as long as the underlying Node network layer handles this correctly, it should be fine.

@HNordeenWMF The requirements of this task seem to contradict the requirements of the parent Epic:

In T427929#12331480, @jasmine_ wrote:

Could you confirm if Mobile Apps would like to serve the entire assetlinks.json served on auth.wikimedia.org [0] to fulfill the DAL/ no redirect requirement specific to android apps? or sufficient to do what we’re doing in the assetlinks.json served on www.wikipedia.org [1], which is to grant the target (android_app) permission to handle all URLs that the source (www.wikimedia.org) can handle via relational string "delegate_permission/common.handle_all_urls" [2]

(took care of the P0 item)

In T436758#12333575, @kevinbazira wrote:

We are going to run a batch generation that will produce an index under:
https://analytics.wikimedia.org/published/datasets/ml/tts/experiment-v1/index.json

Thanks @kevinbazira!
How does this affect the API that the app will use to fetch the audio and vtt contents? (i.e. resolve a page title into the audio and vtt URLs)
I assume the v0 api endpoint (https://wiki-tts.toolforge.org/audio/...) is no longer correct?

✅ deployed

@HNordeenWMF To clarify about the survey:

non-retained users see it 7 days after their first Play tap.

• Display any available content/modules as soon as they're available to the user
• Minimize the latency of the first item loading in the feed as to as low as possible

Much appreciated @Toadette

+1 to the patch - tested, and works.

The event payload that is sent to logstash has a field called error_context, which is a good candidate to stuff the appInstallId into. Perhaps in json form, so it's extensible: '{ id: "xxxx-xxxx-xxxx" }'

In T431048#12258687, @SChekfa-WMF wrote:

@Dbrant @WRai-WMF what specifications for the shake-to-shuffle haptic feedback did you use on Android? i'd like to specify it for iOS here so we can align.

In T433832#12257754, @sbassett wrote:

Any reason we should keep this task security-protected? Should we wait on a future mobile release to be more widely-distributed, with this fix, or are we already there?

In T432385#12233562, @SChekfa-WMF wrote:

we're hiding them, right?

In T432385#12232422, @HNordeenWMF wrote:

@Dbrant I was pleasantly surprised with all the images!
How did you balance preferencing images for the suggestions vs keeping it fresh each day? If there are no new articles with images availalbe, will users see the same 4 again, or will it start to bring in new articles without images

There isn't really a codebase; This bot simply provides an API key for use with GitHub Actions to post messages on tasks:
https://github.com/wikimedia/apps-android-wikipedia/blob/main/.github/workflows/android_phab.yml
(unless we consider the GitHub Action to be the codebase)

In T434720#12216795, @HNordeenWMF wrote:

@Dbrant hey! From @Sucheta-Salgaonkar-WMF :

we should probably separate the content selection path from the end-to-end implementation path - so it's actually probably better for your team to use the list of EN featured articles rather than the csv from that ticket