MobileFrontend is divided into many parts. However, many of these constituent pieces are still a mishmash of multiple, often out of place, responsibilities. For example, an overlay that is a top level application entry point that in itself encapsulates presentation, gateway, and utility duties instead of an overlay that just assembles these distinct responsibilities and their dependencies without knowing their implementation details. This umbrella epic is to track the theme of separating concerns into new parts.
Description
Description
Event Timeline
Comment Actions
Resolving this ticket. We will migrate MobileFrontend to wvui (eventually). I'm tracking this in this ticket: T281930