Change Details

This task continues a discussion that started around T195473#4783284. The question is, how should we best organize our front end code so we can minimize maintenance and new feature development cost? Speaking only about mobile and desktop interfaces for now, any integration with native apps seems best left to the service layers. Some questions that we could answer as part of this discussion: * How hard would it be to merge MobileFrontEnd, or parts of it, into core? * Would that be worthwhile in terms of maintenance? Development of new features? * <<any other specific questions from @daniel>>

This task continues a discussion that started around T195473#4783284. The question is, how should we best organize our front end code so we can minimize maintenance and new feature development cost? Speaking only about mobile and desktop interfaces for now, any integration with native apps seems best left to the service layers. Some questions that we could answer as part of this discussion: * How hard would it be to merge MobileFrontend, or parts of it, into core? * Would that be worthwhile in terms of maintenance? Development of new features? * <<any other specific questions from @daniel>>

This task continues a discussion that started around T195473#4783284. The question is, how should we best organize our front end code so we can minimize maintenance and new feature development cost? Speaking only about mobile and desktop interfaces for now, any integration with native apps seems best left to the service layers. Some questions that we could answer as part of this discussion: * How hard would it be to merge MobileFrontEndend, or parts of it, into core? * Would that be worthwhile in terms of maintenance? Development of new features? * <<any other specific questions from @daniel>>