> NOTE: Removing this is blocked on T43716, T236733, and T236731
The MobileView API was originally made for apps. Now that the MCSPage Content Service is being used (T103362),by the apps, itsMobileView's value is questionable given its maintenance cost.
The MobileView API is only used for the MainPage. This code will also be redundant upon completion of T32405.
It has been marked as deprecated in T210808. Of course deprecating should be done carefully - there may be other consumers of this API, but we should explore who they are and how we can get them using MCS.
Note: The MobileFormatter will continue to exist for MediaWiki mobile web views. The MobileView API actually has a lot of logic that is not shared by the MobileFormatter.
If all goes to plan all Wikimedia apps will be off the API come February of 2020As of June 2020, neither of the current app releases (iOS 6.6 and Android 2.7.50320) relies on MobileView directly. They are using the Page Content Service. Prior to these releases, the Android app was using the Mobile Content Service and the iOS app was using MobileView. This is blocked on T236733 and T236731.
After that,Enough users will have to upgrade to Wikipedia for iOS 6.6 or newer before MobileView can be removed (T236731).
The other element blocking removal of MobileView is incomplete language variant support in Parsoid (T43716). we'll wait until the usage is low enough (in apps) to warrant its removal.
So theoretically the API will be around till at least the end of 2020
The Page Content Service uses Parsoid for most wikis but needs to use the MobileView API for Chinese Wikipedia. Once T43716 is completed, the Page Content Service will need to be updated to remove dependence on MobileView for zhwiki (T43716).