Thanks to everybody for talking through this and clarifying the issues.
So I'd like to move forward and figure out how we all should proceed.
I'm completely fine with renaming MobileFrontEnd2 to help avoid confusion. :-) I'll look at the suggestions and pick one.
My ideal scenario would be me continuing this rewrite while the mobile team continues with feature development on MobileFrontend. I really believe that there are several issues with the current MobileFrontend that are better resolved with a full rewrite instead of a slow refactoring of the existing extension. But I'm also happy to work with Arthur to refactor and rewrite the current MobileFrontend more gradually to resolve the issues raised.
I could work with the mobile team to come up with a checklist of goals to complete in the refactoring and rewriting before we can write off the need for a replacement for MobileFrontend. Functionaility wise, MobileFrontend2 is a clone of the original with very minimal UI changes. Maybe we could write Selenium tests for this? Maybe I could work with Chris McMahon to learn what tests need writing for this extension and write them.
-- John