Hi @HNordeenWMF, Just to confirm, will this only appear in the Home Feed and only be shown once (without repeats)?

Correct!

Instrument similar to other surveys, so that free text and data is sent to Shay

@HNordeenWMF In previous surveys, we actually haven't had a free text field. For free-text surveys, we have employed Google Forms in the past.
There are fairly strict character limits in our instrumentation, making any free-text input bound by very tight constraints. In this case the constraint is on the order of ~250 characters.
We can either:

• Not have a free text field
• Have a free-text field, but it would be limited to 250 characters, and would need to be built (increasing the estimate to probably a M or L)
• Bounce out to a Google form.

@Dbrant We did for Year in Review https://docs.google.com/presentation/d/14g4rWuDkZJ-_moi6LtGhfy0hC9wlcs-9HVpi-iDnLio/edit?slide=id.g3cdb2d4511e_0_112#slide=id.g3cdb2d4511e_0_112 - is it possible to reuse?

The freetext is the main reason for doing the survey, so if we cannot do that within 2-3 points then I will cancel this task.

In T420939#12073518, @HNordeenWMF wrote:

@Dbrant We did for Year in Review

Ohh of course, sorry, forgot about that instance. To be more precise, our newer instrumentation that is working towards integrating with TestKitchen/GrowthBook imposes these stricter character limits. (Year-in-Review was using legacy instrumentation)

However, what do you actually think about limiting the response to 250 characters? This could be a pretty healthy-sized sentence, and would likely capture the gist of anything the user wants to convey. And the input field is a single line, which makes it cumbersome to enter anything much larger anyway.

And since this is in fact mostly built already, as you point out, it would not be much more difficult after all.

Got it! Yes limiting to 250 characters is acceptable! If someone goes over, does it simply chop off their answer on our end?
Or prevent the user from submitting. If we prevent the user from submitting, we just want to make sure there's some kind of user-facing error.

In T420939#12075951, @HNordeenWMF wrote:

Got it! Yes limiting to 250 characters is acceptable! If someone goes over, does it simply chop off their answer on our end?
Or prevent the user from submitting. If we prevent the user from submitting, we just want to make sure there's some kind of user-facing error.

It will prevent from submitting, and there's a standard "counter" component underneath the text field that displays "xx/250" which turns red if it goes over.

Perfect, works for me!

dbrant closed https://github.com/wikimedia/apps-android-wikipedia/pull/6715

latest alpha!

LGTM

Looks good on 50598-r-2026-07-13
Tested on:
Pixel 6 on Android 16
Pixel 8 on Android 16
OnePlus 8 on Android 13
Galaxy A36 on Android 15

Signed off