@Mari-LouA are you suggesting to add a TL;DR?

@Mari-LouA Do you think it would help if the answer started with a big "TL;DR: You can't"? FAQs here often include some reasoning behind certain decisions/policies, so that users don't have to search for further information.

@Mari-LouA well, it does look more like my original revision now...

Should there be some link or explanation for how to enable responsive mode? I’ve seen users struggling with that.

@user289905 valid point, and also worth pointing out that the full site (desktop) link on mobiles is found at the very bottom of the page in itsy bitsy font. Very easily missed.

Can't they just ask the Android developer for access so they can take the app down? Why can't they remove the iOS app if the iOS developer is still working there?

@Mari-LouA The point of that section is to ward off questions that will inevitably be asked by authors of duplicates in the comments. Also, it answers the question's bullet "I'm wondering why the latest version is from 2017".

@Sonicthe Q: “I'm wondering why the latest version is from 2017.” A: Because Stack Exchange stopped supporting the mobile app in 2017. The answer is also in the paragraph: The mobile apps have not been updated since 2017, so any changes since then have been purely server-side. which was your edit. The answer is therefore repetitive and redundant. Finally, Also, following budget reassessments, the app developers were redelegated to other teams within the company; one of them later left the company. How relevant is that to someone who only wanted to report a bug?

@Mari-LouA The mobile apps were still "technically" supported after 2017 and before the 2019 discontinuation announcement, to the point where SE staff were still positively responding to them. The point of the question is, "why weren't there any updates after 2017 if the discontinuation announcement was in 2019?". Also, the bullet in the question asks why there have been no updates, while the text you refer to merely makes a statement that there have been no updates.

How will "No, support questions can still be asked, and perhaps the community here knows a workaround for your bug." work if the questions are closed as duplicates of this one?

@Alex, I don’t really see the conflict here. If a new support question can be answered with a specific guide, then it will be answered (provided it’s not a dupe of something else). If it cannot be answered because some support or feature request depends on features not supported in the app, then it’ll be closed as a dupe of this FAQ. In which scenario will a support question not “work” due to this FAQ?

@user289905 How will close-voters know if a question can be answered?

@Alex because close voters are sane and so are the user with gold badges that can (un)hammer these if something goes south.

I noticed that Stackexchange app is no longer available on playstore

Hmmm. I'm not impressed with that response as apps which are not maintained and updated tend to become unsafe security-wise from what I have read. That could be the reason why Google Play Store delisted the app as they review stagnant apps. They should be made unusable in my mind even though they are popular for features which are unavailable via the website. I think I might uninstall my copies seeing as they have not been maintained since 2017.

@ChrisRogers I might add that when the Android developer left Stack Exchange, SE ceased to have access to the account under which the app was published, and recovering the account is (apparently) a long and complicated process. That's why SE can't tell for what exact reason the app was removed.

Re: "the iOS app may disappear at any time"– it seems any time has finally arrived.