Discussed:
* MobileView api
* Split it out to it's own extension
* Improve test coverage, business use cases
* Evaluate if refactoring would make sense
* Improve RL usage in MobileFrontend
* Either use a linter that matches dependency trees with the actual code
* Or use an external bundler for the dependency graphs and just include entry points in extension.json
* Feature management ("flagging") T141087
* Extract core/foundational UI components, document the hell out of them, providing examples of how to use them to build new features, and place them way, way, WAY outside of the standard MobileFrontend hierarchy
* Since Joaquin introduced me to it, I always think of Redux when I think of the outstanding documentation
* Extract Special:Nearby into its own extension
Created:
* T140882 Extracting MobileFormatter to a composer library
* T138071 Fast isolated unit testing in MobileFrontend