11

It's been a while since the SE team last had an iOS or Android developer, and development job on the apps have not had any insights for years.

That, however, doesn't deny the fact that there are still many users to them. As a consequence, people are continuing to submit bug reports and sometimes feature requests about them.

If development on iOS/Android apps has ceased indefinitely, what should we to do their bug reports and feature requests?

Are we going to keep them with the hope that development on apps will resurrect one day, or just ignore them and telling users that development has frozen?

17

Just leave the questions alone. Most of the apps are still available for download and some people use them.

On the slim chance that development resumes, bug reports and feature requests will be useful. In the meantime, leaving these questions open allows users to post workarounds as answers.

8

There's nothing that should be done with these questions because:

1) There are many links to them which would unexpectedly break for <10k-ers,

2) They are useful historical artifacts to know and understand the history of SE,

3) There's always the chance of development starting up again.

They should not be deleted for reasons 1 and 2, and they should not be closed as "can no longer be reproduced" for reason 3 and because they can still be reproduced by using the apps, even if they aren't going to be fixed.

The one thing we can and probably should do is specify in the tag wikis and/or excerpts that development has stopped and that bug reports and feature requests are not likely to be fixed/implemented to warn posters of new questions and viewers of old questions.

Other than that, bug reports and feature requests for the iOS/android apps are fine and should stay as-is.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .